Hello, my watch R has 5.1.1 (LDZ22D) stock ROM and it has some problems. I tried factory reset, still not ok. I would like to try flashing again the stock ROM. I have found this thread: http://forum.xda-developers.com/g-watch-r/development/stock-boot-recovery-g-watch-r-t2956964 , i downloaded boot.img, recovery.img and system.img, checked SHA1 but i don't know which version should i try? 5.1.1 (LDZ22D), 5.1.1 (LCA44B), 5.0.2: ??? Are there limitations for downgrade / upgrade ?
And as a guide to flashing...
1. i start watch, swype 11 to 5, so now in fastboot mode i connect to PC, the PC detect the watch as what ?
2. adb devices and if watch is detected i continue.
3. fastboot flash boot boot.img
4. fastboot flash recovery recovery.img
5. fastboot flash system system.img
6. restart
is that ok ?
How long does it take to flash each of those imgs ?
thank you
intersectRaven said:
Notes/FAQ:
1.) I re-mkbootimg-ed them since I'll be uploading 2 x 20+MB files if I didn't. Still has the same SHA1 checksums as the ones being checked by stock ROM so it's safe to flash.
2.) If you're confused on how to download click on the box marked in this pic.
3.) The commands for flashing are as follows:
Boot: fastboot flash boot boot.img
Recovery: fastboot flash recovery recovery.img
System: fastboot flash system system.img
*replace boot.img, recovery.img and system.img with their respective filenames
**how to obtain the fastboot executables and drivers are explained in a separate thread
4.) The system.img provided above are stock and NOT ROOTED. If you want to go completely stock, just flash ALL the 5.0.1 images above.
*only for 5.0.1 since I didn't make a system image for 4.4W.2 or below
Click to expand...
Click to collapse
took that from the link you posted, just conect the watch to the dock while in fastboot mode, search for 15 second adb/fastboot installer, after installing that and the computer detects your watch just follow those steps using cmd and navigating to the directory where the files are at first, remember to install fastboot and adb system wide on the 15 second adb installer
when in fastboot mode the watch is not detected:
C:\Users\user>adb devices
List of devices attached
when i chose "recovery" in fastboot mode (android robot on back with door open and red exclamation mark) i get:
C:\Users\user>adb devices
List of devices attached
410KCHserialnr888 sideload
but the watch says he waits "adb sideload <filename>"
what i am doing wrong ? something else had to be done ?
thank you
you can use adb to boot watch on bootloader, but it is not needed since you can boot into fastboot already, problem is the watch is not detected on fastboot mode, try finding some drivers or something, what i usually do is download cydia impactor and select usb then let it do the driver stuff for me, quote me next time so i can get notified when you respond
Can not go to Recovery mode or Fast boot Mode or Boot up "Black Screen"
but still detect USB mode at PC (device manager)
Must conect to PC:
1.Download and install adb driver
2.Download and install Miphone Module (MiFlash Module)
3.Download Stock miui rom (Fastboot Rom not flashzip rom)
4.extract your fastboot miui download rom (extract file should be one image folder and some flash file.bat)
5.Copy MiFlash.exe from your instalation from step 2 to fastboot rom extract directory
6.Conect your phone to pc
7.Start MiFlash exe from extract directory
8.Browse Fastboot rom when you already extract before from MiFlash.exe Taskbar
9.Choose one method flash from bottom taskbar
10.And Click Flash...wait until 100% succesfull
11.Your Done
Note:Mode Flash All (All Data will erase)
Test under Xiaomi Mi4W
OS:Win.8.1 x64
Hope this is can help
My Regard
Dona55 said:
Can not go to Recovery mode or Fast boot Mode or Boot up "Black Screen"
but still detect USB mode at PC (device manager)
Must conect to PC:
1.Download and install adb driver
2.Download and install Miphone Module (MiFlash Module)
3.Download Stock miui rom (Fastboot Rom not flashzip rom)
4.extract your fastboot miui download rom (extract file should be one image folder and some flash file.bat)
5.Copy MiFlash.exe from your instalation from step 2 to fastboot rom extract directory
6.Conect your phone to pc
7.Start MiFlash exe from extract directory
8.Browse Fastboot rom when you already extract before from MiFlash.exe Taskbar
9.Choose one method flash from bottom taskbar
10.And Click Flash...wait until 100% succesfull
11.Your Done
Note:Mode Flash All (All Data will erase)
Test under Xiaomi Mi4W
OS:Win.8.1 x64
Hope this is can help
My Regard
Click to expand...
Click to collapse
i have tried this method but somehow my phone is still in bootloops. i cant access recovery but fastboot is still possible on the MI 3
bnambiar1997 said:
i have tried this method but somehow my phone is still in bootloops. i cant access recovery but fastboot is still possible on the MI 3
Click to expand...
Click to collapse
bootloops it is ROM Problem maybe You have FLASH with the wrong ROM...
If Success with the right ROM, it is should be Done/Fine, and can not access Recovery Mode Perhaps your Volume Up Button has Broken....
My Regard
bnambiar1997 said:
i have tried this method but somehow my phone is still in bootloops. i cant access recovery but fastboot is still possible on the MI 3
Click to expand...
Click to collapse
Your issue resolved? If not and you don't have recovery then get the latest TWRP recovery and rename it to recovery so the file would be "recovery.img" and put it inside the folder where you have fastboot.exe file.
Now connect your phone to Windows PC and in the same fastboot folder open command prompt (Shift + Right click > then you will see "open command window here" - click on it).
Now type : fastboot devices + enter. If you can see an entry then enter the next command as below
fastboot boot recover.img - This will format the recovery partition with the TWRP and also boot into recovery.
Now you can flash ROM as you want.
Please hit the Thanks button below, if I have helped.
Well, a lot of people wanting to root global miui 11.0.7 and not being able to... So I did it on my Global redmi 7a - MIUI 11.0.7 Global.
Simple though. Apart from whats being said, u can update Magisk to v20.+ after flashing
the 19 version, through the app Magisk Manager automatically installed after flashing.
Prerequisites & Downloads:
- Your bootloader must be unlocked (https://en.miui.com/unlock/)
- ADB and Fastboot -> I did on windows version, maybe can be done on linux...
- patched boot.img for miui 11.0.7 global
- vbmeta.img
- Magisk v19.3 zip -> place it on the root of your external sdcard
This is basically copied from cg730620's post [Guide][Redmi 7A] TWRP, Root with Magisk, Custom ROM [GSI][Pie] and Avedroid's vid
1 - Unlock bootloader and flash stock miui 11.0.7 recovery rom, using miflash 2017
CAREFUL! On the lower right corner check the first option, "clean all", or you may end up with a locked bootloader.
-> exactly the same from the quoted post from now on, what differs is the files and we are only flashing magisk v19.3
"2. Install Minimal ADB and Fastboot
3. Rename patched boot file to boot.img
4. Rename custom recovery file to recovery.img
5. Place boot.img, recovery.img, vbmeta.img in Program Files (x86)/Minimal ADB and Fastboot/ folder
6. Turn off your phone.
7. Reboot phone to fastboot mode by holding Volume-down button while pressing On/Off-button. You know you are in fastboot mode when you see a cartoon bunny.
8. Connect the phone to your PC via USB.
9. On your PC open command prompt and nagivate to ADB folder, or open command prompt window directly from right-click menu in ADB folder; just right-click on empty space and choose 'Open command prompt here'
10. In command prompt, enter the following commands:
Code:
Code:
fastboot flash boot boot.img
Code:
Code:
fastboot flash vbmeta vbmeta.img
Code:
Code:
fastboot flash recovery recovery.img
11. Now reboot to recovery: Press Volume-Up button on your phone and enter the following in command prompt:
or just turn off the phone and reboot by holding Volume-Up and On/Off button (release On/Off when phone turns on, keep holding Volume-Up until you see screen of TWRP recovery)
12. Swipe to allow modifications. If TWRP asks for PIN, enter the PIN code you set for your unlock screen.
13. In TWRP choose Wipe > Advanced Wipe. Select 'Dalvik / ART cache', 'System', 'Data', 'Cache'. Then Swipe to Wipe.
18. In TWRP choose Install. Select the Magisk zip-file on your phone and then Swipe to confirm flash.
Reboot to system, open Magisk, update and there u go.
Same steps of the beginning of Avedroid's video, only with modified boot.img and Magisk Version
https://www.youtube.com/watch?v=NSs08O6uGVI&t=324s
After 16:30 of the video he flashes a custom gsi rom which is not of the interest of this thread, just flash magisk.
Thanks to all who made it possible, especially Avedroid and cg730620
Post questions and answers here, please, NOT in PM.
Good luck!
Thank's it's work fine on custom gsi too, i just flash patch boot, vbmeta, finally install magisk success
I did everything right, however, when it came to installing Magisk, the following error occurred: "Updater process ended with ERROR: 1".
So I redid the whole process, but before installing Magisk I did the following: I went to Mount, I deselected the System partition and after that the installation proceeded normally.
Well, I don’t know if this is the best way to fix this problem, I don’t understand much of these things, but it ended up working for me.
Thanks for the post
I will do some tests to see if everything is working.
Can I just do this on MIUI 11.0.5 Global?
Omborkar said:
Can I just do this on MIUI 11.0.5 Global?
Click to expand...
Click to collapse
Download patched boot.img for ur rom instead of 11.0.7 boot.img I uploaded. Or patch it yourself.
I have a problem. Everytime I do the wipe it says only: "Failed to mount "vendor"(invalid argument)"
What to do?
Google play not certified... after flashing and installed magisk... Got solution??? Thanks
I've rooted my MoKee OS Android 10 rom. Can somebody help me change the system font? The font changer module in Magisk is not appearing in the search bar.
vincecabalan said:
I've rooted my MoKee OS Android 10 rom. Can somebody help me change the system font? The font changer module in Magisk is not appearing in the search bar.
Click to expand...
Click to collapse
I Tried To Root Mokee But Failed. Can You Please Tell Me How You Root Mokee
Hello, what files do I need to rename to boot.img and recovery.img? I'm lost
3. Rename the patched boot file to boot.img
4. Rename the custom recovery to recovery.img
RsAbubokor4 said:
I Tried To Root Mokee But Failed. Can You Please Tell Me How You Root Mokee
Click to expand...
Click to collapse
Extract boot.img of installer mokee.zip Patch boot image https://patcher.yaalex.xyz/ select include magisk Expect to do uploud after downloading rename boot.img sdcard Go twrp flash boot install magisk manager apk
Credit to @idcamper
vincecabalan said:
Extract boot.img of installer mokee.zip Patch boot image https://patcher.yaalex.xyz/ select include magisk Expect to do uploud after downloading rename boot.img sdcard Go twrp flash boot install magisk manager apk
Credit to @idcamper
Click to expand...
Click to collapse
I did according to this advice, uploaded boot.img to this site. Magisk works, but Wifi won't work . When I uploaded boot.img, Wifi works, then it shows that Magisk is not installed, but it was installed.
speed_cars said:
I did according to this advice, uploaded boot.img to this site. Magisk works, but Wifi won't work . When I uploaded boot.img, Wifi works, then it shows that Magisk is not installed, but it was installed.
Click to expand...
Click to collapse
try this process after flash zip of the last magisk from reset factory
Can i do this on miui 11.0.3.0 indian rom based on Android 10. If yes then i need recovery.img pls help.
4. Rename custom recovery file to recovery.img
- where i can download this?, or this is the outcome of step 1?
Everything works fine, exept password. When i set new password, let's say it is 1234, i set the password in the setting, then i press the power button for lock screen, i put the password in as usual, but it just says try again over and over, im pretty sure that it is not my fault. Thanks for reply.
Anyone have patched boot 11.0.4?
jurubebaamarga said:
Well, a lot of people wanting to root global miui 11.0.7 and not being able to... So I did it on my Global redmi 7a - MIUI 11.0.7 Global.
Simple though. Apart from whats being said, u can update Magisk to v20.+ after flashing
the 19 version, through the app Magisk Manager automatically installed after flashing.
Prerequisites & Downloads:
- Your bootloader must be unlocked (https://en.miui.com/unlock/)
- ADB and Fastboot -> I did on windows version, maybe can be done on linux...
- patched boot.img for miui 11.0.7 global
- vbmeta.img
- Magisk v19.3 zip -> place it on the root of your external sdcard
This is basically copied from cg730620's post [Guide][Redmi 7A] TWRP, Root with Magisk, Custom ROM [GSI][Pie] and Avedroid's vid
1 - Unlock bootloader and flash stock miui 11.0.7 recovery rom, using miflash 2017
CAREFUL! On the lower right corner check the first option, "clean all", or you may end up with a locked bootloader.
-> exactly the same from the quoted post from now on, what differs is the files and we are only flashing magisk v19.3
"2. Install Minimal ADB and Fastboot
3. Rename patched boot file to boot.img
4. Rename custom recovery file to recovery.img
5. Place boot.img, recovery.img, vbmeta.img in Program Files (x86)/Minimal ADB and Fastboot/ folder
6. Turn off your phone.
7. Reboot phone to fastboot mode by holding Volume-down button while pressing On/Off-button. You know you are in fastboot mode when you see a cartoon bunny.
8. Connect the phone to your PC via USB.
9. On your PC open command prompt and nagivate to ADB folder, or open command prompt window directly from right-click menu in ADB folder; just right-click on empty space and choose 'Open command prompt here'
10. In command prompt, enter the following commands:
Code:
Code:
fastboot flash boot boot.img
Code:
Code:
fastboot flash vbmeta vbmeta.img
Code:
Code:
fastboot flash recovery recovery.img
11. Now reboot to recovery: Press Volume-Up button on your phone and enter the following in command prompt:
or just turn off the phone and reboot by holding Volume-Up and On/Off button (release On/Off when phone turns on, keep holding Volume-Up until you see screen of TWRP recovery)
12. Swipe to allow modifications. If TWRP asks for PIN, enter the PIN code you set for your unlock screen.
13. In TWRP choose Wipe > Advanced Wipe. Select 'Dalvik / ART cache', 'System', 'Data', 'Cache'. Then Swipe to Wipe.
18. In TWRP choose Install. Select the Magisk zip-file on your phone and then Swipe to confirm flash.
Reboot to system, open Magisk, update and there u go.
Same steps of the beginning of Avedroid's video, only with modified boot.img and Magisk Version
After 16:30 of the video he flashes a custom gsi rom which is not of the interest of this thread, just flash magisk.
Thanks to all who made it possible, especially Avedroid and cg730620
Post questions and answers here, please, NOT in PM.
Good luck!
Click to expand...
Click to collapse
I wish to obtain root / access to magisk,
Wanting to know if I can do this without losing data (having to delete system data)
Thank you
Hello.
So I was trying to root my Redmi 7A - v10.2.1 with TWRP 3.3.1 but now I am stuck in a bootloop.
What I did:
1. Flash boot.img
2. Flash recovery.img
3. Flash vbmeta.img
4. reboot
Phone rebooted to system and TWRP was installed.
Then I booted to TWRP to install Magisk-v23.0.zip,
I went to Advanced Wipe, then wiped 'Dalvik / ART cache', 'System', 'Data', 'Cache'.
When I rebooted, it went into a bootloop, when I go to TWRP it says 'No OS INSTALLED".
What did I do wrong? And how to recover?
Thanks.
Cinox said:
I did everything right, however, when it came to installing Magisk, the following error occurred: "Updater process ended with ERROR: 1".
So I redid the whole process, but before installing Magisk I did the following: I went to Mount, I deselected the System partition and after that the installation proceeded normally.
Well, I don’t know if this is the best way to fix this problem, I don’t understand much of these things, but it ended up working for me.
Thanks for the post
I will do some tests to see if everything is working.
Click to expand...
Click to collapse
Im also getting the same error,, but what do you mean by "deselected the System partition". I see "system_root" in Mount but not "System"
Anybody knows how to root realme C11 with Magisk?
Will this method work in this dvice?
https://forum.xda-developers.com/re...9-mediatek-t4149531/post83310015#post83310015
Mrinalsaha said:
Anybody knows how to root realme C11 with Magisk?
Will this method work in this dvice?
https://forum.xda-developers.com/re...9-mediatek-t4149531/post83310015#post83310015
Click to expand...
Click to collapse
Not tested but will work. If something goes wrong, you can flash you stock boot.img from fastboot.
To get stock boot.img
You can download stock rom from Software Update realme site and decrypt and convert .ozip to .zip with https://github.com/bkerler/oppo_ozip_decrypt
or
Go to stock recovery with power off your device and then hold Volume Down(-) + Power buttons same time to boot into recovery mode.
Connect device to PC, install drivers for realme and setup ADB & Fastboot Tools
Then run following
Code:
adb devices
adb root
adb pull /dev/block/platform/bootdevice/by-name/boot
Then your working directory in your PC will have stock boot image(rename it to boot.img from boot).
This a a simple guide on how to root realme c11 with magisk
Get boot.img from stock rom.
To patch boot.img
>Select Install
>Select Select and Patch a file
>Select stock boot.img in Magisk Manager app and place Magisk Patched boot.img from Downloads folder to PC then do below
>place magisk_patched.img and vbmeta.img in platform tools folder in your PC
}connect phone in fastboot mode, open Command window and run
>fastboot devices
>fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
>fastboot flash boot magisk_patched.img
>fastboot reboot
Finally Open Magisk Manager, do initial setup and then after reboot do magisk hide in Magisk Manager settings.
Bootloader of your phone should be already unlocked and usb debugging should be enabled before doing this
I have attached vbmeta.img and magisk_patched.img of RMX2185_11_A.79
Use my magisk_patched.img only if you are using RMX2185_11_A.79(check in software update)
Here is vbmeta ang magisk_patched.img for RMX2185_11_A.79
Gofile - Free Unlimited File Sharing and Storage
Gofile is a free, secure file sharing and storage platform. With unlimited bandwidth and storage, you can easily store and share files of any type without any limits. Our advanced features, such as CDN support and password protection, make Gofile the ideal choice for individuals and businesses...
gofile.io
Reposting here (from the Magisk forum) on the advice of a Senior Moderator.
I have a Pixel 5 and two days ago now I updated from redfin-2110-rq3a.211001.001-factory-23f4cec2 to redfin-2111-sp1a.211105.004-factory-749e8f9f (yes the Aus version), i.e. from the October version to the November version.
All went well until I tried to root the device using Magisk - something I've done *many* times. The trouble is that after I flashed the patched boot.img, the device would not boot - it started to for a few seconds and then went back into fastboot mode.
I've tried a few times but always the same result.
And it seems that you cannot rollback to the October release - the flash-all.sh completes OK but the subsequent boot hangs.
BTW (1): I'm still using the canary channel, is this still necessary?
BTW (2): I also posted in the github Magisk issues page and that issue was promptly closed with the comment "format data". Really?!
Help.
Curiouser and curiouser: this works
adb reboot bootloader
fastboot boot redfin-2111_boot_magisk_patched.img
gone_bush said:
Reposting here (from the Magisk forum) on the advice of a Senior Moderator.
I have a Pixel 5 and two days ago now I updated from redfin-2110-rq3a.211001.001-factory-23f4cec2 to redfin-2111-sp1a.211105.004-factory-749e8f9f (yes the Aus version), i.e. from the October version to the November version.
All went well until I tried to root the device using Magisk - something I've done *many* times. The trouble is that after I flashed the patched boot.img, the device would not boot - it started to for a few seconds and then went back into fastboot mode.
I've tried a few times but always the same result.
And it seems that you cannot rollback to the October release - the flash-all.sh completes OK but the subsequent boot hangs.
BTW (1): I'm still using the canary channel, is this still necessary?
BTW (2): I also posted in the github Magisk issues page and that issue was promptly closed with the comment "format data". Really?!
Help.
Click to expand...
Click to collapse
Sorry, but you are going to have to wipe your phone here. On the next updates you won't have to following these instructions.
Get the vbmeta.img from the factory image (the same place you got the boot.img) and put it into your fastboot folder.
In bootloader/fastboot enter:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Then enter:
fastboot -w (<---this wipes your phone)
Then flash the patched boot image as you normally would and reboot.
In the future for updates, download both the ota.zip and the factory image. Pull the boot.img from the factory image and patch it. Pull the vbmeta.img and put it into your fastboot folder with the patched boot.img. Sideload the OTA and when the flash is done, boot to bootloader using the volume/power buttons on your phone from recovery (you'll be there to sideload the ota.zip) IF YOU BOOT TO /SYSTEM YOU'LL HAVE TO WIPE AGAIN!
Flash the vbmeta.img with fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img, then flash the patched boot.img and reboot. You won't have to wipe again as long as you don't boot to /system and don't forget to flash the vbmeta.img with disabling verity and verification.
xunholyx said:
Sorry, but you are going to have to wipe your phone here. On the next updates you won't have to following these instructions.
Get the vbmeta.img from the factory image (the same place you got the boot.img) and put it into your fastboot folder.
In bootloader/fastboot enter:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Then enter:
fastboot -w (<---this wipes your phone)
Then flash the patched boot image as you normally would and reboot.
In the future for updates, download both the ota.zip and the factory image. Pull the boot.img from the factory image and patch it. Pull the vbmeta.img and put it into your fastboot folder with the patched boot.img. Sideload the OTA and when the flash is done, boot to bootloader using the volume/power buttons on your phone from recovery (you'll be there to sideload the ota.zip) IF YOU BOOT TO /SYSTEM YOU'LL HAVE TO WIPE AGAIN!
Flash the vbmeta.img with fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img, then flash the patched boot.img and reboot. You won't have to wipe again as long as you don't boot to /system and don't forget to flash the vbmeta.img with disabling verity and verification.
Click to expand...
Click to collapse
Thank you for your reply. Some questions:
1) What's changed that required a wipe? (Let's face it, it's a MAJOR PITA! Thankfully, I do use TitaniumBackup )
2) You state "download both the ota.zip and the factory image" - what's the difference?
3) Re "Pull the vbmeta.img" - in the current instance, is that from the November file (SP1A.211105.004), if not, from where?
4) Do I have this right for future updates?
* Unpack the downloaded file and put the boot.img and vbmeta.img files in a safe place
* Sideload the update by
adb reboot recovery
Apply update from ADB
adb sideload <ota-update.zip>
* Use volume buttons to boot into bootloader (booting into system will mean I'll have to do another wipe!)
* fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
* flash patched boot.img
* boot
5) Re using Magisk to patch the boot.img: can, say, the November boot.img be patched whilst the phone is running the October update?
Yeah, I know, answering my questions is all you've got to do with your life
1: verified boot is needed in Android 12. Patching the boot.img breaks the signature from Google
2: after flashing the factory image in fastboot you're promoted to press any key to continue, which boots the phone to system iirc (I could be mistaken ~ it's been over a year since I flashed a factory image). You can boot to bootloader from recovery after you sideload the OTA.
3: yes. From the update you are applying.
4: I guess.... Place the vbmeta.img in your fastboot folder the same as the patched boot.img (at least that's where I always put the patched boot.img). Put the pulled boot.img wherever you like to transfer it to your phone from to patch. The rest after that part is correct.
5: yes
EDIT: (Sorry I forgot to use the reply button)
xunholyx said:
1: verified boot is needed in Android 12. Patching the boot.img breaks the signature from Google
2: after flashing the factory image in fastboot you're promoted to press any key to continue, which boots the phone to system iirc (I could be mistaken ~ it's been over a year since I flashed a factory image). You can boot to bootloader from recovery after you sideload the OTA.
3: yes. From the update you are applying.
4: I guess.... Place the vbmeta.img in your fastboot folder the same as the patched boot.img (at least that's where I always put the patched boot.img). Put the pulled boot.img wherever you like to transfer it to your phone from to patch. The rest after that part is correct.
5: yes
EDIT: (Sorry I forgot to use the reply button)
Click to expand...
Click to collapse
Thank you for yor replies and time - much appreciated!