Related
Hello , i have flashed CWM Recovery. Now i want to replace that with TWRP. How to do that ? Help ??
2 ways:
- Download a TWRP flashable .zip. While in recovery, wipe cache. Then flash .zip. Then go to "advanced options" in CWM and choose "reboot recovery"
- Download a TWRP recovery.img, and flash it through fastboot. Make sure you have fastboot and adb drivers. Connect phone to pc in fastboot mode. Open a CMD window from where you have your adb and fastboot files, as well as the recovery.img file. In the cmd window type "fastboot flash recovery _______.img" Where the blank spot is, is where you would put the name of your recovery .img file.
Hi,
Third way (Rooted Moto G)
Download TWRP Manager from Google Play and do installation of recovery with...worked perfectly for me
Keep in mind that CWM nandroid backups and TWRP backups aren't interchangeable.
OK
Simply download the twrp and flash it using the instructions on the developer's thread.
It will replace automatically.
Hii.. All , I'm using A Lyf wind mobile , I have my my orginginel ( system.img ) file I don't have PC Computer . , I'm using TWRP 3.0 .. Somebody help me how to flash a System.img using TWRP
_ THANKS _
vinay durva said:
Hii.. All , I'm using A Lyf wind mobile , I have my my orginginel ( system.img ) file I don't have PC Computer . , I'm using TWRP 3.0 .. Somebody help me how to flash a System.img using TWRP
_ THANKS _
Click to expand...
Click to collapse
TWRP can flash .img files without having to do anything special.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
TWRP can flash .img files without having to do anything special.
Click to expand...
Click to collapse
Sir .. I was tried , there was only 2 options in TWRP 1st one recovery & 2cond one boot .. Which 1 ican select ,, I need to flash system.img
vinay durva said:
Sir .. I was tried , there was only 2 options in TWRP 1st one recovery & 2cond one boot .. Which 1 ican select ,, I need to flash system.img
Click to expand...
Click to collapse
I dont think you've booted into TWRP yet, I think you're looking at bootloader, select recovery and see if it boots to TWRP.
TWRP has more than just 2 options, are you sure you have TWRP? What version is it? Does it look like this?
http://cloud.tapatalk.com/s/58a730280544c/Screenshot_2017-02-17-12-15-48.png?
If that's what you have, select Install then find your .img and flash it.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
I dont think you've booted into TWRP yet, I think you're looking at bootloader, select recovery and see if it boots to TWRP.
TWRP has more than just 2 options, are you sure you have TWRP? What version is it? Does it look like this?
http://cloud.tapatalk.com/s/58a730280544c/Screenshot_2017-02-17-12-15-48.png?
If that's what you have, select Install then find your .img and flash it.
Click to expand...
Click to collapse
Yes sir I'm Booting Into TWRP , Then > install > install images >. I found 2 options 1st one BOOT 2cond RECOVERY , but I won't to flash SYSTEM.img
vinay durva said:
Yes sir I'm Booting Into TWRP , Then > install > install images >. I found 2 options 1st one BOOT 2cond RECOVERY , but I won't to flash SYSTEM.img
Click to expand...
Click to collapse
I remember now that TWRP doesn't flash system.img correctly, system.img isn't a standard .img, you need PC and use fastboot.
Sent from my SM-S903VL using Tapatalk
Thanks Sir.. Any Another way to flash system , i don't have A PC
vinay durva said:
Thanks Sir.. Any Another way to flash system , i don't have A PC
Click to expand...
Click to collapse
I wouldn't try it without PC
Sent from my SM-S903VL using Tapatalk
vinay durva said:
Thanks Sir.. Any Another way to flash system , i don't have A PC
Click to expand...
Click to collapse
I know it is too late, but you can enter in Advaced > Terminal and then run this command:
dd if=/sdcard/system.img of=/dev/block/bootdevice/by-name/system
If your mobile phone doesnt have by-name symlinks you will need to enter the correct partition.
Aex12 said:
I know it is too late, but you can enter in Advaced > Terminal and then run this command:
dd if=/sdcard/system.img of=/dev/block/bootdevice/by-name/system
If your mobile phone doesnt have by-name symlinks you will need to enter the correct partition.
Click to expand...
Click to collapse
hi aex, I have the same problem but I dont have the folder
/bootdevice/by-name............
can you help me?
it will not work.
try to make a folder and "mount -o loop file in it.
and it will be not mounted also if you specify file system type.
(if it work probably you can use the file)
so ,i don't know how fastboot write in partition or probably
in to file system.
however if you do a dd of your current system partition in a file , after will be correctly mounted , or rewrited correctly in the original partition if you need.
then probably you cannot use fastboot system.img directly in twrp shell (using dd)
this is my experience (e2303 sony / pexorom 3.0 twrp 3.1.1)
if you are searching a fast way to know system partition device block
cat /etc/fstab
and look for system
or just mount system in twrp , then in a terminal do a
df -h
and search for system
for e2303 was /dev/block/mmcblk0p30
(example)
twrp have busybox and light kernel.
so , is linux.
for better support try to ask
tonystark88
u need to use simg2img
(sparse file format compression)
system partition device name can be different on other phones.
done.
img can be write by twrp whitout pc/fastboot.
c'ya
giuseppe
just go to file manager and search for system partition, and on first part type your system.img location and 2 part type just system location
I did this Steps on my Huawei P8. Sim2Img reported a non sparse image, so i moved directly to the DD steps. But after writing the image to the partition, the /system Partition cannot get mountet...
What the hell iam doing wrong ????
I extracted the system.img from an update.app Firmware file.
Its the same Firmware file i flashed before with the dload method.
I want to install TWRP on my Phone with an faulty USB Port. So i have no PC / ADB. I Installed the Firmware via the official Dload Method from Huawai. Then i used this crappy Kingroot to get root and installed TWRP. Now i wanted to flash the stock system partition to get rid of Kingroot for Safetynet.
But why i cant just flash the systempartition ?
Or is there another way to gain root for 15 seconds without traces ?
chr2002 said:
I did this Steps on my Huawei P8. Sim2Img reported a non sparse image, so i moved directly to the DD steps. But after writing the image to the partition, the /system Partition cannot get mountet...
What the hell iam doing wrong ????
I extracted the system.img from an update.app Firmware file.
Its the same Firmware file i flashed before with the dload method.
I want to install TWRP on my Phone with an faulty USB Port. So i have no PC / ADB. I Installed the Firmware via the official Dload Method from Huawai. Then i used this crappy Kingroot to get root and installed TWRP. Now i wanted to flash the stock system partition to get rid of Kingroot for Safetynet.
But why i cant just flash the systempartition ?
Or is there another way to gain root for 15 seconds without traces ?
Click to expand...
Click to collapse
Why not just use the settings in Kingroot to remove root? Or convert from Kingroot to SuperSu then use SuperSu app settings to remove root?
You don't have to flash the stock system to remove root.
Sent from my LGL84VL using Tapatalk
Kingroots uninstall leaves traces in /system/xbin and Safetynet wont work. Why i did not try Supersu ? :-/
But i managed to flash the system.img without problems.
First i tryed an extracted system.img from the Huawei Firmware extractor and Sim2img reported an invalid sparse image. So i thought it must be a raw image.....And this was my mistake. It is a useless image for TWRP.
So i created a flashable zip (TWRP cant flash this, too and the /system partition is not mountable after flashing / installing this zip.
BUT, the system.img INSIDE this zip is a spase image, which sim2img can handle. It gave me a nice raw image which i just dd´d to /system and BINGO, my phone starts up normally
The Short Version :
- Create a FLASHABLE ZIP with the Huawei Firmware Extractor
- use SIM2IMG in TWRP Terminal to get a RAW Image.
- dd´it to the /system partition
System img
You use the restore in twrp to flash your system img, you just until the other boxes
Edit: Sorry wrong thread
Lenovo K5 Pro ROM img
After flashing img file (using TWRP 3.3.1) the phone (Lenovo k5 pro) starts in bootloader mode. Everyone can help?
Help u
Hi u can download a deodexed rom because ais doesn't support some stock roms for ex ch Samsung roms. then decompile it.then decompile it with rar or zarchiver or etc. Then install android image studio (ais) from google
Then open it and tap unpack/mount and select system.img or system.img.ext4 file in decompiled rom . After mounting, copy all files to a directory for ex emulated/0/system/system or another. Attention if you copy it in another directory, rename it as (system) now copy the boot.img from decompiled rom into emulated/0/system .then download this file
https://forum.xda-developers.com/an...oid-o-beta-redesigned-emoji-set-t3608280/amp/
Extract meta-inf file into emulated/0/system using winrar or zarchiver or etc. Now you need to have a system folder,boot.img file and a Meta-inf in diractory emulated/0/system. Now compress system,boot.img and meta-inf into one archive and after completing, turn of your device and boot it into twrp recovery and wipe data and cache without wipping internal storage then select install. Then tap select storage and select internal storage.then go to the file and select it and turn off zip singuature verification and install it after installing tis rom, install root zip file and wipe cache/dalvik art and then reboot your device. It may take between 5-25 minutes to boot. Enjoy your new rom
#issues
Sometimes your device maybe take bootloop so you need to install your stock boot.img file and after installing your root zip file choose wipe cache/dalvik art and then reboot your system.
#Alert
1.Don't install the recovery.img file which exists in the decompiled rom because it takes your device into recovery mod and not boot anymore and after you need to install the stock rom using PC
2.your device maybe take bootloop in this method so do it with your own risk
---------- Post added at 07:58 AM ---------- Previous post was at 07:53 AM ----------
ShmuelCohen said:
After flashing img file (using TWRP 3.3.1) the phone (Lenovo k5 pro) starts in bootloader mode. Everyone can help?
Click to expand...
Click to collapse
Reboot your device and install twrp official app and open it and select flash image from a directory and select your own twrp and reboot your device [root]
Connect your phone to a PC and install stock rom using ADB or another app which was made for your smartphone [no root]
Hello
i make dump and convert it to recovery rom
it can be flashed by TWRP
this is last official EU version of Le2 x52x rom
this rom have complete translation (without english or chinese untranslated parts) of all EU languages
best way how to flash it if you havent got twrp
0. download rom https://webshare.cz/file/363v61oM3d/x527-5-9-21s-rar
1. extract downloaded package
2. go to bootloader by pressing and hold volume down and power button
3. open command promt and run:
3.1 fastboot oem unlock-go
3.2 fastboot boot twrp.img
4. now you are rebooted to twrp
5. copy rom (X527-5_9_21S.zip) to the phone
6. flash rom
7. wipe data factory reset
8. reboot phone
9. you are in official EU rom with stock recovery
veisen said:
Hello
i make dump and convert it to recovery rom
it can be flashed by TWRP
this is last official EU version of Le2 x52x rom
this rom have complete translation (without english or chinese untranslated parts) of all EU languages
best way how to flash it if you havent got twrp
0. download rom https://webshare.cz/file/363v61oM3d/x527-5-9-21s-rar
1. extract downloaded package
2. go to bootloader by pressing and hold volume down and power button
3. open command promt and run:
3.1 fastboot oem unlock-go
3.2 fastboot boot twrp.img
4. now you are rebooted to twrp
5. copy rom (X527-5_9_21S.zip) to the phone
6. flash rom
7. wipe data factory reset
8. reboot phone
9. you are in official EU rom with stock recovery
Click to expand...
Click to collapse
Can you make the same with the x522? I want to get stock again
nabelar82 said:
Can you make the same with the x522? I want to get stock again
Click to expand...
Click to collapse
yes you can
Thanks! Thats exactly what im looking for! Pefect stock ROM! Easy to install with twrp, working perfect in my x520.
veisen said:
yes you can
Click to expand...
Click to collapse
I mean if you can I don't have the stock backup I deleted by mistake
nabelar82 said:
I mean if you can I don't have the stock backup I deleted by mistake
Click to expand...
Click to collapse
you can flash this rom it is compatible
veisen said:
you can flash this rom it is compatible
Click to expand...
Click to collapse
The ROM is really good but i Tried everything to pass through safetynet but i cant do it.
Can I install regularly via stock update, w/o twrp? What's is date of security patch? Can you put homescreen there?
I'm on 5.9.021s for x526. I have x527.
google Drive
Can you upload it on google Drive and share the link please , cause google drive is faster and easier way to download
Owing all gratitude towards you
svsavic said:
Can I install regularly via stock update, w/o twrp? What's is date of security patch? Can you put homescreen there?
I'm on 5.9.021s for x526. I have x527.
Click to expand...
Click to collapse
You can not update it via stock recovery bcs leeco never release this rom it is installed on europe (Czech branded phones) i cannot post screen bcs im change phone i have Essential ph-1 for now
Can i flash it as a secondary rom (multirom)?
Does anyone have the stock modem for x527? because my signal keeps coming on and off constantly in every eui rom so I can't go back to stock, strangely I can use it on Nougat and Oreo. I've flashed this stock rom but no solution.
Hi @veisen !
Thanks for the ROM.
However - how can it be an official ROM if it shows a 'Le X527' but with a 'Snapdragon 820' (when it should be a Snapdragon 652)?
Cheers, raimerik
raimerik said:
Hi @veisen !
Thanks for the ROM.
However - how can it be an official ROM if it shows a 'Le X527' but with a 'Snapdragon 820' (when it should be a Snapdragon 652)?
Cheers, raimerik
Click to expand...
Click to collapse
Thats a bug with official rom itself. This rom is official, so chill
veisen said:
5. copy rom (X527-5_9_21S.zip) to the phone
Click to expand...
Click to collapse
can't copy X527-5_9_21S.zip (2,1GB) to /sdcard. Copy always stops after copying 140MB or so. I copy mounting USB storage from TWRP, and then through the file administrator with copy-paste (Ubuntu 16.04, linux). Filesystem is ok. I've done a factory reset before. What can I do?
xe7um said:
can't copy X527-5_9_21S.zip (2,1GB) to /sdcard. Copy always stops after copying 140MB or so. I copy mounting USB storage from TWRP, and then through the file administrator with copy-paste (Ubuntu 16.04, linux). Filesystem is ok. I've done a factory reset before. What can I do?
Click to expand...
Click to collapse
Try pushing it through adb
Rename the file to update.zip
Open terminal
cd "directory of the zip folder"
adb push update.zip /sdcard/
Wait for few minutes, it should be done.
bonsai.14 said:
Try pushing it through adb
Rename the file to update.zip
Open terminal
cd "directory of the zip folder"
adb push update.zip /sdcard/
Wait for few minutes, it should be done.
Click to expand...
Click to collapse
I've tried it already:
Code:
[email protected]:~/LeeecoLe2X527$ adb push -p X527-5_9_21S.zip /sdcard/Varis
Transferring: 15335424/2096207546 (0%)
Hanged up
xe7um said:
can't copy X527-5_9_21S.zip (2,1GB) to /sdcard. Copy always stops after copying 140MB or so. I copy mounting USB storage from TWRP, and then through the file administrator with copy-paste (Ubuntu 16.04, linux). Filesystem is ok. I've done a factory reset before. What can I do?
Click to expand...
Click to collapse
You can Sideload it enable sideload on twrp and use command
adb sideload "/your_dir/your_file.zip"
veisen said:
You can Sideload it enable sideload on twrp and use command
adb sideload "/your_dir/your_file.zip"
Click to expand...
Click to collapse
Ok, @veisen I'll try it. But do you have any reasonable explanation of why adb push stops copying?
Any one using this rom? How's battery life n camera ?
If possible post some screenshots
TWRP + MAGISK for our Motorola One Action
First of all, let me thank to @ilia3367 for his big effort bringing the joy of mod to our phones (One Vision and Action) and my fellow countryman @sfoot13 for his unvaluable help.
Original guide
Disclaimer
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Backup all your personal information, it'll be wiped.
* This process was performed on the XT2013-1 using PSBS29.-21-20-4 compilation.
Click to expand...
Click to collapse
Instructions
1- Unlock your Motorola One Action using Motorola's Official Guide.
2- Download this file to your PC.
2.1- Get the latest compilation of your firmware, according to your region, here.
2.2- Unzip the file downloaded on step 2 on c:\adb (you should already have installed ADB, Fastboot and Drivers at this point) and unzip the firmware in a place of your convenience.
3- Copy the files KANE_flash_stock.bat and vbmeta.img (remember, both files are from the file you've downloaded on the step 2) of c:\adb to the firmware folder you unzipped on step 2.2.
3.1- Some firmwares have one more system.img_sparsechunk than others, in case the firmware you've download has 10 system.img_sparsechunk add the follow line (after the 9th system.img_sparsechunk) to the .bat file using any text editor (notepad is ok) and save it:
Code:
fastboot flash system_a system.img_sparsechunk.10
4- Copy this files (located at c:\adb) to your External SD (mandatory):
Disable_Dm-Verity_ForceEncrypt.zip
MagiskManager-v7.3.4.apk
Magisk-v19.4.zip
TWRP-3.3.1_Installer_One_Vision.zip
This is where the fun begins.
5- Reboot your phone to bootloader mode.
6- Once detected, execute the KANE_flash_stock.bat you've edited and copied to the firmware folder and wait until the phone reboots to bootloader again (around 2-3 minutes)
7- Open CMD on your computer and type
Code:
cd c:\adb
, then
Code:
fastboot -w
and when it's done
Code:
fastboot boot TWRP-3.3.1_Motorola_One_Vision.img
8- TWRP will boot on your phone, surely in Russian, check the box and swipe to allow modifications on /system. I suggest you to set TWRP on your language (if not Russian of course ), the language setting is on the right column on the third button, and then, the globe icon (the last one), choose your language and set it up using the gray button.
*If you can't get to TWRP the first time, after the Android One Screen, keep pressing volume down and power buttons, when the phone shuts down, release the button power and get into fastboot again and try the command described above (fastboot boot TWRP...). Try until you can get into TWRP recovery, the first time took me around 4-5 times.
8.1- According to your language, go to Install > Select Storage > Micro SD card and flash TWRP-3.3.1_Installer_One_Vision.zip, once it's done, go to the home screen.
8.2- Now tap on Wipe > Format Data > Type Yes and go back to the home screen again.
8.3- Reboot to Recovery.
9- Install > Magisk-v19.4.zip and Disable_Dm-Verity_ForceEncrypt.zip, go to the home screen and tap on Reboot > Bootloader
9.1- On CMD type
Code:
fastboot flash vbmeta_a vbmeta_patch.img
and when it's done, press the power button to start.
10- The phone will show Android One Logo > Unlocked Bootloader warning screen > Android One Logo > It will reboot and will repeat the same process
10.1- After that scary but necessary reboot, it will reach the setup screen and... It will reboot and will repeat the process shown on step 10.
11- Once it reaches the setup screen again it will not reboot again (randoms reboot has been reported, nothing serious, let it reboot and keep it using).
12- Complete setup.
13- Uninstall Magisk Manager and install the APK you've copied to your External SD on step 4.
Now you're rooted.
Thanks for taking the time to read the whole guide and excuse my not-so-well (poor is threshed) english.
The original guide didn't work for me on the part when it says to boot TWRP using fastboot > Wipe Data > boot TWRP via fastboot again, it kept hanging on the Android One screen.
Greetings,
Charly.
Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I keep getting stuck on boot screen
Has anyone tried it yet? Because I tried to root the device following the guide but can't get it to boot in twrp. Every time I try to, It gets stuck on the boot screen and Then I have to repair it through moto smart assistant
Root Moto One Action - Working on Android Pie (9) and Q (10) 23.01.2020
anongh0st said:
Has anyone tried it yet? Because I tried to root the device following the guide but can't get it to boot in twrp. Every time I try to, It gets stuck on the boot screen and Then I have to repair it through moto smart assistant
Click to expand...
Click to collapse
There's another way to do it.
Download the files and install magisk on your phone.
1. Open magisk and patch your boot.ing
2. Save your patched boot to adb-fastboot folder.
3. Reboot to bootloader.
4. Flash vbmeta.img: fastboot flash vbmeta_a vbmeta.img
5. Flash your patched boot: fastboot flash boot_a PATCHEDBOOT.IMG
6. Flash vbmeta_patched: fastboot flash vbmeta_a vbmeta_patch.img
7. fastboot erase userdata and reboot.
8. Configure your phone and install magisk manager apk.
9. Here, you'll need and app... Franco kernel app, because that app allow you to flash zips without twrp (I don't know a similar app).
10. Open Franco kernel app and install twrp installer zip and reboot.
11. Reboot into FASTBOOT and type fastboot -w after that, select "Reboot Recovery".
12. Now, configure Twrp, change language and format Data (type YES), if you don't format data, you'll end in bootloop.
13. Flash magisk again because the phone was unrooted when twrp installer was flashed and flash Disable_Dm-Verity_ForceEncrypt.zip.
14. Reboot and if everything was successfully, you should be rooted with twrp working.
15. Be grateful
---------- Post added at 02:33 AM ---------- Previous post was at 02:27 AM ----------
@Tuandroidaldia
Thank you so much for the guide
If you want to UPGRADE or DOWNGRADE MAGISK, do this:
Download the Magisk version that you need and reboot into recovery.
1. Flash the downloaded Magisk version.
2. Now flash Disable_Dm-Verity_ForceEncrypt.zip
3. Reboot.
4. Check if everything is ok.
5. Hit or say "thanks".
anongh0st said:
Has anyone tried it yet? Because I tried to root the device following the guide but can't get it to boot in twrp. Every time I try to, It gets stuck on the boot screen and Then I have to repair it through moto smart assistant
Click to expand...
Click to collapse
I rooted my device and then made this guide, so yes, I "followed" it If you're not able to boot into TWRP then you're missing some steps, like "fastboot -w"
Hi, I just have a little query. My device model number is XT2013-2. Since you performed the aforementioned steps on XT2013-1, do you have any idea whether it will work on my device or not? The sole reason I cannot go ahead and try it myself is that the XT2013-2 is currently not supported by Moto Smart Assistant. So I don't want to leave my device in a bricked state with no workaround. Therefore any help in this regard will be highly appreciated.
binary**# said:
Hi, I just have a little query. My device model number is XT2013-2. Since you performed the aforementioned steps on XT2013-1, do you have any idea whether it will work on my device or not? The sole reason I cannot go ahead and try it myself is that the XT2013-2 is currently not supported by Moto Smart Assistant. So I don't want to leave my device in a bricked state with no workaround. Therefore any help in this regard will be highly appreciated.
Click to expand...
Click to collapse
I bricked my device a few times and never used "Moto Smart Assistant", only fastboot and fastboot commands. In order to achieve root on your device, you should get the firmware (step 2.1). In case you have no luck getting root, you can recover your device using fastboot and fastboot commands.
Tuandroidaldia said:
I bricked my device a few times and never used "Moto Smart Assistant", only fastboot and fastboot commands. In order to achieve root on your device, you should get the firmware (step 2.1). In case you have no luck getting root, you can recover your device using fastboot and fastboot commands.
Click to expand...
Click to collapse
Got it. Thanks By the way, is there any batch file to execute these all fastboot commands at one go? Because I only know the fastboot commands for flashing all the sparsechunk, .bin and.img files. But on extracting the stock firmware. there seem to be various other files as well, of which I have no clue whatsoever. Neither do I have any idea regarding their fastboot commands.
binary**# said:
Got it. Thanks By the way, is there any batch file to execute these all fastboot commands at one go? Because I only know the fastboot commands for flashing all the sparsechunk, .bin and.img files. But on extracting the stock firmware. there seem to be various other files as well, of which I have no clue whatsoever. Neither do I have any idea regarding their fastboot commands.
Click to expand...
Click to collapse
Yes, download the file attached in the 2nd step in this post and grab the file "KANE_flash_stock.bat" and if the firmware you downloaded for your XT2013-2 has 10 system.img_sparsechunk add the follow line (after the 9th system.img_sparsechunk) to the .bat file using any text editor (notepad is ok) and save it:
Code:
fastboot flash system_a system.img_sparsechunk.10
Unzip the firmware file and copy "KANE_flash_stock.bat" to the unzipped firmware folder.
Tuandroidaldia said:
Yes, download the file attached in the 2nd step in this post and grab the file "KANE_flash_stock.bat" and if the firmware you downloaded for your XT2013-2 has 10 system.img_sparsechunk add the follow line (after the 9th system.img_sparsechunk) to the .bat file using any text editor (notepad is ok) and save it:
Code:
fastboot flash system_a system.img_sparsechunk.10
Unzip the firmware file and copy "KANE_flash_stock.bat" to the unzipped firmware folder.
Click to expand...
Click to collapse
It seems my wordings confused you. By saying "these fastboot commands", I was referring to the fastboot commands to be used while flashing the files of the stock firmware and not for the rooting process. The latter part you have already explained quite well in the first post itself. Anyways, thanks for the suggestions
So here are my results
After unlocking the bootloader, I was able to execute the process upto the point we have to boot the TWRP recovery. Although the fastboot command showed the success message while booting to twrp recovery, yet the device got stuck in the Android One screen. So then I had to (obviously) skip the flashing of TWRP zip, Magisk zip, and DM Verity file. I went ahead and flashed the vbmeta file and the device got booted to Android OS without any hiccups. So currently the device works normally but without root (and recovery). The only reason I guess for that is you have tried this on XT 2013-1 whereas mine was XT 2013-2. But still, I don't think that should have made such a glaring difference.
As a side note, please change the TWRP boot command from fastboot boot TWRP-3.3.1_One_Vision.img
to fastboot boot TWRP-3.3.1_Motorola_One_Vision.img. The zip file contains the TWRP recovery with the latter name. Although not a big issue for us, still any new user may get confused with the subsequent error message that will pop up.
binary**# said:
It seems my wordings confused you. By saying "these fastboot commands", I was referring to the fastboot commands to be used while flashing the files of the stock firmware and not for the rooting process. The latter part you have already explained quite well in the first post itself. Anyways, thanks for the suggestions
Click to expand...
Click to collapse
I understood you. One of the steps for achieving root is to flash the Stock Firmware (with the patched vbmeta.img), so, If you want to go back to stock, you have to flash the entire firmware using the same commands as described above (with the stock vbmeta.img)
binary**# said:
After unlocking the bootloader, I was able to execute the process upto the point we have to boot the TWRP recovery. Although the fastboot command showed the success message while booting to twrp recovery, yet the device got stuck in the Android One screen. So then I had to (obviously) skip the flashing of TWRP zip, Magisk zip, and DM Verity file. I went ahead and flashed the vbmeta file and the device got booted to Android OS without any hiccups. So currently the device works normally but without root (and recovery). The only reason I guess for that is you have tried this on XT 2013-1 whereas mine was XT 2013-2. But still, I don't think that should have made such a glaring difference.
As a side note, please change the TWRP boot command from fastboot boot TWRP-3.3.1_One_Vision.img
to fastboot boot TWRP-3.3.1_Motorola_One_Vision.img. The zip file contains the TWRP recovery with the latter name. Although not a big issue for us, still any new user may get confused with the subsequent error message that will pop up.
Click to expand...
Click to collapse
Thanks for the note, I'll change the guide ASAP. If you don't get to TWRP at the first try, you have to reboot into bootloader again (keep pressing the power button and volumen down button until it powers off, release the power button and it should reboot to bootloader), enter fastboot boot TWRP-3.3.1_Motorola_One_Vision.img and see if you can boot into TWRP, if not, try again until you can boot to TWRP (it took me around 3 or 4 times to get TWRP booted on my One Action the first time)
Hi Guys!
Got my Action One today (US User here!) and was pulling out my damn hair!!!
For those who can NOT boot into TWRP double check STEP 3!!! My issue was, even though I copied the extra zip file into the firmware folder, it did NOT overwrite the vbmeta.img so it was still loading the non patched version! Once I saw that the version it was flashing was from 9-16-2019 (For my firmware - RETAIL) and not the one from the zip from 9-26-2019! Once did that, on the second try TWRP booted and volia!
SO OP Please add to check the vbmeta.img is the correct version being flashed if they can not boot to TWRP and thanks for the instructions!
Ok so stupid me (This happened to me on my G5s+. I come from Quark so there was only one possible firmware for the phone since it was a verizon branded firmware) flashed the wrong firmware (RETAIL vs RETUS) but this guys doesn't see to work on the XT2013-4 though. The RETAIL firmware will let me have data but no voice on Verizon.
Any suggestions anyone?
My dear ... I did all the correct procedure, following every detail and more than once. And it didn't work! Neither this method nor the replacement of boot.img with the magiskmanager patch. "failed to validate boot image"
Motorola One Action XT2013-1
Sorry for the Google translator.
thalesjans said:
My dear ... I did all the correct procedure, following every detail and more than once. And it didn't work! Neither this method nor the replacement of boot.img with the magiskmanager patch. "failed to validate boot image"
Motorola One Action XT2013-1
Sorry for the Google translator.
Click to expand...
Click to collapse
During the original setup, where did it fail? Did it not boot TWRP?
Nothing works. Neither the original setup nor enter TWRP. This available TWRP doesn't even actually install (Failed). I downloaded from the unofficial TWRP site, and this was OKAY but did not boot ... already did and redo the procedure more than ten times ... give up !!!
thalesjans said:
Nothing works. Neither the original setup nor enter TWRP. This available TWRP doesn't even actually install (Failed). I downloaded from the unofficial TWRP site, and this was OKAY but did not boot ... already did and redo the procedure more than ten times ... give up !!!
Click to expand...
Click to collapse
So you first downloaded and flashed your firmware from the listed and did the sets to add in the extra line of code for it? Did that even complete? Then the fastboot -w? Also you copied over the vbmeta.img in the zip to the firmware folder? Twrp will not boot if that patched file is not there. Also you only boot from twrp not flash it. You don't flash it until later
---------- Post added at 02:46 PM ---------- Previous post was at 02:45 PM ----------
Also what model of the XT2013 are you uaing? There is XT2013-1 thru XR2013-4.
Root success! Xt2013-2
So I finally rooted my Moto One Action (XT2013-2). I read on many forums that the method of flashing the patched boot.img file gave some kind of validation error for their boot files. But anyhow I went ahead with the very method and was able to successfully root my device. Here are the steps to be followed.
STEPS:
View attachment 4870223
NOTE: USERS HAVING XT 2013-2 (INDIAN VARIANT) MAY DIRECTLY TAKE MY PATCHED BOOT.IMG FILE. IT IS BASED ON THE FIRMWARE VERSION PSBS29.39-23-6
1. Extract the boot.img file from the stock firmware.
2. Patch it via Magisk Manager. The magisk_patched.img file will now be created under the Downloads folder. Move it to the platform-tools folder on your desktop.
3. Reboot to fastboot mode and flash the vbmeta file via fastboot flash vbmeta_a vbmeta.img
4. Now use the fastboot flash boot_a magisk_patched.img to flash the patched boot file.
5. Next, flash the vbmeta patched file using fastboot flash vbmeta_a vbmeta_patch.img
6. Then erase user data using fastboot erase userdata
7. Finally fastboot reboot
8 Now set up the device and install the Magisk Manager app.
9. Head over to the Magisk Manager app. It will ask for some additional configurations. Allow it. It will take a minute or two for the Magisk configuration to complete. Once done, your device will automatically reboot once. it's normal.
10. That's it. Your Moto One Action will now be successfully rooted (as already mentioned, the process was carried on the version XT 2013-2.)
This guide is general guide for the installation of custom ROMs. I will also include guide to install stock ROM on devices which have been bricked or for solving various problem which you may encounter in custom ROMs. There are other guides for the same purpose but most of them are outdated and many of you seem to ignore old guide despite the fact that those guides can be helpful.
This is guide is only relevant for installation of custom ROMs which were released up to the date of posting this guide or up to android version 11. Recovering a bricked device can be done in the same way as to this one but installation instruction for devices with android version greater than 11 may differ.
DISCLAMER
Code:
I am NOT responsible for bricked devices,
thermonuclear war or for you getting fired because your alarm app failed.
Make sure the bootloader is unlocked and never lock the bootloader
How to unlock bootloader ?
>See in this thread.
Hard Brick, Soft brick, Problems in custom rom due to bad base, installation of base for switching to custom roms: windows linux
Installation of stock ROM through fastboot : The reply below
Migration from stock base to custom ROM : CLEAN FLASH
Migration between different version of same custom ROM : DIRTY FLASH
FOR SPECIFIC THREADS
Oragne Fox For Daisy
TWRP For Daisy
Magisk
CREDITS:
LInkBoi for his previous guide and TWRP
DarthJabba9 for Orange Fox Recovery
Every pros in daisy telegram groups.
EDL FLASHING (For windows only)
EDL flashing can be helpful when flashing every partition of device is needed either for clean stock base or after brick or after some failure.
EDL flashing can be the final resort when everything else fails.
PREREQUISITES
1) A good USB cable, your phone
2) A PC with either windows or linux
3) Fastboot drivers from google and edl drivers from qualcomm
4) Platform tools from google
5)Fastboot rom. This should be full rom in .tgz format.
6)Xiaomi flash tool (LATEST VERSION AVAILABLE)
Install the adb and fastboot drivers from google. If you are on windows 10 or greater then you can also use "windows update > optional updates" to update adb and fastboot drivers + edl drivers. For the installation of drivers always use trusted sources and don't turn of driver signature enforcement if you can.
Extract the platform tools in a convenient folder, we will be doing our operations from this folder for fastboot and adb opeartions. Extract the fastboot ROM and place that in convenient folder as well. And for xiaomi flash tool extract the zip and launch XiaoMiFlash.exe .
If you can access fastboot in you phone then the phone can be booted into edl mode through fastboot else you have to take out back cover and short the testpoint pins to make the device boot into edl mode (see the attached image ).
If you can access fastboot. Boot into fastboot and type the following command in terminal.
To check if device is connected properly and drivers are properly installed
If no devices is shown then connect device properly with good usb cable and check the drivers.
Code:
fastboot devices
To boot phone into edl mode. This is only possible if the bootloader is unlocked else testpoint-edl is the only option
Code:
fastboot oem edl
The device should be shown as COM device in device manager ( Windows ). If not then either drivers aren't installed properly or your phone isn't in edl mode.
Now click on refresh button in xiaomi flash tool. Your device should be recognized as com device. Set the path to the images folder ( extracted fastboot rom ). Select CLEAN ALL option . If everything is good then click
on FLASH. The flashing process should start now. After the process completes keep pressing power button to boot device into the currently installed ROM.
Just install the rom and setup once even if you're going to flash custom rom next. This reduces various problems which may come in custom ROMs.
If any error occurs then try the following:
Make sure you are using latest flash tool.
Good fastboot rom (shouldn't be corrupted )
Good USB cable and try different ports of the PC.
The flashing should be done immediately after booting to edl. If not then take out battery and reconnect it if you have back cover open(In case of hard brick). Or keep pressing power button and volume down to boot into fastboot and boot to edl mode again from the above instructions(If fastboot is accessible)
For booting to edl using testpoint:
> Take out backcover
> Disconnect battery
> Short the pins
> Flash
> Connect battery after flashing is complete
> Keep pressing power button to boot into system.
qdl flashing ( linux only )
For very detailed guide github -> bkerler edl
Thanks to DEFXZ and LinkBoi for suggesting this alternative.
Make sure you have platform tools, fastboot rom and other prerequisites to detect device properly.
clone the repository in convenient place
Code:
git clone https://git.linaro.org/landing-teams/working/qualcomm/qdl.git --depth=1
change to qdl directory
Code:
cd qdl
Build qdl tool
Code:
make
Finally flash the rom
Code:
./qdl --storage emmc --include /path/to/stock/images /path/to/stock/images/prog_emmc_firehose_8953_ddr.mbn /path/to/stock/images/rawprogram0.xml /path/to/stock/images/patch0.xml
The paths are the paths to various files inside the images folder which will be obtained after fastboot rom is extracted.
For further informations:
Original github link
qdl discussion in XDA
FASTBOOT FLASHING
PREREQUISITES
FASTBOOT DRIVERS
PLATFORM TOOLS
FASTBOOT ROM
GOOD USB CABLE
PC WITH WORKING USB PORT
See this for meeting prerequisites.
Install fastboot drivers, connect device to PC via USB.
Extract platform tools into a convenient folder.
Extract fastboot ROM into a convenient folder.
Go to platform tools folder ( this will contain files and executable like fastboot.exe) and open powershell or any terminal window there
[ shift + right click and select open (powershell) window here ]
Type this command to see everything worked correctly.
Code:
fastboot devices
If not then check every step properly.
Now execute the script to flash the ROM.
Execute flash_all.bat script for windows PC.
Execute flash_all.sh script for linux PC.
If platform tools cannot be accessed system wide then.
Code:
./fastboot devices
will provide fastboot devices information.
For flashing drag and drop flash_all.bat or flash_all.sh file into the terminal.
Code:
'/media/user001/user/daisy/stock_roms/daisy_global_images_V10.0.18.0.PDLMIXM_9.0/flash_all.sh'
It will look something like this in linux and similar in windows.
If any error occurs the search for particular error. Most of the times the error is due to corrupted fastboot ROM or bad connection between phone and PC.
FINALLY! FLASHING CUSTOM ROM
STEP 0
Flash(if not flashed already) the stock base recommended by particular ROM, if the ROM doesn't recommend a specific stock base flash 10.0.18.0 from the above instructions.
PREREQUISITES
TWRP or ORANGE FOX RECOVERY
Fastboot drivers and platform tools (details above )
The ROM which you want to flash, choose from here
GAPPS package if rom is vanilla and you want to install it.
Magisk if you want to root.
As you may have known by experience, our device doesn't have recovery partition so, flashing recovery through fastboot isn't possible. For flashing recovery first we need to boot recovery image and then only we can flash it.
If you want to use twrp:
Download both twrp*.zip and twrp*.img and place it in a convenient place.
If you want to use orange fox recovery:
Download orangeFox*.zip and extract it.
Keep both the .zip and .img file in convenient place.
If you have sdcard then copy ROM file, gapps, magisk, twrp or orange fox files into sdcard.
If not then there will be further instructions.
Now, connect the phone to the PC via USB and enable usb debugging. And open terminal in the platform tools folder as in above instructions.
Check device connectivity:
Code:
adb devices
Reboot into fastboot:
Code:
adb reboot bootloader
Check device connectivity:
Code:
fastboot devices
Lets check if the bootloader is unlocked:
Code:
fastboot oem device-info
If bootloader isn't unlocked you won't be able to flash custom recovery into the device. So, first unlock the bootloader. This should be allowed in the developers option of your phone first. This will factory reset the device.
Code:
fastboot oem unlock
Now if everything is good then it's time to boot into custom recovery:
Code:
fastboot boot recovery.img
recover.img is name of image of whichever custom recovery you want to use.
Code:
fastboot boot '/media/user001/storage (1)/daisy/twrp/twrp-3.5.2_9-2-daisy-unofficial.img'
It's like this in my case. You can drag and drop after typing fastboot boot
The phone should now boot into custom recovery. If it ask for decryption then your lockscreen password should work there.
if you want to flash recovery only then find the recovery.zip you want and flash it.
The steps further is also valid for moving between different custom roms. The term used for such process is CLEAN FLASH.
For Flashing custom ROMS :
SOMETIMES FLASHING INSTRUCTIONS MAY DIFFER SO, BE SURE TO CROSS CHECK FOR INSTRUCTION IN ROM SPECIFIC XDA THREAD OR TELEGRAM GROUP
The following action will wipe userdata if not wiped already. Be sure to backup data before these steps. Also if you encounter any future problems full backup from custom recovery may be able to solve most of the problems. So, be sure to keep full backup(including every partition) of your device.
Go to main menu > wipe > select all except internal storage and microSD.
Swipe right to perform wipe.
Install custom recovery by flashing recovery.zip
(This is done in case adb push doesn't work below and sdcard isn't available for flashing)
Again go to main menu > wipe > format data
Type yes and press enter.
If you don't have files in your sdcard then:
push rom file + gapps + other files into your device through adb push.
The command will be something like this:
Code:
adb push '/media/user001/storage (1)/daisy/posp/potato_daisy-11-20210919-dumaloo.v4.2.3+20.Community.zip' /sdcard
If adb push fails to work then you can reboot recovery and simply copy the files through file explorer.
Reboot to recovery only if you had installed recovery after wiping system else the device will soft brick
Now flash the rom.zip by selecting the file and swiping right.
Flash custom recovery if the ROM doesn't contain recovery
We have to change current slot even if we don't want to flash anymore things.
Latest recoveries changes slot automatically So, go to main menu > reboot > recovery
Now flash files which you want to flash i.e. gapps and magisk.
Again, Don't flash gapps if the ROM is of Gapps variant
Most of the roms now have implemented FBE (File Based Encryption ). So, you need to format data before rebooting to system. Again, check for specific ROM installation instruction if that is required or not. If you keep data from previous ROM that won't be considered a clean flash so, for proper clean flash format data before rebooting to system.
reboot system
MOVING BETWEEN DIFFERENT VERSION OF SAME CUSTOM ROM
Dirty flash or OTA
Most of the newer ROMs have seamless update ( even the unofficial ones ). The OTA update is simple. Just go to updater ( in settings > system or native app, depends upon the rom). If your ROM is of vanilla version then make sure gapps and/or magisk which you have installed, your ROM and custom recovery all support addon.d survival script. If they don't then you may have to flash everything again after update process is complete.
If custom recovery itself doesn't support update then you may need to choose different recovery or dirty flash ROM from the recovery. Don't worry most of the roms and both the recoveries for daisy support OTA and addon.d survival.
DIRTY FLASHThe process of flashing a ROM on top of existing one keeping the /data partition intact is known as dirty flashing. Such flashing must be done only on different builds of same ROM and it isn't recommended to flash build of lower version on top of higher version.
The steps for dirty flashing:
Download the update package.
Reboot to recovery
Enter password for decryption if encrypted.
Flash the update.zip package.
Reboot recovery, if recovery/rom doesn't support survival of recovery then flash recovery before rebooting to recovery.
If gapps and/or magisk survival isn't supported then flash gapps and magisk, make sure gapps is of the same type which was flashed before.
reboot system
Hi @user-001 thanks for this.
I'm on a stock A2 lite thats never had anything done to it , am i right in thinking i follow the clean flash section ?
You mention in there
We have to change current slot even if we don't want to flash anymore things.
Click to expand...
Click to collapse
I'm not fully sure what that involves could you break it down the steps a little for me.
I've downloaded all the files and am set up but i'm unsure on the Flashing fastbbot section where you say to use these files..
Execute flash_all.bat script for windows PC.
Click to expand...
Click to collapse
Is this a section i can bypass ? if not where can i get them from ?
Cheers
steve.loveday said:
Hi @user-001 thanks for this.
I'm on a stock A2 lite thats never had anything done to it , am i right in thinking i follow the clean flash section ?
You mention in there
I'm not fully sure what that involves could you break it down the steps a little for me.
I've downloaded all the files and am set up but i'm unsure on the Flashing fastbbot section where you say to use these files..
Is this a section i can bypass ? if not where can i get them from ?
Cheers
Click to expand...
Click to collapse
1) Yes you should follow clean flash instructions.
2)Changing of slot is done in custom recovery. Precisely in the reboot menu. But newer recoveries automatically switch the slot after flashing the rom , just be sure to reboot to recovery after flashing the recovery zip file.
3) the flash_all.bat script will be inside the extracted rom(fastboot rom) folder. You can use xiaomiflash too for flashing through fastboot.
user-001 said:
1) Yes you should follow clean flash instructions.
2)Changing of slot is done in custom recovery. Precisely in the reboot menu. But newer recoveries automatically switch the slot after flashing the rom , just be sure to reboot to recovery after flashing the recovery zip file.
3) the flash_all.bat script will be inside the extracted rom(fastboot rom) folder. You can use xiaomiflash too for flashing through fastboot.
Click to expand...
Click to collapse
Hi thanks for the reply,
I'm getting confused with all the various guides all seem to want you to do it a different way.
As i'm wanting Lineage thier instructions are...
Installation:
Download the latest build from here
Download LinkBoi00's version of TWRP here
Reboot to bootloader (adb reboot bootloader)
Fastboot into TWRP recovery (fastboot boot twrp*.img)
Do a factory reset in TWRP
Flash the latest build of Lineage OS
Boot into your new phone
Click to expand...
Click to collapse
Theres no mention of the edl or fastboot flashing and also the fastbot rom i downloaded doesnt have the flash_all.bat script in the zip file.
So do i follow thier instructions or these ones ?
Cheers
steve.loveday said:
Theres no mention of the edl or fastboot flashing and also the fastbot rom i downloaded doesnt have the flash_all.bat script in the zip file.
So do i follow thier instructions or these ones ?
Cheers
Click to expand...
Click to collapse
This guide deals with how to do something rather than what to do, meaning you should always do what particular rom suggests but the way to do this is mentioned here.
edl or fastboot flashing comes under clean flashing with new base, most of the time you aren't required to do this.
The script should be clean_all.bat or something similar just don't execute script with lock in the name(it will lock the bootloader)
And if you're already on the recommended base you don't have to flash the fastboot rom.
First of all, thank you very much for the detailed guide. What you have done here took a lot of work to do but it will help a lot of people (including me) to understand, albeit rudimentarily, the structures and functions of the devices etc.
For all that, thanks again.
When I start using the guide, I will update this post with any questions, such as :
fastboot boot '/media/user001/storage (1)/daisy/twrp/twrp-3.5.2_9-2-daisy-unofficial.img'
why not doing below? (For those who, like me, are not very familiar with linux.)
1. > adb push <twrp.img> /sdcard or same adb push "C:\platform-tools\twrp-3.5.2_9-2-daisy-unofficial.img" /sdcard
( which means push <file> from "adb|platform-tools\ folder" (eg. C:\platform-tools\)
into the root of <internal storage> | /storage/emulated/0 )
2. Reboot from adb to fastboot:
> adb reboot bootloader
3. Boot the image from <internal storage>:
> fastboot boot /sdcard/twrp-3.5.2_9-2-daisy-unofficial.img
What is the "Red" pointed and "Yellow" addresses"?
fastboot boot '/media/user001/storage (1)/daisy/twrp/twrp-3.5.2_9-2-daisy-unofficial.img'
I followed your "EDL FLASHING" post (#2) and it worked exactly as you mention!
In short, I was comming from unsuccessful flashing... but this is out of topic.
For me, did not worked the first time (after restarts) but the other day worked perfect.
The point is, most of times, it's becase windowz drivers.
We have to point that windowz needs their time to take the drivers in place. So, be patient and leave windowz to (not forced) restart(s).
AntonyMan said:
What is the "Red" pointed and "Yellow" addresses"?
fastboot boot '/media/user001/storage (1)/daisy/twrp/twrp-3.5.2_9-2-daisy-unofficial.img'
Click to expand...
Click to collapse
That must be your terminal representing different type of character in different colors.
Or, Are you talking about something else ?
steve.loveday said:
Theres no mention of the edl or fastboot flashing and also the fastbot rom i downloaded doesnt have the flash_all.bat script in the zip file.
So do i follow thier instructions or these ones ?
Cheers
Click to expand...
Click to collapse
For future references, the extracted fastboot ROM should be like this and you need to execute flash_all.bat or flash_all.sh script depending upon your OS or terminal.
user-001 said:
That must be your terminal representing different type of character in different colors.
Or, Are you talking about something else ?
Click to expand...
Click to collapse
Of course I'm talking about something else. lol
I was talking about that 'strange' address. fastboot boot '/media/user001/storage (1)/daisy/twrp/twrp-3.5.2_9-2-daisy-unofficial.img' (explained in post #11)
There is not such a directories in my miA2Lite phone. Obviously, it's because you are on Linux or Mac (UNIX). On Windowz 'command prompt' syntax it's slightly different.
Thus, I typed fastboot boot "/sdcard/twrp-3.5.2_9-2-daisy-unofficial.img"
* /sdcard is the root of <internal storage> directory.
** On Windows, double quote the address, if it's include spaces.
AntonyMan said:
Of course I'm talking about something else. lol
I was talking about that 'strange' address. There is not such a directories in my miA2Lite phone.
Thus, I typed fastboot boot "/sdcard/twrp-3.5.2_9-2-daisy-unofficial.img"
* /sdcard is the root of <internal storage> directory.
** On Windows, double quote the address, if it's include spaces.
Click to expand...
Click to collapse
The twrp image was on my pc(linux) i was booting directly from pc's terminal. And if you use only adb(or fastboot) then the paths are pc's absolute paths.