XT1955-5 bootloader unlock install TWRP & Root with Magisk - Moto G7 Power Guides, News, & Discussion
So when I got this device I went to root it and found there's not very good documentation on what to do to get root and recovery installed so after many boot loops and reinstall of firmware here is what I did to gain root and TWRP and have a stable environment. You will need to use ADB & Fastboot commands please install either this : https://forum.xda-developers.com/showthread.php?t=2317790 or https://forum.xda-developers.com/showthread.php?t=2588979 or you can install from here: https://developer.android.com/studio/releases/platform-tools. you will also need the Motorola drivers located here: https://support.motorola.com/us/en/solution/MS88481. Once you have obtained these you can proceed with the bootloader unlock. I have the unlocked version of the Motorola G7 Power so I was able to fallow the sets here: https://support.motorola.com/us/en/bootloader/unlockyourdeviceb. If you have a different variant I'm not sure if your able to unlock your bootloader please try and let me know in this thread. I AM NOT RESPONSIBLE IF YOU SCREW YOUR DEVICE UP OR FOR ANY DAMAGE TO YOUR DEVICE
Bootloader unlock steps:
1. On your device go to Settings and to System, Then About phone and click " Build Number " until you unlock developer options.
2. Back out one step and click the Advanced tab and then click " Developer Options ".
3. Once in developer options " OEM Unlocking " turn off " Automatic Updates " and enable "USB Debugging".
4. Once you have done USB Debugging open the start button type "CMD" and open a command prompt.
5. Once in command prompt type " adb devices " make sure you authorize the pc on the phone. then type in command prompt " adb reboot bootloader "
6. Once in bootloader type in command prompt " fastboot oem get_unlock_data " from here fallow the directions on the Motorola Bootloader Unlocking page: https://support.motorola.com/us/en/bootloader/unlockyourdevice
7. Take the number given to you by Motorola and type in command prompt " fastboot oem unlock CODE FROM MOTO " then enter the same command again and your device will be bootloader unlocked.
TWRP & Magisk install:
This is where I found it to be difficult to get things right either I would bootloop or I wouldn't be able to unencrypt my sd card in TWRP so I couldn't read things right all sorts of dumb issues. All the files I used are attached so please let me know if this works as well as it did for me. Please download the TWRP .img file it was too large to attach: https://dl.twrp.me/ocean/ Also make sure that your command prompt is in the directory of your stored files.
Here are a list of commands to get TWRP and install Root please be in bootloader mode to start this process.
1. fastboot boot twrp-3.3.1-2-ocean.img
2. In TWRP go to the wipe option and select the format and type " yes " once it has done that go back to the main TWRP page by hitting the home bottom and select Reboot and select Reboot Bootloader.
3. fastboot boot twrp-3.3.1-2-ocean.img
4. Once in TWRP adb push twrp-installer-3.3.1-2-ocean.zip /tmp/ then click install and navigate to the /tmp folder and install the TWRP .zip file
5. After you install TWRP do this : adb push Magisk-v20.1(20100).zip /tmp/ then navigate to your /tmp folder and install Magisk .zip file
6. After you install magisk you can reboot the system and let it sit it might loop once or twice but it will boot. I did the force encrypt disable with the attached zip file then i rebooted.
Also I found it best to do this with a fresh installed firmware that hasn't been booted yet I downloaded the firmware/ROM from here: https://mirrors.lolinet.com/firmware/moto/ocean/official/RETUS/ here is a list of commands to copy and paste into command prompt please make sure your device is in bootloader/ fastboot mode.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
Well i messed it up some how. my phone would boot loop three times and then go back to the twrp screen. after 30 minutes of messing with it i gave up and factory reset it via the adb platform tools.
Got it to work but had to start fresh as said at very bottom using retus version, I did all that then step by step but i booted once just to enable usb debugging of course, already had oem unlock but then right back into recovery flashed magisk and disable dm verity both back to back before reboot and all went fine cant get ota ofc but surely better roms will start showing up soon and I wont give a crap about stock anymore.
---------- Post added at 08:30 PM ---------- Previous post was at 08:29 PM ----------
toxinburn said:
Got it to work but had to start fresh as said at very bottom using retus version, I did all that then step by step but i booted once just to enable usb debugging of course, already had oem unlock but then right back into recovery flashed magisk and disable dm verity both back to back before reboot and all went fine cant get ota ofc but surely better roms will start showing up soon and I wont give a crap about stock anymore.
Click to expand...
Click to collapse
I am gonna check one thing I had it all working another method before but after installing something thru magisk it soft bricked I think it was vanced youtube maybe also cant seem to find a way to get vipre to work sadly.
Question
Does this method bypass the screen lock password on the phone? I have this phone that is locked with a passcode, so I can't easily get it into developer mode. Sorry, I'm a total newbie to this but am trying to learn. Thanks in advance!
A tip for linux users. If you are getting "< waiting for any device >" after the "fastboot oem get_unlock_data". Ctrl-c to exit the command. Su to root and then "fastboot oem get_unlock_data".
I give up, SIM stopped working after multiple failed attempts at installing Custom ROMs, even so much as installing Magisk+force encrypt disable brings up Factory data reset screen. Now my SIM doesn't even work on another stock phone for some reason, since the ban that apparently exists, if applied, should be IMEI-only, and somehow it works on a Custom ROM+Magisk device of mine. Going back to stock with locked bootloader I guess
SIM stopped working on G7 Power = neither SIM from two different carriers, one that's never been on a rooted/unlocked bootloader phone, don't even show up as a grey signal icon, tried both slots.
My SIM not working on another stock phone (G7 Play) = not recognized at all, but at least it recognizes there's a SIM card in there, grey signal.
Working fine on G5 with Magisk, Xposed and OmniROM
So maybe I banned both the chip (?) and IMEI, but still for some reason it works on another bootloader unlocked phone
Hyoretsu said:
I give up, SIM stopped working after multiple failed attempts at installing Custom ROMs, even so much as installing Magisk+force encrypt disable brings up Factory data reset screen. Now my SIM doesn't even work on another stock phone for some reason, since the ban that apparently exists, if applied, should be IMEI-only, and somehow it works on a Custom ROM+Magisk device of mine. Going back to stock with locked bootloader I guess
SIM stopped working on G7 Power = neither SIM from two different carriers, one that's never been on a rooted/unlocked bootloader phone, don't even show up as a grey signal icon, tried both slots.
My SIM not working on another stock phone (G7 Play) = not recognized at all, but at least it recognizes there's a SIM card in there, grey signal.
Working fine on G5 with Magisk, Xposed and OmniROM
So maybe I banned both the chip (?) and IMEI, but still for some reason it works on another bootloader unlocked phone
Click to expand...
Click to collapse
From what I've been able to tell, the SIM cards are locked via IMEI (from MetroPCS I assume?, cause that's what they do), and will appear invalid, but should show the phone number in the settings. It should also say out of service, unless inserted into the phone that it originally belonged to.
I have an E5 Play, and unlocked it using the device unlock app built-in from MetroPCS, after 3 months of service (maybe 6 I forget). After that, I could throw in other SIMs. But the phones those SIMs would come out of, they couldn't read the metro card. They said invalid. But it still recognized it was a card, and showed phone number in settings. Said out of service.
After realizing this, I found out you can change devices in the website real quick, and that should solve the "invalid SIM" issue.
Possibly some custom ROMs lack what restricts all this in the first place, and the Sim must be valid because it's a SIM, in service, and the proper network. No clue there. What carrier are you on?
Linux-Lord said:
From what I've been able to tell, the SIM cards are locked via IMEI (from MetroPCS I assume?, cause that's what they do), and will appear invalid, but should show the phone number in the settings. It should also say out of service, unless inserted into the phone that it originally belonged to.
Click to expand...
Click to collapse
The thing is, "stopped working" literally, it doesn't have out of service, phone number, no signal, not even the "emergency calls only", heck I can't even find my IMEI in settings nor *#0606#, I think that's what's causing the problem. This SIM also came from that Custom ROM device (originally inserted there, but bought as a standalone data plan)
Linux-Lord said:
and will appear invalid, but should show the phone number in the settings. It should also say out of service, unless inserted into the phone that it originally belonged to.
Click to expand...
Click to collapse
If you're talking about how it showed up like that on the G7 Play it used to work just fine in there, and no, that's not the original phone, it's just a phone I used to test if my SIM was still working
Linux-Lord said:
I have an E5 Play, and unlocked it using the device unlock app built-in from MetroPCS, after 3 months of service (maybe 6 I forget). After that, I could throw in other SIMs. But the phones those SIMs would come out of, they couldn't read the metro card. They said invalid. But it still recognized it was a card, and showed phone number in settings. Said out of service.
Click to expand...
Click to collapse
In this phone, G7 Power, it doesn't even recognize a card is in the tray anymore (unlike the G7 Play which at least knows there's one and G5+Custom ROM, in which it works)
Linux-Lord said:
After realizing this, I found out you can change devices in the website real quick, and that should solve the "invalid SIM" issue.
Possibly some custom ROMs lack what restricts all this in the first place, and the Sim must be valid because it's a SIM, in service, and the proper network. No clue there. What carrier are you on?
Click to expand...
Click to collapse
Not that it's gonna help much but OI (Brazil), and if that's on Motorola support page my G7 Power is main phone already.
Is the force encrypt disable necessary? And what does it do?
So, I have successfully rooted my Moto G7 Power by using the method above, but i tried not doing the "format data" and fortunately, I have rooted my phone. For the 1st attempt, I kinda soft-bricked my device by doing the steps briefly, my phone would always bootloop back to recovery mode, but after not doing the "format data" step, it led to a success. So for anyone who are currently experiencing bootloop, flash the stock firmware to your phone and root it again by using the method above but don't do the "format data" step. (flashing the stock firmware would not re-lock the bootloader, so you can try to root your phone again easily.)
error
I get this error
C:\Program Files (x86)\Minimal ADB and Fastboot> adb push magisk adb push Magisk-v20.1(20100).zip /tmp/
adb: error: cannot stat 'magisk': No such file or directory
adb: error: cannot stat 'adb': No such file or directory
adb: error: cannot stat 'push': No such file or directory
adb: error: cannot stat 'Magisk-v20.1(20100).zip': No such file or directory
---------- Post added at 08:07 AM ---------- Previous post was at 07:49 AM ----------
gladiatorbong said:
Well i messed it up some how. my phone would boot loop three times and then go back to the twrp screen. after 30 minutes of messing with it i gave up and factory reset it via the adb platform tools.
Click to expand...
Click to collapse
same here
brokenlocked22 said:
I get this error
C:\Program Files (x86)\Minimal ADB and Fastboot> adb push magisk adb push Magisk-v20.1(20100).zip /tmp/
adb: error: cannot stat 'magisk': No such file or directory
adb: error: cannot stat 'adb': No such file or directory
adb: error: cannot stat 'push': No such file or directory
adb: error: cannot stat 'Magisk-v20.1(20100).zip': No such file or directory
Click to expand...
Click to collapse
I mean, that's entirely on you, the command is wrong. Remove the first 3 words. And check the name of your Magisk ZIP (and location)
Hyoretsu said:
I mean, that's entirely on you, the command is wrong. Remove the first 3 words. And check the name of your Magisk ZIP (and location)
Click to expand...
Click to collapse
same thing as always.. no matter what lol
brokenlocked22 said:
same thing as always.. no matter what lol
Click to expand...
Click to collapse
If it's same thing as always then you're still using "adb push magisk adb push Magisk-v20.1(20100).zip /tmp/". There's no "but I'm not", if it's indeed the same error as before you're messing up on the syntax. Make sure you've put Magisk inside Minimal ADB folder, rename it to magisk.zip and run "adb push magisk.zip /tmp/"
why is magisk pushed to tmp and not to internal storage . Why not just push magisk to internal sotrage and just install that way through twrp or that wont work. just wondering.
Anyone tried this on XT1955-4?
dirtyscout said:
So when I got this device I went to root it and found there's not very good documentation on what to do to get root and recovery installed so after many boot loops and reinstall of firmware here is what I did to gain root and TWRP and have a stable environment. You will need to use ADB & Fastboot commands please install either this : https://forum.xda-developers.com/showthread.php?t=2317790 or https://forum.xda-developers.com/showthread.php?t=2588979 or you can install from here: https://developer.android.com/studio/releases/platform-tools. you will also need the Motorola drivers located here: https://support.motorola.com/us/en/solution/MS88481. Once you have obtained these you can proceed with the bootloader unlock. I have the unlocked version of the Motorola G7 Power so I was able to fallow the sets here: https://support.motorola.com/us/en/bootloader/unlockyourdeviceb. If you have a different variant I'm not sure if your able to unlock your bootloader please try and let me know in this thread. I AM NOT RESPONSIBLE IF YOU SCREW YOUR DEVICE UP OR FOR ANY DAMAGE TO YOUR DEVICE
Bootloader unlock steps:
1. On your device go to Settings and to System, Then About phone and click " Build Number " until you unlock developer options.
2. Back out one step and click the Advanced tab and then click " Developer Options ".
3. Once in developer options " OEM Unlocking " turn off " Automatic Updates " and enable "USB Debugging".
4. Once you have done USB Debugging open the start button type "CMD" and open a command prompt.
5. Once in command prompt type " adb devices " make sure you authorize the pc on the phone. then type in command prompt " adb reboot bootloader "
6. Once in bootloader type in command prompt " fastboot oem get_unlock_data " from here fallow the directions on the Motorola Bootloader Unlocking page: https://support.motorola.com/us/en/bootloader/unlockyourdevice
7. Take the number given to you by Motorola and type in command prompt " fastboot oem unlock CODE FROM MOTO " then enter the same command again and your device will be bootloader unlocked.
TWRP & Magisk install:
This is where I found it to be difficult to get things right either I would bootloop or I wouldn't be able to unencrypt my sd card in TWRP so I couldn't read things right all sorts of dumb issues. All the files I used are attached so please let me know if this works as well as it did for me. Please download the TWRP .img file it was too large to attach: https://dl.twrp.me/ocean/ Also make sure that your command prompt is in the directory of your stored files.
Here are a list of commands to get TWRP and install Root please be in bootloader mode to start this process.
1. fastboot boot twrp-3.3.1-2-ocean.img
2. In TWRP go to the wipe option and select the format and type " yes " once it has done that go back to the main TWRP page by hitting the home bottom and select Reboot and select Reboot Bootloader.
3. fastboot boot twrp-3.3.1-2-ocean.img
4. Once in TWRP adb push twrp-installer-3.3.1-2-ocean.zip /tmp/ then click install and navigate to the /tmp folder and install the TWRP .zip file
5. After you install TWRP do this : adb push Magisk-v20.1(20100).zip /tmp/ then navigate to your /tmp folder and install Magisk .zip file
6. After you install magisk you can reboot the system and let it sit it might loop once or twice but it will boot. I did the force encrypt disable with the attached zip file then i rebooted.
Also I found it best to do this with a fresh installed firmware that hasn't been booted yet I downloaded the firmware/ROM from here: https://mirrors.lolinet.com/firmware/moto/ocean/official/RETUS/ here is a list of commands to copy and paste into command prompt please make sure your device is in bootloader/ fastboot mode.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
IM a bit confused should I flash a fresh installed firmware first right after i unlock the boot loader?
Also I found it best to do this with a fresh installed firmware that hasn't been booted yet I downloaded the firmware/ROM from here: https://mirrors.lolinet.com/firmware/moto/ocean/official/RETUS/ here is a list of commands to copy and paste into command prompt please make sure your device is in bootloader/ fastboot mode.
[Redacted]
Excellent guide, rooted my Moto G7 from Metro PCS.
brokenlocked22 said:
same thing as always.. no matter what lol
Click to expand...
Click to collapse
I LOVE IT!!! :good:
Related
Flashing to stock Android NPD90G from TWRP error: "remote: unsupported command"
Flashing to stock Android NPD90G from TWRP error: "remote: unsupported command"
Fixed flashing error "remote: unsupported command" when flashing a Pixel C back to stock
I used TWRP and SuperSU to root and modify the buildprops to enable and get an early look at the windowing in Android N beta on my Pixel C release 5 ahead of time.
When Release 5 NPD90G was available I decided to flash back to stock from Developer Preview 4 NPD56N rooted with SuperSU and flashed with TWRP. I like root - I run Ubuntu and Win 7. I don't mind running a rooted device if it doesn't have all my work and financial data. When the final N release is out, the Pixel C will become my work machine. It's almost there.
I'm naturally paranoid. I change my long passwords frequently and use 2 factor authentication for everything. So if I can, I'll take a stock release. See my instructions for wiping Android devices: How to wipe an Android Phone: the paranoid editon
I could not flash the NPD90G stock bootloader because of an error "remote: unsupported command"
Here's how I fixed it.
Updated the SDK manager including SDK Tools and USB drivers.
With the Pixel C in recovery mode, {hold the power key and volume down}
In TWRP mount System and reboot to recovery
>ADB Shell.
From ADB Shell I ran
>fwtool vbnv write dev_boot_fastboot_full_cap 1 to reenable Fast boot.
Then I changed from TWRP to Fastboot mode {power button plus hold the volume up button}
>fastboot erase userdata
>fastboot erase boot
>fastboot erase cache
>fastboot erase recovery
>fastboot erase system
See Note 1. Below
>fastboot flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
>fastboot flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
Note 1.
The first time through I flashed the following line items which resulted in the resting robot Andi. I don't think I needed to do this, but if the above instructions don't work, run the following before continuing for {flash bootloader bootloader-dragon-google_smaug.7900.27.0.img}
>flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
>fastboot reboot-bootloader
>fastboot flash system system.img
>fastboot flash boot boot.img
>fastboot flash recovery recovery.img
>fastboot flash cache cache.img
Twrp can't flash The problem is that I can't boot into the twrp because when i try to flash it the answer is failed unsupported remote command
Tugio said: The problem is that I can't boot into the twrp because when i try to flash it the answer is failed unsupported remote command Click to expand... Click to collapse When in fastboot mode, use: Code: fastboot boot twrp-local-file-on-computer.img
DanBUK said: When in fastboot mode, use: Click to expand... Click to collapse It's nice of you to help a fellow XDA user. But I suspect he's already solved his problem of three months ago.....
Hi guys I have the same problem: - the bootloader is unlocked (Coreboot menu says so) - fastboot says "secure: yes" but "unlocked: yes" too - "fastboot flashing get_unlock_ability" returns "1" - "fastboot flashing unlock" says that the bootloader is already unlocked But I have no recovery and if I try to fastboot boot recovery.img it fails with signature verification error Can I do something to unbrick the device? Regards
lllopa said: Hi guys I have the same problem: - the bootloader is unlocked (Coreboot menu says so) - fastboot says "secure: yes" but "unlocked: yes" too - "fastboot flashing get_unlock_ability" returns "1" - "fastboot flashing unlock" says that the bootloader is already unlocked But I have no recovery and if I try to fastboot boot recovery.img it fails with signature verification error Can I do something to unbrick the device? Regards Click to expand... Click to collapse My solution is very simple: fastboot flashing lock fastboot flashing unlock fastboot reboot And now let it boot.... and wait. After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C
Make sure you have the latest version of fastboot and adb. I get these errors almost every month if I don't update. https://developer.android.com/studio/releases/platform-tools.html
@stevep2007, thank you so much! I've been dealing with this "remote: unsupported command" nonsense for days now after trying to revert back to an older Oreo version of Lineage. This did the trick!
How can I solve the problem when my Pixel C is not unlocked? My Pixel made an update and after installing the Update I got the green little man. Now I have no Chance to activate USB debugging etc. Its also not possible to install twrp.img How can I go to ADB shell with locked bootloader? Or isn't it possible? Fastboot devices shows me my tablet. ADB devices also show my tablet with "sideload". But every try to flash my Pixel fails. I alway get the message .... remote: unknown command.......fastboot error: command failed flash-all.bat showes that all "*.img are missing" error: command failed... unknown command etc....... So any idea to get my Pixel working again? ADB shell would make it I think. But how with locked bootloader.
_Arne_ said: My solution is very simple: fastboot flashing lock fastboot flashing unlock fastboot reboot And now let it boot.... and wait. After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C Click to expand... Click to collapse This did it for me!! Thanks much. I also updated platform-tools at the same time, who knows which did it
_Arne_ said: My solution is very simple: fastboot flashing lock fastboot flashing unlock fastboot reboot And now let it boot.... and wait. After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C Click to expand... Click to collapse In the scenario described by @llopa this solution does not work. In that scenario there are no solutions
bernardomarx said: In the scenario described by @llopa this solution does not work. In that scenario there are no solutions Click to expand... Click to collapse Sorry replied incorrectly
"No Sim Card detected" (due to TWRP backup restore) fix through fastboot commands?
"No Sim Card detected" (due to TWRP backup restore) fix through fastboot commands? Yesterday I had to restore my phone to a previous ROM (stock MM) from RR 5.8.5 Nightly. This was due to my working from home and needing to generate an RSA soft token, which is set up on an app on the backup, yadda yadda... Anyway, my restore worked fine, and I was able to generate my key and work from home. However... when I went to use my phone, I noticed that the SIM card was no longer detected. I tried restoring my RR rom, and it too would not detect my Sim card. In my attempts to find a fix, and then my attempt to restore the stock firmware and bootloader (that seems to be the only fix), I managed to royally hose my phone by attempting to flash the Full Stock LL ROM, which failed and must have overwritten the bootloader and recovery partitions. Trying to turn the phone on resulted in a vibration, but only a black screen. I was able to unbrick the phone using various guides I scrounged up and utilizing XFSTK and IntelSOC drivers, which must be installed when Windows 10 is booted with the special option to install unsigned drivers enabled (hold shift when you click restart, then option 7). I can post what I went through when I get home to my files and stuff if anyone requests it. Asus Flash Tool refused to flash the raw firmware (wrong format my ass), so I had to manually run the fastboot options. Everything was hunky dory after this. Every fix for the SIM card issue pointed to reverting to stock firmware, which is what I did. However, I'm thinking there must be some key partition that I flashed in fastboot that revived the SIM. I performed the below commands from this thread . Does anyone see a command that screams "I'm fixing sim card issues"? 1. fastboot devices ( see if it is recognized: else plug out usb and plugin again) 2. fastboot oem erase_osip_header 3. fastboot oem start_partitioning 4. fastboot flash /tmp/partition.tbl partition.tbl 5. fastboot oem partition /tmp/partition.tbl 6. fastboot erase system 7. fastboot erase cache 8. fastboot erase data 9. fastboot erase APD 10. fastboot erase ADF 11. fastboot oem wipe splashscreen 12. fastboot oem stop_partitioning 13. fastboot flash splashscreen splash_sign.bin 14. fastboot flash token MFG_BOM_Full.bin 15. fastboot flash ifwi ifwi-prod.bin 16. fastboot flash boot boot_sign.bin 17. fastboot flash recovery recovery_sign.bin 18. fastboot flash fastboot droidboot_sign.bin 19. fastboot flash APD APD.img 20. fastboot flash system system.img 21. fastboot reboot Click to expand... Click to collapse If we can get the fix for an undetected SIM card after TWRP backup down to a few (or single) fastboot command, it'd be a nice convenience for us all. Alternatively, does anyone know of a proper way to restore TWRP backups without losing SIM card detection? UPDATE SECTION I had found this site while searching for a solution yesterday, and it has the following fastboot commands for fixing the sim issue: adb reboot bootloader fastboot erase modemst1 fastboot erase modemst2 fastboot reboot Click to expand... Click to collapse So in this case, the modem partition is being erased. But I don't see anything in the unbricking fastboot commands that erases the modem partition. Am I just missing it? I could see my IMEI in Sim Slot 1, so maybe it wasn't a modem partition issue. ------------------------------------------------------------------------------------------------------------------- Found this thread (How did I miss it before?): https://forum.xda-developers.com/zenfone2/general/guide-how-to-zenfone-t3173314 The minimal boot options he listed are all in TWRP 3.1.1-0. The only thing I was missing before was config... I'm thinking that might be the key to preventing this. Next step is to determine if there's a config partition, and what happens when you do stuff to it (and ultimately how to restore the partition when you don't have a TWRP backup on hand).
Rooting Motorola G6 Play gone wrong
Hi everyone, I bought a Motorola G6 play model XT1922-3 type 374B and wanted root acces on this device. So I started by succesfully unlocking my bootloader using the following tutorial. After this a started tried to root the device using this tutorial. This tutorial doesn't link to boot images anymore so I was able to find the moto-g6-play-jeter-patched-twrp.img somewhere else. I did the following things: - reboot to bootloader [Succesfull] - fastboot boot moto-g6-play-jeter-patched-twrp.img [Unsuccesfull] The device did boot the twrp image but I was unable to interact with it in any way. I couldn't swipe or press buttons. I made a short video to show this. I wanted to retry the whole thing so I did reboot to bootloader but then I accidently entered the following command: fastboot flash boot moto-g6-play-jeter-patched-twrp.img picture of command prompt After this I wasn't able to normally boot my device. When I try to do so the screen goes black and says n/a in the left corner. Please does anyone know how I could either be able to boot my normal stock rom again or to have a rooted rom? Kind regards Sven Onderbeke
Hi Sven, This isn't going to be the most advanced reply, as I'm not very experienced with this stuff either, but it seems you have accidentally flashed your twrp image to 'boot', wherever that is, which is why the phone isn't able to boot to system. Can you still boot into bootloader and recovery (twrp)? If so, then I'd suggest using fastboot to flash a sock or custom ROM. I'm not sure exactly which one though, you have basically the same model as me and that seems to use the JETER ROMS a list of which are over here (can't post links yet, so you will just have to search on mirrors . lolnet . com /firmware/moto/jeter/official/ or remove the spaces I seem to have somehow lost the partitions on mine, but will start a new thread question about that.
Sven Onderbeke said: Hi everyone, I bought a Motorola G6 play model XT1922-3 type 374B and wanted root acces on this device. So I started by succesfully unlocking my bootloader using the following tutorial. After this a started tried to root the device using this tutorial. This tutorial doesn't link to boot images anymore so I was able to find the moto-g6-play-jeter-patched-twrp.img somewhere else. I did the following things: - reboot to bootloader [Succesfull] - fastboot boot moto-g6-play-jeter-patched-twrp.img [Unsuccesfull] The device did boot the twrp image but I was unable to interact with it in any way. I couldn't swipe or press buttons. I made a short video to show this. I wanted to retry the whole thing so I did reboot to bootloader but then I accidently entered the following command: fastboot flash boot moto-g6-play-jeter-patched-twrp.imgpicture of command prompt After this I wasn't able to normally boot my device. When I try to do so the screen goes black and says n/a in the left corner. Please does anyone know how I could either be able to boot my normal stock rom again or to have a rooted rom? Kind regards Sven Onderbeke Click to expand... Click to collapse Just flash a stock boot.img to boot. Then just flash TWRP to recovery. In TWRP, format data. Type yes. Then reboot recovery. Then Use TWRP to flash magisk. Done.
Hi again Sven, I just wanted to let you know that I just downloaded the following RETAIL ROM ALJETER_RETAIL_9.0_PPPS29.55-35-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml and used the following fastboot commands, one at a time. fastboot flash partition gpt.bin fastboot flash bootloader bootloader.img fastboot flash modem NON-HLOS.bin fastboot flash fsg fsg.mbn fastboot flash dsp adspso.bin fastboot flash boot boot.img fastboot flash system system.img_sparsechunk.0 fastboot flash system system.img_sparsechunk.1 fastboot flash system system.img_sparsechunk.2 fastboot flash system system.img_sparsechunk.3 fastboot flash system system.img_sparsechunk.4 fastboot flash oem oem.img fastboot flash vendor vendor.img fastboot erase carrier fastboot erase userdata fastboot erase DDR fastboot flash logo logo.bin fastboot reboot Which rebooted into bootloader so pressed "start" and all booted fine now. It looks like we have the same device, so hopefully that will work for you too.
[GUIDE] How to root it
First, I assume you know what root, fastboot, SafetyNet, bootloader, adb is ( SEARCH FIRST BEFORE DOING THESE STEPS! ) and you know the risks of rooting a device! Me nor the XDA guys are responsible for bricked devices, nor any damage to you and/or your device. So, after that, let's dive into the steps of rooting it First of all is to download your stock android image ( in case something goes wrong plus the boot.img needed for this process ) You can download your stock image the way you want, you can use lolinet etc, just make sure it matches your device! So, open the image you downloaded, extract the boot.img file and put it on the phone's internal memory, then download Magisk Manager ( I personally used GitHub to download.... ) and open it. Now, select 'Install' ( the one that says Magisk, not the manager ), go to 'Select and Patch a file' Navigate and select your boot.img, then wait for it to complete, after that, you'll see a file in the Download folder on the phone called 'magisk_patched.img' grab this file and put it on the computer. The next step is that you'll need to unlock your bootloader ( I'll not cover how to do that here, but a quick search on ' how to unlock Motorola bootloader' should help ), but be aware that it will format your phone ( you'll lose any saved data, so pay attention! ) After, put the phone in fastboot mode again ( vol minus + power button ), then on the terminal window you're using fastboot, run this command: fastboot boot magisk_patched.img ( I assume you put the magisk_patched in the same folder you're running fastboot ( Windows case ) ) REMEMBER TO TEST EVERYTHING ON YOUR DEVICE IN THIS PART BEFORE CONTINUING!!!!! IF YOUR PHONE DIDN'T BOOT OR BOOTED BUT WITH MALFUNCTION STOP NOW AND REBOOT IT, MAYBE YOUR STOCKROM WASN'T CORRECT OR SOMETHING ELSE... After that your device will normally boot, install Magisk Manager and check if it "says" installed and displays the version. If so and your device runs fine, reboot again to fastboot then run on the terminal window: fastboot flash boot magisk_patched.img This will make the root persistent after reboots Now as you expected, you're rooted A bonus tip: Safetynet will fail! To fix that, open Magisk Manager, then go to it's settings, then tap to enable "MagiskHide" and then tap "Hide Magisk Manager" type a new name for the Manager and boom, that's it, now SafetyNet will work ( In my case it did hehe ) I'm new to English, learning alone, so any mistyping etc tell me and I'll fix it Also I'm new to XDA too hihi
Thanks a lot for sharing your experience! Has there been anyone else who managed to root this device? I really want to buy one but first I want to make sure I will be able to root it from day 1. I don't like to use an unrooted phone
I bought my device last Black Friday and rooted it this week with this guide. I’ve downloaded my boot.img from Lolinet and googled how to unlock a bootloader of a Moto phone. I’ve also enabled oem unlock in developer settings. It’s not so difficult. The bonus tip from the OP is very helpful. Only rename Magisk is not enough. Also hide the manager to pass the safetynet test.
ReneZeiss said: I bought my device last Black Friday and rooted it this week with this guide. I’ve downloaded my boot.img from Lolinet and googled how to unlock a bootloader of a Moto phone. I’ve also enabled oem unlock in developer settings. It’s not so difficult. The bonus tip from the OP is very helpful. Only rename Magisk is not enough. Also hide the manager to pass the safetynet test. Click to expand... Click to collapse Amazing tips. I think in the end we are free to root it without screwing the device for good Thanks!!
Ok, I got mine yesterday, and today I successfully root it. It worked flawlessly!! Thanks for the guide and advices!!
Root now si possible with twrp, new update thanks @seba_3567
MrZeroXD said: First, I assume you know what root, fastboot, SafetyNet, bootloader, adb is ( SEARCH FIRST BEFORE DOING THESE STEPS! ) and you know the risks of rooting a device! Me nor the XDA guys are responsible for bricked devices, nor any damage to you and/or your device. So, after that, let's dive into the steps of rooting it First of all is to download your stock android image ( in case something goes wrong plus the boot.img needed for this process ) You can download your stock image the way you want, you can use lolinet etc, just make sure it matches your device! So, open the image you downloaded, extract the boot.img file and put it on the phone's internal memory, then download Magisk Manager ( I personally used GitHub to download.... ) and open it. Now, select 'Install' ( the one that says Magisk, not the manager ), go to 'Select and Patch a file' Navigate and select your boot.img, then wait for it to complete, after that, you'll see a file in the Download folder on the phone called 'magisk_patched.img' grab this file and put it on the computer. The next step is that you'll need to unlock your bootloader ( I'll not cover how to do that here, but a quick search on ' how to unlock Motorola bootloader' should help ), but be aware that it will format your phone ( you'll lose any saved data, so pay attention! ) After, put the phone in fastboot mode again ( vol minus + power button ), then on the terminal window you're using fastboot, run this command: fastboot boot magisk_patched.img ( I assume you put the magisk_patched in the same folder you're running fastboot ( Windows case ) ) After that your device will normally boot, install Magisk Manager and check if it "says" installed and displays the version. If so and your device runs fine, reboot again to fastboot then run on the terminal window: fastboot flash boot magisk_patched.img This will make the root persistent after reboots Now as you expected, you're rooted A bonus tip: Safetynet will fail! To fix that, open Magisk Manager, then go to it's settings, then tap to enable "MagiskHide" and then tap "Hide Magisk Manager" type a new name for the Manager and boom, that's it, now SafetyNet will work ( In my case it did hehe ) I'm new to English, learning alone, so any mistyping etc tell me and I'll fix it Also I'm new to XDA too hihi Click to expand... Click to collapse yes or yes I must download the full firmware, can't find the boot.img directly?
Hi, I root the G9+ with your guide and now it's rooted, thank you for post it. I want to change te system fonts, I have some visual impediments and I need a fonts with more contrast and bold. I try with Fontster, HiFonts, Zfonts, and many more. I grant root privileges to these via MagiskManager, but without any success. It's normal that? any idea why? The rootchecher confirm that the phone it's rooted. Please can help me? Thank you and please excuse my poor english
pmb6000 said: Hi, I root the G9+ with your guide and now it's rooted, thank you for post it. I want to change te system fonts, I have some visual impediments and I need a fonts with more contrast and bold. I try with Fontster, HiFonts, Zfonts, and many more. I grant root privileges to these via MagiskManager, but without any success. It's normal that? any idea why? The rootchecher confirm that the phone it's rooted. Please can help me? Thank you and please excuse my poor english Click to expand... Click to collapse I think u'll need to port your custom fonts as Magisk Modules, since you can't change system files directly ( even with root ).
Hi, I'm new to rooting the phone, I managed to unlock the bootloader, I did everything as in the description except the last step because the fastboot boot magisk_patched.img command did not work. So I copied the magisk file to the adb folder and typed: fastboot flash boot C: \ adb \ magisk_patched_INTjS.img. My phone touchscreen has stopped working. I'm very worried. Is it possible that I used the wrong stock image version or did I do it wrong? Now I wish the phone would just work
taboelephant said: Hi, I'm new to rooting the phone, I managed to unlock the bootloader, I did everything as in the description except the last step because the fastboot boot magisk_patched.img command did not work. So I copied the magisk file to the adb folder and typed: fastboot flash boot C: \ adb \ magisk_patched_INTjS.img. My phone touchscreen has stopped working. I'm very worried. Is it possible that I used the wrong stock image version or did I do it wrong? Now I wish the phone would just work Click to expand... Click to collapse So maybe your stock was wrong, if ' fastboot boot magisk_patched.img ' failed then u can't force ( fastboot flash ) the installation since it'll probably cause problems... I suggest you try to download your stock rom and re-flash the boot partition, if no lucky, try using ' Lenovo rescue and smart assistant ' and hope it works again...
MrZeroXD said: So maybe your stock was wrong, if ' fastboot boot magisk_patched.img ' failed then u can't force ( fastboot flash ) the installation since it'll probably cause problems... I suggest you try to download your stock rom and re-flash the boot partition, if no lucky, try using ' Lenovo rescue and smart assistant ' and hope it works again... Click to expand... Click to collapse Yes, I tried to enter this command but it said that it cannot find the file magisk. Tomorrow I will try to install the stock rom with RSD Lite if that's the right decision, with the help of this website: https://www.androidinfotech.com/moto-g9-plus-odessa-android-10/. If that doesn't help, I will have to give it to repaired because I won't be able to handle it myself.
taboelephant said: Yes, I tried to enter this command but it said that it cannot find the file magisk. Tomorrow I will try to install the stock rom with RSD Lite if that's the right decision, with the help of this website: https://www.androidinfotech.com/moto-g9-plus-odessa-android-10/. If that doesn't help, I will have to give it to repaired because I won't be able to handle it myself. Click to expand... Click to collapse Sincerely I would suggest using the Lenovo tool, it's simple to use, and guaranteed to pick the correct rom.
MrZeroXD said: Sincerely I would suggest using the Lenovo tool, it's simple to use, and guaranteed to pick the correct rom. Click to expand... Click to collapse OK I wiil try tomorrow reapir it with this lenovo tool, I wish it will help.
taboelephant said: OK I wiil try tomorrow reapir it with this lenovo tool, I wish it will help. Click to expand... Click to collapse It's should work since it's an official tool, any news tell us. Good lucky buddy.
Lenovo tool does not work although my model exists its: G9 plus XT2087-2 error that appears: Unable to match tche appropriate firmware. Some key information cannot be read from the device. You can find my stock room here: https://mirrors.lolinet.com/firmware/moto/odessa/official/. Its RETEU or RETEU_PL version: XT2087-2_ODESSA_RETEU_10_QPA30.19-Q3-32-50_subsidy-DEFAULT. I am from Poland, so it could be RETEU_PL. How can I install this stock room if the lenovo tool doesn't work?
taboelephant said: Lenovo tool does not work although my model exists its: G9 plus XT2087-2 error that appears: Unable to match tche appropriate firmware. Some key information cannot be read from the device. You can find my stock room here: https://mirrors.lolinet.com/firmware/moto/odessa/official/. Its RETEU or RETEU_PL version: XT2087-2_ODESSA_RETEU_10_QPA30.19-Q3-32-50_subsidy-DEFAULT. I am from Poland, so it could be RETEU_PL. How can I install this stock room if the lenovo tool doesn't work? Click to expand... Click to collapse So, I've a code that I use on my Linux box, it should work in windows too, but all of your stock rom ( bootloader.img ; got.bin; recovery.img ; etc ) must be in the same folder as fastboot.exe Here's the code Spoiler fastboot --set-active=a fastboot getvar max-sparse-size fastboot oem fb_mode_set fastboot flash partition gpt.bin fastboot flash bootloader bootloader.img fastboot flash vbmeta_a vbmeta.img fastboot flash vbmeta_b vbmeta.img fastboot flash radio_a radio.img fastboot flash radio_b radio.img fastboot flash bluetooth_a BTFM.bin fastboot flash bluetooth_b BTFM.bin fastboot flash dsp_a dspso.bin fastboot flash dsp_b dspso.bin fastboot flash logo_a logo.bin fastboot flash logo_b logo.bin fastboot flash boot_a boot.img fastboot flash boot_b boot.img fastboot flash dtbo_a dtbo.img fastboot flash dtbo_b dtbo.img fastboot flash recovery_a recovery.img fastboot flash recovery_b recovery.img fastboot flash super super.img_sparsechunk.0 fastboot flash super super.img_sparsechunk.1 fastboot flash super super.img_sparsechunk.2 fastboot flash super super.img_sparsechunk.3 fastboot flash super super.img_sparsechunk.4 fastboot flash super super.img_sparsechunk.5 fastboot flash super super.img_sparsechunk.6 fastboot flash super super.img_sparsechunk.7 fastboot flash super super.img_sparsechunk.8 fastboot erase carrier fastboot erase userdata fastboot erase metadata fastboot erase ddr fastboot oem fb_mode_clear fastboot reboot
MrZeroXD said: So, I've a code that I use on my Linux box, it should work in windows too, but all of your stock rom ( bootloader.img ; got.bin; recovery.img ; etc ) must be in the same folder as fastboot.exe Here's the code Spoiler fastboot --set-active=a fastboot getvar max-sparse-size fastboot oem fb_mode_set fastboot flash partition gpt.bin fastboot flash bootloader bootloader.img fastboot flash vbmeta_a vbmeta.img fastboot flash vbmeta_b vbmeta.img fastboot flash radio_a radio.img fastboot flash radio_b radio.img fastboot flash bluetooth_a BTFM.bin fastboot flash bluetooth_b BTFM.bin fastboot flash dsp_a dspso.bin fastboot flash dsp_b dspso.bin fastboot flash logo_a logo.bin fastboot flash logo_b logo.bin fastboot flash boot_a boot.img fastboot flash boot_b boot.img fastboot flash dtbo_a dtbo.img fastboot flash dtbo_b dtbo.img fastboot flash recovery_a recovery.img fastboot flash recovery_b recovery.img fastboot flash super super.img_sparsechunk.0 fastboot flash super super.img_sparsechunk.1 fastboot flash super super.img_sparsechunk.2 fastboot flash super super.img_sparsechunk.3 fastboot flash super super.img_sparsechunk.4 fastboot flash super super.img_sparsechunk.5 fastboot flash super super.img_sparsechunk.6 fastboot flash super super.img_sparsechunk.7 fastboot flash super super.img_sparsechunk.8 fastboot erase carrier fastboot erase userdata fastboot erase metadata fastboot erase ddr fastboot oem fb_mode_clear fastboot reboot Click to expand... Click to collapse Room that I will download should I unpack to adb folder or where? Is it safe to install it yourself or is it better to go to a local phone repairer? It may be hard to find someone who knows what to do.
taboelephant said: Room that I will download should I unpack to adb folder or where? Is it safe to install it yourself or is it better to go to a local phone repairer? It may be hard to find someone who knows what to do. Click to expand... Click to collapse Yeah, as I said, u need to unpack it to the folder where you see the ' fastboot.exe ' file, and then copy all the spoiler commands I sent, put the phone in fastboot mode, and open the cmd in the folder where fastboot.exe and your extracted rom is, then paste and run the spoiler commands and you're good to go, remember that it'll take a while since it'll re-flash all your system.
MrZeroXD said: Yeah, as I said, u need to unpack it to the folder where you see the ' fastboot.exe ' file, and then copy all the spoiler commands I sent, put the phone in fastboot mode, and open the cmd in the folder where fastboot.exe and your extracted rom is, then paste and run the spoiler commands and you're good to go, remember that it'll take a while since it'll re-flash all your system. Click to expand... Click to collapse Ok I will try this method in the evening when I have free time, thank you for your help and sorry for my lack of knowledge. I'm also afraid that when I install the wrong room, usb debugging will turn off, although the theoretical version number is correct.
taboelephant said: Ok I will try this method in the evening when I have free time, thank you for your help and sorry for my lack of knowledge. I'm also afraid that when I install the wrong room, usb debugging will turn off, although the theoretical version number is correct. Click to expand... Click to collapse No prob, we're all learning, and all you need to fix a device that doesn't boot, is an unlocked bootloader, since u can re-flash, I did this on a few devices ( moto x4 ; moto G5s ; moto g9+ ) and succeeded on repairing those...
Can't install TWRP
I flashed my redmi note 8 pro indian version with miflash, and downgraded to android 9 from 11 to install Ubuntu touch. Ubports installer still didnt recognize my phone I am guessing cause it was Begoniain(india) as opposed to Begonia(Global) that is supported. But my problem is I want to go back to Android, and I dont know how to go back, I didn't have any recovery tool installed before installing Ubuntu Touch, now Ubuntu is very buggy, and I can't seem to install TWRP. I have no other recovery tools installed, just fastboot. I guess I should hvae installed twrp before installing Ubuntu Touch. I want to know how I can go back to android or to any other supported custom rom. Thank you.
whats wrong with fastboot?
Hey, thanks for replying. I followed the steps in this video which is a very accurate video i found after searching for many videos. basically he asked to download the right TRWP, then ADB platform tools, then the ADB driver found here [OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in... forum.xda-developers.com then using "fastboot flash recovery twrp.img" cmd command this seemed to work for many people and everything went well. but I just can't boot to twrp it just takes me to the ubuntu touch screen and i log back in to UT
xiaomi: Code: fastboot flash recovery twrp.img fastboot oem reboot-recovery
aIecxs said: xiaomi: Code: fastboot flash recovery twrp.img fastboot oem reboot-recovery Click to expand... Click to collapse I get this message FAILED (remote: 'unknown command') fastboot: error: Command failed
more commands I tried 'fastboot flash boot' gives me this error fastboot error android_product_out not set and 'fastboot boot recovery' command gives me this error fastboot error cannot load 'recovery' no such file or directory another command 'adb reboot bootloader' gave me this error no devices/emulators found
I recommend to read 'fastboot help' 'fastboot flash' cmd requires two arguments: target (partition name) and source (path to file on pc) 'fastboot boot' cmd requires one argument only: source (path to file on pc) 'no such file or directory' means there exist no such file or directory with name 'recovery' (Note this command requires bootable flag on current slot or will silently fail) 'fastboot oem' commands are device specific hidden commands. 'fastboot oem reboot-recovery' does not work on my device, but you will find lot suggestions for this here in forum (I just copy-pasted of xiaomi forum) 'adb' commands generally can't work in fastboot mode (and 'adb reboot bootloader' is fastboot mode btw) if 'fastboot oem reboot-recovery' is unknown command, you can use 'fastboot reboot' instead. press and keep holding volume up while the phone reboots, it will enter recovery mode.
now the phone is stuck at restarting i tried this 'fastboot erase data" FAILED (remote: Partition table doesn't exist) i just want a way to reset the phone back to android or other custom rom
Partition table doesn't exist?? you must have done something stupid...
aIecxs said: I recommend to read 'fastboot help' 'fastboot flash' cmd requires two arguments: target (partition name) and source (path to file on pc) 'fastboot boot' cmd requires one argument only: source (path to file on pc) 'no such file or directory' means there exist no such file or directory with name 'recovery' (Note this command requires bootable flag on current slot or will silently fail) 'fastboot oem' commands are device specific hidden commands. 'fastboot oem reboot-recovery' does not work on my device, but you will find lot suggestions for this here in forum (I just copy-pasted of xiaomi forum) 'adb' commands generally can't work in fastboot mode (and 'adb reboot bootloader' is fastboot mode btw) if 'fastboot oem reboot-recovery' is unknown command, you can use 'fastboot reboot' instead. press and keep holding volume up while the phone reboots, it will enter recovery mode. Click to expand... Click to collapse thank you i will try it
aIecxs said: Partition table doesn't exist?? you must have done something stupid... Click to expand... Click to collapse yes i think so, i think i should've installed twrp before that was the mistake, but i'll have to format this somehow
Did you try flash by mi flash the rom that you used to downgrade?
yes this is the first thing i tried, the same procedure i used to downgrade to 9 with mi flash, but when i do that it flashses in just 1 second, and gives success message, i was like it can't be that fast, but that happens everytime, so i figured somethings wrong. I turn on my phone and it's not flashed, it boots to ubuntu touch, but now even that's not happening, now it just keeps restarting after xiomi unlcoked screen.
i want to install a custom rom that goes best with my phone, i dont really want andriod to be honest, but need to have something installed to boot atleast, and I dont really mind if the phone goes dead, so i am not worried about experimenting on it
pp1pkew said: yes this is the first thing i tried, the same procedure i used to downgrade to 9 with mi flash, but when i do that it flashses in just 1 second, and gives success message, i was like it can't be that fast, but that happens everytime, so i figured somethings wrong. I turn on my phone and it's not flashed, it boots to ubuntu touch, but now even that's not happening, now it just keeps restarting after xiomi unlcoked screen. Click to expand... Click to collapse Try flash by sp flash tool. Maybe your partitions got fked by flash Ubuntu.
pp1pkew said: i tried this 'fastboot erase data" FAILED (remote: Partition table doesn't exist) Click to expand... Click to collapse aIecxs said: Partition table doesn't exist?? you must have done something stupid... Click to expand... Click to collapse I believe that error message is misleading. It should mean FAILED (remote: 'No such partition.') you probably meant 'userdata' partition. however, I do not recommend fastboot erase cmd. you should be able to enter fastboot mode with Volume Down button. instead of flashing TWRP into recovery partition (where it belongs) you could cheat bootloader and flash TWRP into boot partition instead. this will boot into TWRP recovery without Volume Up Button. Code: fastboot flash boot twrp.img once in TWRP you can format Data, flash boot partition and install TWRP recovery. probably easiest way is, create backup of boot + recovery from TWRP backup menu. that will create two files, boot.emmc.win + recovery.emmc.win in TWRP/Backups/<serialno>/<date> directory. just create another directory TWRP/Backups/<serialno>/my_files and place your files in there (rename boot.img = boot.emmc.win and twrp.img = recovery.emmc.win) then restore 'my_files' backup from menu. then you can install any ROM from TWRP via System Image. Note that's android device, you can only install android. even ubports Ubuntu touch is not linux, it is just some gui build on top of android kernel to give you linux-like feelings.