Database Info

[NIGHTLY][ROM][FRG83] CyanogenMod 6 for vendor Bravo (HTC Desire GSM)

This thread is reserve for nightly build of CyanogenMod Rom for HTC Desire GSM (cdma version here)
CyanogenMod is a free, community built distribution of Android 2.2 (Froyo) which greatly extends the capabilities of your phone.
Code:
** These CyanogenMod builds are highly experimental and unsupported.
**
** Please refrain from submitting bug reports for any issues
** you may encounter while running one of these builds.
**
** Submitting bug reports on nightly builds is the leading
** cause of male impotence.
What are Nightly build? Auto compiled build of the latest CyanogenMod source from github. This version change each night and aren't officialy supported.
If you find bugs/issues you can/must discuss here (do not submit nightlies bug on CyanogenMod issue tracker).
Warning : Not for new user, flash this build only if you know what you are doing !!!
INSTRUCTIONS:
- First time flashing CM 6 to your Desire (or coming from another ROM)?
1. Root your device and install Clockwork Recovery (Unrevoked method is recommended).
2. Do a Nandroid backup!
3. Update your radio if needed (720p require 5.x radio)
4. WIPE (wipe data/factory reset + wipe cache partition)
5. Install the ROM
6. Optionally install the Google Addon
- Upgrading from earlier CM6?
1. Do a Nandroid Backup!
2. Install the ROM (your Google apps will be backed up automatically)
There are no Google Apps bundled with CM ROMs, because Google asked Cyanogen to remove copyrighted apps, after flashing rom don't forget to flash Google Addon package if you want it.
Latest version: http://mirror.teamdouche.net/?device=bravo
before flash is recommended to check the md5sum
CyanogenMod Enhancement:
ChangeLog / Twitter
Please visit the CyanogenMod Wiki for step-by-step installation walkthroughs and tons of other useful information.
Thank you to EVERYONE involved in helping with testing, coding, debugging and documenting! Enjoy!
thank's to gatsu_1981 and imfloflo for inspiration

Rooting Guide
http://forum.xda-developers.com/showthread.php?t=788044
Google Addon: latest HDPI-20101114
Other release http://goo-inside.me/google-apps/
Radio Firmware: 5.x radio required (GSM ONLY)
Desire GSM radio thread
Read/Write Access System Partition (S-OFF)?
Thank's to AlphaRev [site] [xda]
Low storage for apps?
Flash the AlphaRev HBOOT Bravo N1Table (Require S-OFF)
Follow this instrunction for update without data lost (aka no data wipe)
Still low storage for apps?
Install an A2SD solution: Firerat or Darktremor
i recommend the Firerat solution: CM specific, less space usage 25kb vs 6mb, bind mount, no boot loop, auto restore after cm rom update (from 1.35b)

Fantastic, thanks Kali!

bemymonkey said:
Fantastic, thanks Kali!
Click to expand...
Click to collapse
+1
And don't post questions before reading the 300+ pages of this thread: http://forum.xda-developers.com/showthread.php?t=719544
Just kidding. But I thought a reference to the old thread could be useful.

yuo should add a link to alpharevs s-off and modified partition table

deleted .

the developt is in 6.1 cyanomod nightly updated right?

Latest nigthlies have been rock solid for me. My only complaint is the annoying credential storage password, which I must enter every time I reboot the phone if I want to connect to 802.1x wifi networks. Other than that, 16x have been flawless.

*cheers kali on*
Finally an up to date thread. Reading your post I learned something. I didn't know firerat a2sd now works with cyanogen.
Anyone got experience migrating from dta2sd to firerat?
Swyped with my S-OFF'd brain using teh internetz

Is there a patched Amon Ra recovery image that allows you to use the N1 partition table ?

why woud you patch it?? just use n1 table and default amon ra

madman_cro said:
why woud you patch it?? just use n1 table and default amon ra
Click to expand...
Click to collapse
So would I be correct in saying that all I have to do is "fastboot flash hboot bravo_alphaspl-n1table.img" followed by a full wipe.

ganjamu said:
So would I be correct in saying that all I have to do is "fastboot flash hboot bravo_alphaspl-n1table.img" followed by a full wipe.
Click to expand...
Click to collapse
what i did was
fastboot erase cache
fastboot flash hboot bravo_alphaspl-n1table.img
fastboot erase cache
fastboot erase system
fastboot erase userdata
fastboot flash recovery blablabla
wiped all from recovery and installed rom

madman_cro said:
what i did was
fastboot erase cache
fastboot flash hboot bravo_alphaspl-n1table.img
fastboot erase cache
fastboot erase system
fastboot erase userdata
fastboot flash recovery blablabla
wiped all from recovery and installed rom
Click to expand...
Click to collapse
Thanks! I will give it a shot tonight and let you know how it goes.

Would this also work?:
nandroid backuo
fastboot erase cache
fastboot flash hboot bravo_alphaspl-n1table.img
fastboot erase cache
fastboot erase system
fastboot erase userdata
fastboot flash recovery blablabla
nandroid restore

stingerpl said:
Would this also work?:
nandroid backuo
fastboot erase cache
fastboot flash hboot bravo_alphaspl-n1table.img
fastboot erase cache
fastboot erase system
fastboot erase userdata
fastboot flash recovery blablabla
nandroid restore
Click to expand...
Click to collapse
Yes! Absolutely no problem... (but if you already have recovery, then there is no need to flash a new one)

Am I the only one having problem with build163? The zip won't install from my recovery, just stating it's 'bad'. I already redownloaded it. It unzip's fine on my linux box. I even rezipped it but my recovery keeps refusing to start the install process.
I'm a bit stumped here.

dipje said:
Am I the only one having problem with build163? The zip won't install from my recovery, just stating it's 'bad'. I already redownloaded it. It unzip's fine on my linux box. I even rezipped it but my recovery keeps refusing to start the install process.
I'm a bit stumped here.
Click to expand...
Click to collapse
Have you tried diasabling signature verification?

vnvman said:
Have you tried diasabling signature verification?
Click to expand...
Click to collapse
It's disabled by default. It just says it can't read the .zip file. If I _enable_ verification it says it can't read the footer from the .zip. If I disable verification again it just says "can't open /sdcard/cm_bravo_full-163.zip (bad)".
I also have the same with build 162. I flashed pretty much every cm-nightly in the last few months and now all of a sudden this? What am I doing wrong .
I just installed the miui-desire.zip file again that was on my sdcard and it installed without a hitch. This is getting annoying .
EDIT: Solved it. Apparently there is a bug in my recovery. If I use the recovery the mount my sdcard over USB, afterwards /sdcard can get unmounted. So it couldn't find the .zip file I was choosing because /sdcard was not mounted. Why it was still possible to list the contents on the sdcard is a mystery to me. That must mean the recovery mounts /sdcard, lists the contents and then unmounts it again, and _then_ tries to start the update?!?
Anyway, going into the 'mounts and storage' menu and choosing 'mount /sdcard' suddenly made sure things worked again.
Really stumped how this happened.

dipje said:
It's disabled by default. It just says it can't read the .zip file. If I _enable_ verification it says it can't read the footer from the .zip. If I disable verification again it just says "can't open /sdcard/cm_bravo_full-163.zip (bad)".
I also have the same with build 162. I flashed pretty much every cm-nightly in the last few months and now all of a sudden this? What am I doing wrong .
I just installed the miui-desire.zip file again that was on my sdcard and it installed without a hitch. This is getting annoying .
Click to expand...
Click to collapse
What recovery image are you using? If you have amonRA you might try to fix this launching clockworkmod via fake flash and using that one to install the update. Otherwise if you already have clockwork you might try flashing amonRA via hboot and use that one...at times i can't perform something with one of the two recoveries, and using the other one often solves every issue for me

I Need a root package

hey guys... all the root packages I have seen so far have a survey to download ... I cant do surveys because .. well its a long story .
in a short version .. I am looking for a direct root package download without being troubled in doing a survey .
I would be grateful if some one can help me out

Please don't duplicate posts, it's against the rules. I was already helping you in the other thread you posted in but I'll continue here. The root package you were looking at is most likely not compatible with your current firmware version. What are your bootloader details? I need to see the first five lines.
Sent from my Evita

timmaaa said:
Please don't duplicate posts, it's against the rules. I was already helping you in the other thread you posted in but I'll continue here. The root package you were looking at is most likely not compatible with your current firmware version. What are your bootloader details? I need to see the first five lines.
Sent from my Evita
Click to expand...
Click to collapse
*** UNLOCKED ***
evita pvt ship s off RL
CID-HTC__622
hboot-2.15.0000
radio-1.30a.32.45.18
opendsp-v33.1.0.45.1128

What's your ultimate goal? Do you want to root your current stock ROM or install a custom ROM? Either way you need to install TWRP recovery first. I'm assuming you already have adb/fastboot installed on your PC.
Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you have TWRP recovery on your phone.
If you want to root your current stock ROM you can just flash SuperSU through the install menu in TWRP recovery. You'll find a download link here:
http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip
If you want to install a custom ROM, just find one you like, download it, read the install instructions on the ROM thread, perform a full wipe (cache/dalvik cache/factory reset/system) through the wipe menu in TWRP, then install the ROM through the install menu in TWRP.
Before doing either of these options you should make a backup of your current setup in the backup menu in TWRP. Select system, data, and boot, then swipe to backup.
Sent from my Evita

timmaaa said:
What's your ultimate goal? Do you want to root your current stock ROM or install a custom ROM? Either way you need to install TWRP recovery first. I'm assuming you already have adb/fastboot installed on your PC.
Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you have TWRP recovery on your phone.
If you want to root your current stock ROM you can just flash SuperSU through the install menu in TWRP recovery. You'll find a download link here:
http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip
If you want to install a custom ROM, just find one you like, download it, read the install instructions on the ROM thread, perform a full wipe (cache/dalvik cache/factory reset/system) through the wipe menu in TWRP, then install the ROM through the install menu in TWRP.
Before doing either of these options you should make a backup of your current setup in the backup menu in TWRP. Select system, data, and boot, then swipe to backup.
Sent from my Evita
Click to expand...
Click to collapse
tried to flash recovery ...
"error : cannot load "recovery file name" (openrecovery-twrp-2.6.0.0-evita)
though it is in the same folder of android where I put fastboot and all that stuff..

The command should be:
Code:
fastboot flash recovery openrecovery-twrp-2.6.0.0-evita.img
Sent from my Evita

timmaaa said:
The command should be:
Code:
fastboot flash recovery openrecovery-twrp-2.6.0.0-evita.img
Sent from my Evita
Click to expand...
Click to collapse
oh I forgot the img thing haha
thanks a lot
though now I wanna flash the venom rom (sense 5 , 4.2) and step 3 says : "Confirm the MD5 on the download page matches the MD5 of the file on your phone (ES File Explorer will show the MD5 of the file)" what does that mean ?

If you're downloading the file directly to your phone, use an app called AFV (Android File Verifier) to check the md5. After you've downloaded the ROM just copy the md5 listed on the download site, open AFV, paste the md5 into the box, click the select file button, navigate to the file then long press it and select calculate md5, hopefully it'll say success. If it says anything other than success the download is corrupt.
Sent from my Evita

timmaaa said:
If you're downloading the file directly to your phone, use an app called AFV (Android File Verifier) to check the md5. After you've downloaded the ROM just copy the md5 listed on the download site, open AFV, paste the md5 into the box, click the select file button, navigate to the file then long press it and select calculate md5, hopefully it'll say success. If it says anything other than success the download is corrupt.
Sent from my Evita
Click to expand...
Click to collapse
oh ok thanks alot you are smart you know ?? extremely helpful and nice to have you around the thread

madshark2009 said:
oh ok thanks alot you are smart you know ?? extremely helpful and nice to have you around the thread
Click to expand...
Click to collapse
Thanks, I've just been doing this for a while. Give yourself some time and try to keep up with things and you'll gain a whole lot of knowledge too.
Sent from my Evita

[STOCK] [OFFICIAL EU UNTOUCHED] [MULTI] LeEco Le2 X527 5.9.21s

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] Root your Motorola One Action

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.)

[HELP] Moto G7 Power Rooting via Magisk

Recently, I have been trying to root my Moto G7 Power via Magisk but have run into an issue.
My plan:
1. Using the Magisk Manager, download the Magisk zip file and place it in my phones Internal Storage
2. Using ADB and Fastboot, flash TWRP with the following command: "fastboot flash boot twrp.img"
3. Using twrp on my phone, Install the Magisk zip file
4. Reboot
After rebooting, I was greeted with a slow and infinite switching between black and no LED's on.
What did I do wrong?
Would appreciate any answers, even if they only point me in the right direction

Akte_ said:
Recently, I have been trying to root my Moto G7 Power via Magisk but have run into an issue.
My plan:
1. Using the Magisk Manager, download the Magisk zip file and place it in my phones Internal Storage
2. Using ADB and Fastboot, flash TWRP with the following command: "fastboot flash boot twrp.img"
3. Using twrp on my phone, Install the Magisk zip file
4. Reboot
After rebooting, I was greeted with a slow and infinite switching between black and no LED's on.
What did I do wrong?
Would appreciate any answers, even if they only point me in the right direction
Click to expand...
Click to collapse
In fastboot u need to type fastboot boot (the name of recovery)
make sure the recovery image is in afb folder

roadkill42 said:
In fastboot u need to type fastboot boot (the name of recovery) then enter bottom.make sure the recovery image is in afb folder
Click to expand...
Click to collapse
What do you mean by "then enter bottom"

Akte_ said:
What do you mean by "then enter bottom"
Click to expand...
Click to collapse
Aoto correct I fixed the response

Now TWRP is not prompting for a password to decrypt my internal storage, meaning I cannot access the Magisk zip in there. Any ideas?

Akte_ said:
Now TWRP is not prompting for a password to decrypt my internal storage, meaning I cannot access the Magisk zip in there. Any ideas?
Click to expand...
Click to collapse
I never had that problem try orange fox do u have sdcard? Or u could side load get ofox recovery put in ur afb folder then with phone in fastboot type fastboot boot (orange fox.img) I renamed mine ofox.this should get u into internal storage if still need help go to tellagram group Moto g 7 power support group