Develop Bugs

[Win32 Tool]GUI One Click Root and UN-Root / VZW / US ONLY / DOWNLOAD ADDED

!!Check out the Video on how it works!!!
http://www.youtube.com/watch?v=ZANt0vaiZYs
[Disclaimer]:
The method of rooting your Android device as described below is solely by your choice and your choice only!
IT WILL WIPE YOUR DATA. IT WILL WIPE YOUR DATA. IT WILL WIPE YOUR DATA.
I, XDA, and other forum members claim no liability for any harm that may come to your device, including, but not limited to: bricked phones, voided manufacturer warranties, bootloops, loss of data, etc
While generally this software is safe, and does have fail safe and error checking, it does not mean that something can/shell/or will not go wrong. Please be prepared if it does.
[/Disclaimer]
[Information]:
Device Supported:
MZ600 VZW 3G/4G
Software Supported:
3.0 Build HRI39
3.0.1 Build HRI66
3.1 Build HMJ37
Method Used:
Fastboot oem unlock
Unsecured boot.img for device software.
Features:
Fast and easy 1 click root method for supported sw.
Error checking to prevent mistakes as much as possible.
Takes 5-8 Mins to Unlock/Root device.
Install's SU and Superuser.apk
Detects Software version to version selected, helps install correct files needed.
Other Information:
This will WIPE ALL USER DATA.
Tested with:
3.0 Build HRI39
3.0.1 Build HRI66
3.1 Build HMJ37
I have personally restored to all three version's of the software and tested root and unlock on all software version's. This should/will work as long as you follow instructions. Its really not hard, and its hard to mess up.
[/Information:]
I know there is just a WIFI Version and I will add support later. It will auto detect you're phone mode.
{
"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"
}
[DOWNLOAD LINK HERE]
Download Here DO NOT POST ON OTHER FORUMS IF ITS POSTED ON OTHER FORUMS I WILL REMOVE LINK AND STOP SUPPORT THIS IS FOR XDA ONLY!
Download Unroot_tools, please extract into the unroot_tools folder.
If you use this software please leave feedback.

Supported Devices:
US VZW 3G/4G on either 3.0/3.0.1/3.1
Support for other devices planed:
US VZW WIFI on either 3.0/3.0.1/3.1
EU Xoom's
Support to flash Clockwork Recovery is planned.
Support to install new framework for SMS/MMS/UAString on either 3.0/3.0.1/3.1
*I will not enable phone features untill a phone app can be used, i use another carrier other then VZW and I myself would like to be able to use the phone feature as well but can't untill a new phone.apk is compiled for honeycomb or one comes out that works with it*

Looking pretty smooth. Just took the plunge to root via adb though.
The unroot method will let you lock without getting any LNX errors,?

The LNX error from what I seen is because the device needs to be unlocked again in order to boot.
Ill have too check it out again, I restored mine last night and received this LNX error. The way to recover was to boot fastboot by shutting the device off first VOL UP + PWR let it stay off for a min then boot into fastboot by VOL UP + PWR this kicked me into fastboot and running the cmd fastboot oem unlock my device was able to boot properly without an issue.

I am assuming the device cannot be locked and boot because the img files are not signed files from Motorola? I ran into this problem recently while trying to revert back to stock and locked to give the video app a try. I had a terrible experience with LNX 0x0004. Pretty severe brickage. Kinda scurry thought I had a high dollar paper weight.
amoamare said:
The LNX error from what I seen is because the device needs to be unlocked again in order to boot.
Ill have too check it out again, I restored mine last night and received this LNX error. The way to recover was to boot fastboot by shutting the device off first VOL UP + PWR let it stay off for a min then boot into fastboot by VOL UP + PWR this kicked me into fastboot and running the cmd fastboot oem unlock my device was able to boot properly without an issue.
Click to expand...
Click to collapse

Yes, sorry still at work so short answers.
From what it seems is that you have to return completely to stock images, even then it might now work. From what it seems the application the removes the lock might also implement security in order to prevent from being locked again.
While the lock method works for some I think its all dependent on when people got their xoom. Mine is new and came loaded with latest software.
I think you hit it right on the nail. I think that even returning back to stock because the images and boot partitions have been modify the device will fail to boot. I have tried RSDLite to restore the SBF all the way from version 4.8 to 5.3.1 and it will not restore it fails each time. Only way to recover it was to re unlock the device and the device booted fine.
Tried to relock again and it failed to boot.

W00t just what we need...

It should be much more difficult for them to brick there device with this tool. As the user isnt using a 1 click method made for 1 version of the system.
The problem with the 1 click's out is currently they flash 1 boot.img for only 1 system either 3.0 or 3.01 this cause the device to hang at boot then people thinking something went wrong.
The program is designed with error checking in mind.
As seen in the video I show you this by purposely selecting the wrong software version, it notify's me that i'm trying to install the wrong boot.img for the a mismatched version of the os.
Also i was receiving the LNX errors before when trying to relock the device i figured out a good method and it will be implemented.

This is amazing if this works flawless, and I'm Super new to android, and I just bought a Xoom, I'm curious what does Rooting do for the device?, also why do people try to Un-Root for?

This is 3G only?

Yes 3G only, once the 3G is completly done ill focus on the WIFI version. I do not have a WIFI version myself so it will be based of whats posted.

Bad ass! Can't wait for wifi version! Great work
Azrael X 4.0

Can you tell me where the download link is?

Its comming as soon as i fix the MD5 Checks for the files and images.

Download Link Added.

Thanks op, I used this to unroot my xoom and it worked perfectly.

Thank you for the reply glad you liked it.

I'm eagerly awaiting the WIFI version! Woot!
Sent from my SAMSUNG-SGH-I897 using XDA Premium App

I dont have a WiFi version so I need someone with adb experience so that I can implement a wifi version.
I take it just need the right boot images as well for the wifi version as there seems to be some hardware differences. But i need someone who can adb the device and get me some getprop information so that i can implement the wifi version of the device. I have rooted and unrooted my device over 20 times with this tool. Its fast and easy to use. I actually just updated it again with a new help box when it gets to fastboot oem unlock. I will have to also add one for the fastboot oem lock feature as I think I forgot to add that one.
Anyway.
If you have used this software Please Please leave feedback so that other users can see the success to fail rate. *THERE SHOULDNT BE ANY FAIL RATE* but if it fails i need to know so i can fix what ever it didnt do.

Will u not being doing this for EU xooms?

XAA/XAA/VZW - Texting Issue

Hey all,
I followed the guide at https://forum.xda-developers.com/galaxy-s8/how-to/rd-carrier-switch-root-snapdragon-t3597473/page66 starting with a stock Verizon S8 plus
But ended up screwing something up and ended up with XAA/XAA/VZW instead of XAA/VZW/VZW and now I can not send any text messages.
I did enable all bands from within *#2263#, but I only have the options of LTE/3G/2G when looking at the network mode.
Just wondering if anyone ended up in the same spot I am and how you resolved it (without returning the phone)

sniper7kills said:
Hey all,
I followed the guide at https://forum.xda-developers.com/galaxy-s8/how-to/rd-carrier-switch-root-snapdragon-t3597473/page66 starting with a stock Verizon S8 plus
But ended up screwing something up and ended up with XAA/XAA/VZW instead of XAA/VZW/VZW and now I can not send any text messages.
I did enable all bands from within *#2263#, but I only have the options of LTE/3G/2G when looking at the network mode.
Just wondering if anyone ended up in the same spot I am and how you resolved it (without returning the phone)
Click to expand...
Click to collapse
Did you flash XAC with CSC, reboot and flash XAC Home_CSC, then flash VZW with home_CSC only? Are you using Princeton?

sniper7kills said:
Hey all,
I followed the guide at https://forum.xda-developers.com/galaxy-s8/how-to/rd-carrier-switch-root-snapdragon-t3597473/page66 starting with a stock Verizon S8 plus
But ended up screwing something up and ended up with XAA/XAA/VZW instead of XAA/VZW/VZW and now I can not send any text messages.
I did enable all bands from within *#2263#, but I only have the options of LTE/3G/2G when looking at the network mode.
Just wondering if anyone ended up in the same spot I am and how you resolved it (without returning the phone)
Click to expand...
Click to collapse
I'm sitting in the same boat. I did have everything working and wanted to updated to the newest vzw firmware but wouldn't let me do a straight update, as ODIN kept saying Model mismatch. So I started the process over with the newest vzw firmware and now am stuck at XAA/XAA/VZW.
Also tried going back full VZW firmware and that is not happening.
Also after following the guide and everything is flashed, I cannot go in a flash the same Home CSC file from the vzw firmware as it tells me there is a model mismatch still

VinylJStar said:
Did you flash XAC with CSC, reboot and flash XAC Home_CSC, then flash VZW with home_CSC only? Are you using Princeton?
Click to expand...
Click to collapse
Yes, I did in that order; and I used Odin PrinceComsy 3.12 to flash XAC as I had a md5sum issue in Odin 3.12.7 and then had to use Odin 3.12.7 for VZW as I kept getting a model mismatch in PriceComsy.
PrinceComsy that I have has an MD5 sum of 91a4593ebdba14268ee719e7a5e04e8e
Oden 3.12.7 that I have has an MD5 sum of 5162c42e934b7efbf353e3837ccb0ba3
If you used something that was different can you provide a link?
pimpmaneaton said:
I'm sitting in the same boat. I did have everything working and wanted to updated to the newest vzw firmware but wouldn't let me do a straight update, as ODIN kept saying Model mismatch. So I started the process over with the newest vzw firmware and now am stuck at XAA/XAA/VZW.
Also tried going back full VZW firmware and that is not happening.
Click to expand...
Click to collapse
I would agree, What about Visual Voicemail? When I try to launch it it simply says "not supported".
So far its just the verizon bloat thats removable and outbound text messages that aren't working.

I'm noticing a lot of people having issues. Where are you getting your versions of the custom Odin? It might be something to do with that. I'll upload the one I got that worked for me tonight with the exact steps I took. Maybe that will help some people.

cadcamaro said:
I'm noticing a lot of people having issues. Where are you getting your versions of the custom Odin? It might be something to do with that. I'll upload the one I got that worked for me tonight with the exact steps I took. Maybe that will help some people.
Click to expand...
Click to collapse
I used the Prince Comsy version and the first time I did this is worked fine. But I installed an older version of the VZW firmware and did not have the new advanced display color control. So I tried to just update to the newest one in the Prince Comsy ODIN and gave me a Model Mistmatch error. So I figured I would bite the bullet and do the process over again but use the newest firmware, and am now stuck at this point. I have re-done the process 5 times now and no matter what I am still ending up with XAA/XAA/VZW and no network, IMS is not registering and not out bound text. Also there seems to be no way to go back to full stock and when I flash through ODIN, it goes to the blue Installing Update screen and errors out at 32% every time.

cadcamaro said:
I'm noticing a lot of people having issues. Where are you getting your versions of the custom Odin? It might be something to do with that. I'll upload the one I got that worked for me tonight with the exact steps I took. Maybe that will help some people.
Click to expand...
Click to collapse
Honestly; I don't recall 100% but it would have been from a link posted to XDA-Developers.
Firmware wall all retrieved from sammobile or from links posted here as well.
Please do update and share that link when you get a chance.
Fingers crossed that a straight XAA firmware comes out in the next week that will resolve this issue, and bypass the need for XAC all together.
pimpmaneaton: I have the same exact issue at 32%.

Sorry about the wait guys, I'm in the process of moving into a new place so paperwork is a plenty.
Anyways, here's the version that I downloaded from a thread on XDA.
http://www.mediafire.com/file/26modnk5c01n96h/Odin3_v3.12_PrinceComsy.zip
Also here are the exact steps I took when flashing the multiple firmwares. I actually did this all through the comsy version of Odin.
1: I reset and formatted my phone from the settings menu option, and let it do it's thing.
2: I flashed the Canadian XAC firmware over the phone, and selected the default CSC file. DO NOT use the Home_CSC file for this flash.
2a: enabled the PIN to unlock AND power on the device. No accounts, extra settings or add ons.
3: Once the setup was finished, I went to the Dev settings and enabled USB debugging
4: After that I went into the phone settings menu and enabled all LTE bands and saved my settings.
5: Once that was all done, I used ADB to boot the phone into download mode and selected the stock VZW firmware, and made sure to select the Home_CSC this time
After a few minutes the phone booted up and the setup menu was the same as it was in the Canadian version. I went through all that while connected to Wifi added my accounts and logged everything in, etc. Once it was at the home screen, after maybe 20 seconds it gave me a popup to select the Global network type. Once I selected it, it took maybe another minute or two until I started getting signal and LTE. I sent a test message and I was able to send and receive texts just fine. Data is also working perfectly, as well as calls. Hopefully everything keeps working fine, but as of now everything has been working smoothly.

cadcamaro said:
Sorry about the wait guys, I'm in the process of moving into a new place so paperwork is a plenty.
Anyways, here's the version that I downloaded from a thread on XDA.
http://www.mediafire.com/file/26modnk5c01n96h/Odin3_v3.12_PrinceComsy.zip
Also here are the exact steps I took when flashing the multiple firmwares. I actually did this all through the comsy version of Odin.
1: I reset and formatted my phone from the settings menu option, and let it do it's thing.
2: I flashed the Canadian XAC firmware over the phone, and selected the default CSC file. DO NOT use the Home_CSC file for this flash.
2a: enabled the PIN to unlock AND power on the device. No accounts, extra settings or add ons.
3: Once the setup was finished, I went to the Dev settings and enabled USB debugging
4: After that I went into the phone settings menu and enabled all LTE bands and saved my settings.
5: Once that was all done, I used ADB to boot the phone into download mode and selected the stock VZW firmware, and made sure to select the Home_CSC this time
After a few minutes the phone booted up and the setup menu was the same as it was in the Canadian version. I went through all that while connected to Wifi added my accounts and logged everything in, etc. Once it was at the home screen, after maybe 20 seconds it gave me a popup to select the Global network type. Once I selected it, it took maybe another minute or two until I started getting signal and LTE. I sent a test message and I was able to send and receive texts just fine. Data is also working perfectly, as well as calls. Hopefully everything keeps working fine, but as of now everything has been working smoothly.
Click to expand...
Click to collapse
Thank for the upload; but its the same version I already have.
So I tried to do a Manual software Update (Settings->Software Updates->Download updates manually) check and i noticed something weird;
"Current Version: G955USQU1AQD9/955UOYN1AQD9/G955USQU1AQD9"
What do each of those build numbers mean?
I'd assume one is the bootloader, one is the the radio, and one is the android version???

guess ill wait for unlocked s8+ firmware and try that, maybe the next verizon update will fix the Xaa/Xaa/Vzw issue

So I just wanted to let you guys know that I sent my phone off to Samsung. Because the Knox hasn't been tripped, the warranty is still valid. So I will let you guys know what they do as far as repairing the phone's software.
Sent from my VS988 using Tapatalk

I'm waiting until the unlocked S8+ releases. I'll try that firmware.
Sent from my Nexus 6P using Tapatalk

Try this flash COMBINATION_FA70_G955USQU1AQD8_CL11249373_QB13326524_REV00_user_mid_noship_MULTI_CERT.tar.md5 and then enable usb debugging and open adb shell and type in echo "VZW" > /efs/imei/mps_code.dat and reboot and flash the full verizon files and bl, ap, cp, home csc, and user data should get you back to vzw/vzw/vzw

Whats the chance someone knows about the SM-G955U1 ?? http://updato.com/firmware-archive-select-model?exact=1&q=SM-G955U1

sniper7kills said:
Whats the chance someone knows about the SM-G955U1 ?? http://updato.com/firmware-archive-select-model?exact=1&q=SM-G955U1
Click to expand...
Click to collapse
its the unlocked firmware, just flashed it. went through a whole sim config thing. It did not complete successfully but I'm going to keep trying. SmS confirmed working on this firmware.

Seems legit will contain testing.
{
"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"
}
Sent from my SM-G955U1 using Tapatalk

Factory reset fixes that problem

Just wanted to provide an update to everyone as well...
Using PrinceComsy Odin, I was able to flash the XAA version of 955U1.
I used the NON-HOME csc file (Didn't have anything I wanted/needed to save) and its working like a champ.
I did have one weird pop-up about "installing features based on the new sim card that was inserted" but no errors.
Beyond testing if visual voicemail works from verizon, I'm happy to report my phone is fully operational Texting-wise.

I have the 955U1 downloaded but I am still using the Canadian FW with Verizon features enabled. Can I just flash over this one with the new firmware and be good to go? Or is there a certain method to doing so.

cadcamaro said:
I have the 955U1 downloaded but I am still using the Canadian FW with Verizon features enabled. Can I just flash over this one with the new firmware and be good to go? Or is there a certain method to doing so.
Click to expand...
Click to collapse
Curious about this too, as im also on the Canadian firmware.

How to downgrade from Android Q beta

My Pixel 2XL has locked bootloader and from yesterday I'm having some issues with touchscreen not responding. I spill some coffee on display - just a few drops of cold coffee - but quickly wiped out. The phone was OK, but in the evening the touchscreen stopped working. My first impression was that's a beta issue and so I manually wiped device but it didn't help, the screen is still not reacting.
So before I tear device to see it's not a hardware issue I would like to try to downgrade to stable android 9. Because bootloader is locked my only option is to update/downgrade via ADB, but because official OTA for Android 9 is older ADB is not allowing me to downgrade.
From what I read, rolling back to stock involves sing-off from the beta program on Google's website and wait for another OTA to revert to stock, but because I wiped the device and can't even set the system up and running I won't get it.
Maybe someone can provide such OTA file? Or maybe I'm doing something wrong.
Please, guys, help me out.

Files are here https://developers.google.com/android/images

Droid_Nut said:
Files are here https://developers.google.com/android/images
Click to expand...
Click to collapse
Because my bootloader is locked I just can't flash system image and so far there's no method to unlock Verizon variant. Only OTA newer than Q beta4.

What happens when you try to wipe/format data from the recovery partition? Having a corrupt system/OS shouldn't have affected the recovery partition and/or the ability to format and wipe it to a stock state...
But, if anything, you might have some luck downloading the OTA system image (can still be found at the developers site of Google's), loading up the stock recovery (don't worry if you get a dead droid with an exclamation/triangle, it's supposed to show that, you just need to hold Power + Volume-Up at the same time), and running through the selection of "Apply update from update" and/or "Apply update from .zip" where you can now either point to the OTA .zip manually or "push" the file onto your device...
Using the stock recovery to either wipe/format the device or manually applying the OTA seems to be the only rescue method available to locked bootloader devices...
Good luck to you and I hope this helps...

Opt out the beta program on the web and the phone will "upgrade" down to Pie. That's how I did it.
Did a quick search and found article on doing it https://lifehacker.com/how-to-safely-opt-your-device-out-of-the-android-q-beta-1833378770

Adb sideload the stock P ota.
Or opt out then check for update, it'll download and flash back to P but your data will be wiped.

Edmontonchef said:
Adb sideload the stock P ota.
Or opt out then check for update, it'll download and flash back to P but your data will be wiped.
Click to expand...
Click to collapse
My touchscreen doesn't work, so I can't pass the initial set-up.
I just hope Google will release DP5 within a couple of weeks. Or maybe the touchscreen is broken? I guess I have to wait.
BTW Now I'm rocking old Lumia 550 on WM10 and it's a real pain in the a.ss without google services.

lywyn said:
Opt out the beta program on the web and the phone will "upgrade" down to Pie. That's how I did it.
Did a quick search and found article on doing it https://lifehacker.com/how-to-safely-opt-your-device-out-of-the-android-q-beta-1833378770
Click to expand...
Click to collapse
The problem is that with the unresponsive touchscreen I can't go true initial set-up process and my device is not connected to google account. So it just can't receive un-roll OTA.

Maybe someone could upload it's "un-roll" OTA. So I could try to flash it and find out is it software or hardware issue.

adamszostek said:
The problem is that with the unresponsive touchscreen I can't go true initial set-up process and my device is not connected to google account. So it just can't receive un-roll OTA.
Click to expand...
Click to collapse
Supposedly using the stock recovery, adb, and OTA .zip image doesn't require touchscreen as it requires the use of the physical buttons; to boot to bootloader, select recovery, pop up the recovery menu, select within that menu, select the confirmation prompts, and of course adb requires the computer and its keyboard.... so, thoroughly considered, this method of the "unresponsive touchscreen" shouldn't cause any issues...

adamszostek said:
The problem is that with the unresponsive touchscreen I can't go true initial set-up process and my device is not connected to google account. So it just can't receive un-roll OTA.
Click to expand...
Click to collapse
Since the Pixel 2 XL is IP67 rated you could immerse the phone in cold coffee for a few seconds without damage.
"IP67 means the unit can be dropped into a body of water up to a meter deep for half an hour and is resistant to dust."

lywyn said:
Since the Pixel 2 XL is IP67 rated you could immerse the phone in cold coffee for a few seconds without damage.
"IP67 means the unit can be dropped into a body of water up to a meter deep for half an hour and is resistant to dust."
Click to expand...
Click to collapse
I know that, but IP rating doesn't mean that your phone is absolutely 100% safe, and maybe this time I got run out of luck.
I'm just patiently waiting for beta 5 to be announced and then we'll see.

simplepinoi177 said:
Supposedly using the stock recovery, adb, and OTA .zip image doesn't require touchscreen as it requires the use of the physical buttons; to boot to bootloader, select recovery, pop up the recovery menu, select within that menu, select the confirmation prompts, and of course adb requires the computer and its keyboard.... so, thoroughly considered, this method of the "unresponsive touchscreen" shouldn't cause any issues...
Click to expand...
Click to collapse
It's exactly like You said. I'm able to flash Android Q beta DP4 OTA, but after rebooting I'm stuck at welcome screen and the touchscreen doesn't work.
But once, when I removed the SIM card and popped it right back, a popup window for SIM unlock appeared and I was able to input pin (after that screen got frozen), so I believe that's not a hardware issue. I just have to wait for DP5 and find out is it gonna help or not.

Use an external mouse via USB adapter to pass the welcome screen etc

siggey said:
Use an external mouse via USB adapter to pass the welcome screen etc
Click to expand...
Click to collapse
I didn't know that. Thanks for the tip.

siggey said:
Use an external mouse via USB adapter to pass the welcome screen etc
Click to expand...
Click to collapse
So I did. With the mouse, I was able to sign in Google account and unroll from the beta program. I immediately received OTA with android 9 form June, but after a downgrade, my touchscreen still doesn't work.
How the heck is it possible? The screen is connected to the motherboard with only one ribbon, so if that ribbon would be defective, the screen should not turn on or have some artifact.
So far it's working OK, except for some strange glitch with "day widget".
{
"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"
}
Any suggestions? Should remove the screen and see what's inside? I guess that's the only option left.

Probably your screen is broken and you need a new one. Warranty?

siggey said:
Probably your screen is broken and you need a new one. Warranty?
Click to expand...
Click to collapse
Nop, device bought in Best Buy i NY. So would have to bring it overseas from Europe, because in my country Google doesn't sell devices.

New Redmi Note 8 Pro Unbrick/Hardbrick Removal method- No authorized Service Account

I was trying to unbrick my Xiaomi redmi note 8 pro, i have bricked it twice before and both times had to pay someone with an authorized Xiaomi Service Account, well this time i figured id wait for someone to come out with a method that works and id just use my samsung phone until then, well i waited and waited , and eventually i see the mega tread with the anti-brick in it. I was happy but for the few poor schmucks out there that never had a chance to flash that beautiful set of files i found a way out without paying someone to fix your screw ups.
Anyway I've tried lots of things to unbrick it, removing the battery , replacing the battery anything to get my back to fast boot. I've attempted flashing stock a countless amount of times in different ways and today i needed money very bad to pay some bills so i figured id try to fix it one last time so i could sell my note 10 +. I never had a chance to install the antibrick or whatever it is so theres no way this is just a fluke. I would like to give myself no credit anything here besides finding the files and making the guide. I feel bad because people are charging 35 bucks to practically login for you, and id really be a bad guy if i didnt post what ive found today. Well enough of the backstory here's a guide and ill link what worked.
I will provide the download for all the files you will need here.
https://drive.google.com/file/d/1RWwwUEZJnxmSzZMbFj5_zJaGQ1OJAFo5/view?usp=sharing
This guide is for the Global Version but its the same on all your just sub out the global ROM I've provided with my other files for the one in your region
After you have the zip file containing the files needed do as follows.
1. Uninstall your Current Mi-flash / MiFlashpro
2. Extract the .zip folder
3.Install The Miflashpro that i have in the zipped folder
4. Launch Miflashpro and login.
5.After your are logged in launch Spflash.
6. Inside SpFlashTool click the options tab in the top bar, second column from the left , then click options to open the settings , click general, then in the general tab you want to make sure check lib da match is unticked.
7. Now to begin flashing, Match up the .da file and the .auth file with the ones in the special sauce folder of the zip folder you downloaded , after thats its like installing stock "normally", if you are on global the scatter file is in globalromfiles/images directory.
8. When everything is setup simply click download.
9. As a few disclaimers I tried 6 or 7 times before it worked, i dont remember if i had spflashtool set to firmware upgrade or download download only, i will also state that it failed ounce or twice in both, i just held power and volume up until it cycled i head the ding on my pc letting me know windows picked it up and i had device manager open so i could see the mtk preloader and com ports, i was very surprised when it worked but it did. Anyway if this helped anyone please spread the work so people can know that there phones are not at the mercy of someone else's login. If you have any questions or issues please reply to the post ill respond as quick as i can. I'm not a developer just a modder if anything. I know basic python and how to screw up my phone stumbling upon a fix took me weeks or months even of on and off boredom spikes but this worked for me.
Anyway if this helped at all spread the work , and feel free to donate to me on cash app $KaozCash

hi
works with 64gb and 6gb ram version?

Rebellion747 said:
works with 64gb and 6gb ram version?
Click to expand...
Click to collapse
Yes That is what i originally did it on , the begonia model

It Doesn't Work For Me!
I Followed The Steps But Once Again Keeps Having Authorization Problem With The Account!

angrypandagr said:
It Doesn't Work For Me!
I Followed The Steps But Once Again Keeps Having Authorization Problem With The Account!
Click to expand...
Click to collapse
What code is it giving you, I don't have an authorized account and never flashed preloaded in fact I bricked it before that was released

sawclan22 said:
What code is it giving you, I don't have an authorized account and never flashed preloaded in fact I bricked it before that was released
Click to expand...
Click to collapse
This Error "BROM error status_brom_cmd_send_da_fail (0xC0060005)"
Which Is The Error For Not Authorized Account!

angrypandagr said:
This Error "BROM error status_brom_cmd_send_da_fail (0xC0060005)"
Which Is The Error For Not Authorized Account!
Click to expand...
Click to collapse
Okay like I said I revived that error three or 4 times before it worked give me a second to look at the files and see what I did, if I may ask you followed all the steps exactly, for example you clicked firmware upgrade instead of download

sawclan22 said:
Okay like I said I revived that error three or 4 times before it worked give me a second to look at the files and see what I did, if I may ask you followed all the steps exactly, for example you clicked firmware upgrade instead of download
Click to expand...
Click to collapse
I hate to ask but I need a test subject this worked for me but I may have left something out in my steps I could just brick my phone again a try it again myself, but it probably wouldn't be the same because the first the I did after making this thread flash the abtibrick lk and preloader, if you have some alternate way I can talk to you without using this thread I would love to fix it for you if I can, I want this guide the be revised to be a simple but highly detailed guide on how to fix this issue, it worked for me when I did it and I want to be able to help others. I just need someone else with a bricked device to test it too and for me to make sure that it's exactly what I did.

Thanks from my heart
bro your method if it works thank you very much, you saved me

Rebellion747 said:
bro your method if it works thank you very much, you saved me
Click to expand...
Click to collapse
Did you end up fixing your device? I figure if people report back success than more people will see it

Not working
I followed your instructions and did it several times but nothing seems to work for me
.
{
"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"
}
Please find a alternate way or help me.
Thanks for the thread .

RanaDARK said:
I followed your instructions and did it several times but nothing seems to work for me
.
Please find a alternate way or help me.
Thanks for the thread .
Click to expand...
Click to collapse
Odd two people reported no success there's no way it was some kind of fluke for me , I don't believe in that kind of technical luck, is there anyway I could talk to you in real time I would lik to see first hand what's going on

It would be great if someone could confirm that this works, or would talk with OP and they would try to sort it out together. OP clearly wants to help others, and I am curious if there really is a solution to bricking this phone.

Lajbymester said:
It would be great if someone could confirm that this works, or would talk with OP and they would try to sort it out together. OP clearly wants to help others, and I am curious if there really is a solution to bricking this phone.
Click to expand...
Click to collapse
have you guys tried to use edl? if not, try doing edl mode

Please
Hello, could you tell me the contact privately if you need who unlocked it for you? Although this is being advanced, I need the mobile quickly and I would appreciate it very much.

not work for me, the sp tools keep show up notification to login mi account
my phone brick because I downgrade from android 10 to android 9
need help asap guys

sawclan22 said:
Odd two people reported no success there's no way it was some kind of fluke for me , I don't believe in that kind of technical luck, is there anyway I could talk to you in real time I would lik to see first hand what's going on
Click to expand...
Click to collapse
Thing is there is step where the flash tool gets authorisation if it fails to get it it throws a initiation error cmd_failed something like this. Also , this flash tool works normally without account if the phone is not hard bricked.
So I say maybe your phone wasn't hard bricked that's why tools you had worked.

can u please upload only flash tool files
I had already downloaded the rom ...im in my village (due to lockdown) with slow internet /nowifi so can u please upload flash tool only so I can test it

Not Work for Me :/
After trying the method with your files, the problem is still the same, the authentication window comes out every time and I can not flash my phone, for information (without Flash Tools) my phone displays only the LED light and when I connect it on my PC my computer recognizes it for a few seconds and this disconnection, maybe we don't have the same Hard Bricked of the phone
if you have any other information to suggest to me I will be grateful, thank you
(by google translate)

RanaDARK said:
Thing is there is step where the flash tool gets authorisation if it fails to get it it throws a initiation error cmd_failed something like this. Also , this flash tool works normally without account if the phone is not hard bricked.
So I say maybe your phone wasn't hard bricked that's why tools you had worked.
Click to expand...
Click to collapse
No it was definetey hatdbricked, stuck in a brick state after flashing an improper boot.IMG I was getting the error for authorization myself , then the window popped up with that specific set of tools and files , I then logged into my personal account and it worked, I tried flashing a good bunch of times, I removed my battery I couldn't get back to fastboot mode eventually I downloaded that mi flash tool from cynagenmods website , they called it a preauthorized flash tool or a flaehtool that wouldn't require authorization , well it didn't work I found the files in the special sauce folder in somones github , it would let me use them so I unticked something in the settings of sp flash tool , I can refer to the guide to see what it was after that I was super surprised to see it flash , maybe every other time I tried to flash it was a driver issue , if multiple people answer this the same let me know so I can close this thread, when u flash your hardbricked device does it even attempt to flash at all , do u see the loading bar move , usually it would fail for me on the first file it tried flash and I want to know the specific error it gave , this was my second time doing something idiotic and hardbricking this phone , if anyone can download teamveiwer and let me make sure all drivers are the same all files are exactly what I have etc , spflashtool has a good bit of different errors , I can't retest myself , not accurately atleast, the first thing I did after unbricking my phone was flashing the antibrick lk.IMG and bootloader

Question Now I have a new issue regarding the boot.img file.

So I got my phone fixed by flashing some random files I got off a quick Google search and got my phone back up and everything.
Now I have a brand new issue and it's stressing me the hell out that I feel like throwing my phone at the wall because that's how much stress this piece of garbage called a phone is causing me. I have been at this for hours to no proper fix from countless google searches going through websites and other xda threads.
The issue I'm experincing is I'm patching the boot.img file with Magisk and I then flash the img file with adb fastboot. There's 4 things going on when I do this
1 - The phone boots up normally but my touchscreen doesn't work to where I can't click or navigate my entire phone.
2 - The phone ends up in a boot loop where I see the Motorola Logo and that's it it restarts over and over and over and never properly boots.
3 - The phone keeps booting into bootloader on it's own.
4 - When I am able to get through my phone normally after flashing a patched magisk boot file an android update ends up restarting my phone and completely removes my root and I'm back to square one...
All this because I got sick of being bugged by these (BEEP)ing Motorola update pop ups which I made a thread about it on here asking for a way to disable it but never got any responses so I've taken this into my own hands and have made it even MORE worse and it's stressing me out so much.
I need to know how to I extract the boot.img file from my phone myself? I'm finding so many tutorials telling me to just download some boot.img file off the internet but that's what's causing me these issues above because I'm patching something that's probably not even compatible with my phone to begin with so i want to know how do I get the boot.img file directly off my phone so I can patch that with magisk?
I'm at a breaking point with this phone...

jake7901 said:
So I got my phone fixed by flashing some random files I got off a quick Google search and got my phone back up and everything.
Now I have a brand new issue and it's stressing me the hell out that I feel like throwing my phone at the wall because that's how much stress this piece of garbage called a phone is causing me. I have been at this for hours to no proper fix from countless google searches going through websites and other xda threads.
The issue I'm experincing is I'm patching the boot.img file with Magisk and I then flash the img file with adb fastboot. There's 4 things going on when I do this
1 - The phone boots up normally but my touchscreen doesn't work to where I can't click or navigate my entire phone.
2 - The phone ends up in a boot loop where I see the Motorola Logo and that's it it restarts over and over and over and never properly boots.
3 - The phone keeps booting into bootloader on it's own.
4 - When I am able to get through my phone normally after flashing a patched magisk boot file an android update ends up restarting my phone and completely removes my root and I'm back to square one...
All this because I got sick of being bugged by these (BEEP)ing Motorola update pop ups which I made a thread about it on here asking for a way to disable it but never got any responses so I've taken this into my own hands and have made it even MORE worse and it's stressing me out so much.
I need to know how to I extract the boot.img file from my phone myself? I'm finding so many tutorials telling me to just download some boot.img file off the internet but that's what's causing me these issues above because I'm patching something that's probably not even compatible with my phone to begin with so i want to know how do I get the boot.img file directly off my phone so I can patch that with magisk?
I'm at a breaking point with this phone...
Click to expand...
Click to collapse
Most likely you have a mis-matched boot.img.
Use LMSA's flash rescue to reflash the firmware.
Then use that boot.img to patch with magisk.
Stop using random guides that offer no support.
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com

sd_shadow said:
Most likely you have a mis-matched boot.img.
Use LMSA's flash rescue to reflash the firmware.
Then use that boot.img to patch with magisk.
Stop using random guides that offer no support.
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
Click to expand...
Click to collapse
Forgot to include LSMA is not working for me at all probably due to the firmware that I used several weeks ago when I first rooted the phone.
{
"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 had a similar issue to this several weeks ago but it was some other error that I forgot and thinking this was a long time ago I thought by now the program would finally work for me today but nope it never works.
App thinks I'm not in fastboot when I am right now.
So sadly I have to depend on these confusing builds from here and there and who knows where pretty much trial and error...
I wouldn't be in this position if it wasn't for those annoying (BEEP)ing Motorola update pop ups ruining my phone.
Maybe I should just throw the phone at the wall there's no hope.

jake7901 said:
Forgot to include LSMA is not working for me at all probably due to the firmware that I used several weeks ago when I first rooted the phone.
View attachment 5577727
View attachment 5577731
I had a similar issue to this several weeks ago but it was some other error that I forgot and thinking this was a long time ago I thought by now the program would finally work for me today but nope it never works.
App thinks I'm not in fastboot when I am right now.
So sadly I have to depend on these confusing builds from here and there and who knows where pretty much trial and error...
I wouldn't be in this position if it wasn't for those annoying (BEEP)ing Motorola update pop ups ruining my phone.
Maybe I should just throw the phone at the wall there's no hope.
Click to expand...
Click to collapse
Could also be a usb issue, Motos have had some issues like this for a while.
Try a different USB port, Cable or PC

I had the same problem. After patching the boot.img with Magisk and fastboot flashing it, I got no touchscreen.
The problem was the wrong boot.img.
I downloaded Stock ROMs from several sources, all saying that my phone uses a particular Stock ROM. They were all wrong!
I used the Lenovo Rescue and Smart Assistant v6.4.2.13. With genuine Motorola USB drivers.
It found my phone via the IMEI and I downloaded the stock ROM it suggested, it was a different one from all the other ones I had previously downloaded.
TIP, when downloading from the Rescue and Assistant program change where you want it to download to, as it's a pain to try and find it later when you need the boot.img!
After patching with Magisk and fastboot flashing, I'm now rooted and EVERYTHING works!