Clockworkmod recovery doesn't work(only get a blank screen after I make my selection), and my phone wont boot. I'm trying to flash a rom via fastboot or adb.
I installed fastboot and adb using this guide:
fastboot adb guide
I downloaded htc sync to install the drivers.
I'm trying to follow this guide for flashing a new rom
xda flashing guide
when i try "fastboot -w" the command prompt returns "erasing 'userdata'... FAILED <remote: not allowed>"
it seems the sollution for this is posted here. but i don't know how to flash an hboot. Can anyone point me in the right direction? I've been searching and all i could find was fastboot commander, but when I try to flash a new Hboot or my recovery image it returns "flash FAILURE"
sombomb said:
Clockworkmod recovery doesn't work(only get a blank screen after I make my selection), and my phone wont boot. I'm trying to flash a rom via fastboot or adb.
I installed fastboot and adb using this guide:
fastboot adb guide
I downloaded htc sync to install the drivers.
I'm trying to follow this guide for flashing a new rom
xda flashing guide
when i try "fastboot -w" the command prompt returns "erasing 'userdata'... FAILED <remote: not allowed>"
it seems the sollution for this is posted here. but i don't know how to flash an hboot. Can anyone point me in the right direction? I've been searching and all i could find was fastboot commander, but when I try to flash a new Hboot or my recovery image it returns "flash FAILURE"
Click to expand...
Click to collapse
In clockwork use the trackball to select items, not the power button.
To use most fastboot commands you need an unlocked bootloader, or the engineering bootloader. To chanhe your bootloader you need to be s-off, or do an entire ruu.
cmlusco said:
In clockwork use the trackball to select items, not the power button.
To use most fastboot commands you need an unlocked bootloader, or the engineering bootloader. To chanhe your bootloader you need to be s-off, or do an entire ruu.
Click to expand...
Click to collapse
Wasn't using the trackball. This is embarrassing. Thanks for all the helpful info, you're awesome.
=X
wow this is funny, but sadly it helped me also
In case you'd still like to know how to do it via fastboot, here are some steps:
Place the .zip in the same directory as the adb and fastboot executables
Double check the md5 of the .zip before proceeding to prevent bricking the device
Run the following commands in command prompt:
fastboot devices //Verify that the device is detected
fastboot erase cache //Not sure if this is completely necessary, but the guide I followed included it as a step
fastboot oem rebootRUU //Boot into RUU, which lets you flash HBOOT, radio, etc.
fastboot flash zip [zipname.zip] //Replace zipname.zip with the actual name of the file you are flashing
fastboot reboot-bootloader //The guide I pulled this info from didn't specifically say that you should reboot to bootloader rather than to Android, but I have seen others mention that you should always reboot to the bootloader first after flashing an HBOOT or radio. I would do this just in case
thehiggins you saved the day
Thanks You
Didn't know I had to be in RUU. When do I need to be in RUU, when flashing the boot or any boot related img/zip ?
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
Having a weird issue I've never run into. Used to be on Invitrix rom, returned to stock via latest oreo flashall and wanted to get onto Lineage 15.1. While flashall works, I cannot boot from TWRP. I've attempted on both Windows 10, Ubuntu 18.04 LTS and Ubuntu 18.10 and ensured all drivers are installed. I've tried with and without sudo privilege just in case. I've tried renaming the .img to recovery.img, boot.img, etc.. Yet, I keep getting a simple failed message. Bootloader is still unlocked and I've tried multiple cables including the stock one, USB 2.0 and 3.0 ports on both my desktop and and laptop. Is my phone simply corrupted or am I missing something?
sudo fastboot boot twrp-3.2.3-0-nash.img
downloading 'boot.img'...
FAILED (remote: unknown command)
finished. total time: 0.001s
Put the phone in bootloader mode and verify connection.
PHP:
fastboot devices
If it is recognized then...
PHP:
fastboot boot <path/to/twrp-3.2.3-2-nash.img>
*Note - In win you can drag n' drop the recovery img in the command prompt and it will auto fill the full path.
41rw4lk said:
Put the phone in bootloader mode and verify connection.
PHP:
fastboot devices
If it is recognized then...
PHP:
fastboot boot <path/to/twrp-3.2.3-2-nash.img>
*Note - In win you can drag n' drop the recovery img in the command prompt and it will auto fill the full path.
Click to expand...
Click to collapse
I did. Device shows up like normal. I verified by typing
fastboot devices
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:
I did everything on https://wiki.lineageos.org/devices/ginkgo/install , I flashed the recovery, on the Prompt I get "okay" to both Sending and Writing, and on "Now reboot into recovery to verify the installation" my phone is still on fastboot, so I press for a long time the power button to (force?) shut down it, use volume_up+power and what I see is the "Redmi-Recovery 3.0" (stock recovery).
Is it possible to have 2 recovery and I simply don't know how to access the LOS one? Maybe I could have more luck installing TWRP and overwriting it with LOS recovery (how to?)?
From fastboot if I write "fastboot reboot recovery" right after "fastboot flash recovery ..." prompt says "Rebooting into recovery...okay" but then the normal OS is loaded.
If I use
Code:
adb reboot bootloader
I access to the stock fastboot, and from there
Code:
fastboot boot recoveryimagename.img
says
Code:
fastboot: error: cannot load 'lineage-17.1-20201228-recovery-ginkgo.img': No such file or directory
. If I use it from MIUI-OS:
Code:
< waiting for any device >
and Prompt is waiting there.
I have fastboot and recovery image in the same folder but with
Code:
fastboot flash recovery *recovery*
I get
Code:
fastboot: error: cannot load 'lineage-17.1-20201228-recovery-ginkgo.img': No such file or directory
, infact I used full path (full of the img file, not the adb/fastboot which I properly installed) instead of relative, giving the "okay", and after that with
Code:
fastboot boot lineage-17.1-20201228-recovery-ginkgo.img
I get
Code:
fastboot: error: cannot load 'lineage-17.1-20201228-recovery-ginkgo.img': No such file or directory
!
Only now I've seen I was writing from root Prompt and therefore from "C:\WINDOWS\system32>", I used "cd platform-tools_path" and (after
Code:
fastboot flash recovery lineage-17.1-20201228-recovery-ginkgo.img
)
Code:
fastboot boot lineage-17.1-20201228-recovery-ginkgo.img
worked, but now the phone is stuck here!! From prompt everything seems ok. The phone is stuck on the normal loading boot after that "fastboot boot..."! Before I even tried installing TWRP...maybe that was too much? Now?
I used again "fastboot boot lineage-17.1-20201228-recovery-ginkgo.img" and it seems to working...maybe in a couple of minutes(hours probably) I'll mark this as solved!
Ok, I think everything is good now, but I have a question: is it possible to have more than one recovery installed?
BEDBOI2 said:
is it possible to have more than one recovery installed?
Click to expand...
Click to collapse
it is possible on other devices, but until now not possible on ginkgo