Hi! Anyone know when TWRP recovery will be available for Moto G6 Plus (or is it already available)? And are there any custom roms for Moto G6 Plus and will be there any roms?
Check the development section of this forum, any unofficial roms or recoveries for the device will be there. You can also check the TWRP website, as well as the LineageOS website.
never cause you asked. THANKS A LOT
Mr. Nerd_ said:
Hi! Anyone know when TWRP recovery will be avaible for Moto G6 Plus (or is it already avaible)? And are there any custom roms for Moto G6 Plus and will be there any roms?
Click to expand...
Click to collapse
Twrp is available. Search for it on Android file host website. As for roms, check out the project treble forum here on xda for a number of GSIs(generic system images) which are the future of roms. They come in IMG format not zip format. Depending on the gsi you flash, some things may not work mainly finger print scanner.
Sent from my moto g(6) plus using Tapatalk
Xplorer4x4 said:
Twrp is available. Search for it on Android file host website. As for roms, check out the project treble forum here on xda for a number of GSIs(generic system images) which are the future of roms. They come in IMG format not zip format. Depending on the gsi you flash, some things may not work mainly finger print scanner.
Sent from my moto g(6) plus using Tapatalk
Click to expand...
Click to collapse
Do you mean twrp-3.2.1-4-evert.img by erfanoabdi
Is it safe to use and why it isn't listed on TWRP official site?
Mr. Nerd_ said:
Do you mean twrp-3.2.1-4-evert.img by erfanoabdi
Is it safe to use and why it isn't listed on TWRP official site?
Click to expand...
Click to collapse
Yes that is the bootable IMG. There is a installer zip to but that version does not support encryption/decryption.
As for the website, because it is not official. Just because it's not official doesn't always mean it's unsafe.
Sent from my moto g(6) plus using Tapatalk
Xplorer4x4 said:
Yes that is the bootable IMG. There is a installer zip to but that version does not support encryption/decryption.
As for the website, because it is not official. Just because it's not official doesn't always mean it's unsafe.
Sent from my moto g(6) plus using Tapatalk
Click to expand...
Click to collapse
When I'm trying to flash recovery I'm getting this error:
C:\adb\platform-tools>fastboot flash recovery twrp.img
Sending 'recovery' (29516 KB) OKAY [ 0.666s]
Writing 'recovery' (bootloader) Invalid partition name recovery
FAILED (remote failure)
Finished. Total time: 0.692s
Mr. Nerd_ said:
When I'm trying to flash recovery I'm getting this error:
C:\adb\platform-tools>fastboot flash recovery twrp.img
Sending 'recovery' (29516 KB) OKAY [ 0.666s]
Writing 'recovery' (bootloader) Invalid partition name recovery
FAILED (remote failure)
Finished. Total time: 0.692s
Click to expand...
Click to collapse
that's a bootable image. You can boot it with thi command "fastboot boot twrp.img". If you want to install twrp, flash zip installer from twrp
jekyll86 said:
that's a bootable image. You can boot it with thi command "fastboot boot twrp.img". If you want to install twrp, flash zip installer from twrp
Click to expand...
Click to collapse
Thanks, it worked
Related
Hey guys.
I have this little problem with my Android One. I can't flash 'SYSTEM' via fastboot.
har****@har****:~ fastboot flash system system.img
target reported max download size of 134217728 bytes
erasing 'system'...
OKAY [ 0.702s]
sending sparse 'system' (131071 KB)...
OKAY [ 4.725s]
writing 'system'...
FAILED (remote: sparse image size span overflow.)
finished. total time: 5.431s
har****@har****:~
Click to expand...
Click to collapse
I got this error while flashing Ubuntu Touch (Which I built), Android 5.0 (Which, again, I built) and also AOKP's system.img
Any solutions to this?
rhar**** said:
Hey guys.
I have this little problem with my Android One. I can't flash 'SYSTEM' via fastboot.
I got this error while flashing Ubuntu Touch (Which I built), Android 5.0 (Which, again, I built) and also AOKP's system.img
Any solutions to this?
Click to expand...
Click to collapse
Hey ,
I am facing the same problem after building aosp 4.4.4
Did you find a solution ?
joshuab227 said:
Hey ,
I am facing the same problem after building aosp 4.4.4
Did you find a solution ?
Click to expand...
Click to collapse
Not yet
rhar**** said:
Not yet
Click to expand...
Click to collapse
I was unable to flash it via fastboot but could flash it by creating an ota zip.
joshuab227 said:
I was unable to flash it via fastboot but could flash it by creating an ota zip.
Click to expand...
Click to collapse
Same here.
But many a times you need to flash from fastboot. Flashing zip isn't practical when you are making a new os
BTW I compiled resurrection remix lp with your device tree @rhar****, when I try to flash it fails to mount system. Any clue what I can do?
Sent from my Android One using XDA Free mobile app
akhil1999 said:
BTW I compiled resurrection remix lp without your device tree @rhar****, when I try to flash it fails to mount system. Any clue what I can do?
Sent from my Android One using XDA Free mobile app
Click to expand...
Click to collapse
You need to take a log of what's the problem and debug it. Its not the device tree thing, though
https://docs.google.com/file/d/0B1MuHk_wIzdxUEZpdnozVUMtM0E/edit?usp=docslist_api
That's my recovery.log
Please help if you can.
Thanks.
akhil1999 said:
https://docs.google.com/file/d/0B1MuHk_wIzdxUEZpdnozVUMtM0E/edit?usp=docslist_api
That's my recovery.log
Please help if you can.
Thanks.
Click to expand...
Click to collapse
Better talk in pm
I only started trying this since last night but I am unable to flash factory images. I tried the 5.1.1 non-tmobile image, as well as today's 6.0 release image. (Hardware: Macbook Pro w/ OS 10.11 El Capitan)
I've tried both flash-all.sh as well as fastboot update and both end up with the same error message:
Code:
target reported max download size of 536870912 bytes
sending 'bootloader' (10387 KB)...
OKAY [ 0.327s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.726s]
finished. total time: 1.053s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
sending 'radio' (115487 KB)...
OKAY [ 3.616s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.532s]
finished. total time: 5.149s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
fastboot(3602,0xa2ed1000) malloc: *** mach_vm_map(size=2094395392) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 2092300200 bytes
error: update package missing system.img
Looking at the image-shamu-mra58k.zip file, it does not contain any .sig files. Only userdata.img, system.img, recovery.img, cache.img, boot.img and android-info.txt.
Any idea what's going on and how to fix it?
Unlock the bootloader?
MrBrady said:
I only started trying this since last night but I am unable to flash factory images. I tried the 5.1.1 non-tmobile image, as well as today's 6.0 release image. (Hardware: Macbook Pro w/ OS 10.11 El Capitan)
I've tried both flash-all.sh as well as fastboot update and both end up with the same error message:
Looking at the image-shamu-mra58k.zip file, it does not contain any .sig files. Only userdata.img, system.img, recovery.img, cache.img, boot.img and android-info.txt.
Any idea what's going on and how to fix it?
Click to expand...
Click to collapse
Just manually flash the images.
iRub1Out said:
Unlock the bootloader?
Click to expand...
Click to collapse
Bootloader is unlocked and I am running TWRP recovery. Does it need to be stock recovery and locked bootloader to flash the factory images?
danarama said:
Just manually flash the images.
Click to expand...
Click to collapse
Like this?
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
yes, actually, exactly like that.
Are you guys getting the red "Corrupt..." triangle during boot when using this w/ TWRP?
Or you can use the gui Nexus toolkit for factory images.
Not as "fun" but works.
530farm said:
Are you guys getting the red "Corrupt..." triangle during boot when using this w/ TWRP?
Click to expand...
Click to collapse
I get a dead Android with a red triangle when trying to boot into recovery. It seems my TWRP got toasted somehow. However I do not receive any corrupt notice when booting the device normally.
I performed a fastboot flash of TWRP 2.8.7.1 and on first boot, TWRP gave a warning where I had to accept that it was OK to modify the system. I have never seen that before. After installing TWRP I do get the corrupt device message upon boot.
useranonymous said:
Or you can use the gui Nexus toolkit for factory images.
Not as "fun" but works.
Click to expand...
Click to collapse
Is there one available for Mac?
useranonymous said:
Or you can use the gui Nexus toolkit for factory images.
Not as "fun" but works.
Click to expand...
Click to collapse
If I used Nexus Toolkit what should i choose to flashed it. Fastboot: System?
MrBrady said:
Is there one available for Mac?
Click to expand...
Click to collapse
You can try this one.
http://forum.xda-developers.com/nexus-6/development/toolkit-nexus-6-one-click-mac-toolkit-t2956434
---------- Post added at 06:48 PM ---------- Previous post was at 06:42 PM ----------
chipis said:
If I used Nexus Toolkit what should i choose to flashed it. Fastboot: System?
Click to expand...
Click to collapse
I used the WUG toolkit and used flash Stock +Unroot with the Other/Browse option for picking the downloaded img.
I also checked "Force Flash Mode" and let the tool run through the script.
useranonymous said:
You can try this one.
http://forum.xda-developers.com/nexus-6/development/toolkit-nexus-6-one-click-mac-toolkit-t2956434
---------- Post added at 06:48 PM ---------- Previous post was at 06:42 PM ----------
I used the WUG toolkit and used flash Stock +Unroot with the Other/Browse option for picking the downloaded img.
I also checked "Force Flash Mode" and let the tool run through the script.
Click to expand...
Click to collapse
Sorry iam noob to this. So i have a custom rom. should go and flash a stock.?
Because ones i press what you said it jumps to look for image but it dont find anything
chipis said:
Sorry iam noob to this. So i have a custom rom. should go and flash a stock.?
Because ones i press what you said it jumps to look for image but it dont find anything
Click to expand...
Click to collapse
Do you want to go to stock?
I did because I want to try M which I downloaded from here.
https://developers.google.com/android/nexus/images
Of course this wipes your device so please keep that in mind.
Going from 5.1 to 6 requires a wipe especially with a custom ROM.
You will lose root until rooting the stock M build comes out.
I'm OK with being stock for now since I use Google pay.
But I'll play with custom M ROMs when they come out later.
useranonymous said:
Do you want to go to stock?
I did because I want to try M which I downloaded from here.
https://developers.google.com/android/nexus/images
Of course this wipes your device so please keep that in mind.
Going from 5.1 to 6 requires a wipe especially with a custom ROM.
You will lose root until rooting the stock M build comes out.
I'm OK with being stock for now since I use Google pay.
But I'll play with custom M ROMs when they come out later.
Click to expand...
Click to collapse
Jisus i feel dumm, ok i have flashed the image before M, Because i was on the LVY48E
Sorry i coming from samsung device. Nexus is a little different.
Now I just download the M Where should go To flashed what just downloaded using the Nexus Root Tool Kit?
lose root if flash M ??
useranonymous said:
Do you want to go to stock?
I did because I want to try M which I downloaded from here.
https://developers.google.com/android/nexus/images
Of course this wipes your device so please keep that in mind.
Going from 5.1 to 6 requires a wipe especially with a custom ROM.
You will lose root until rooting the stock M build comes out.
I'm OK with being stock for now since I use Google pay.
But I'll play with custom M ROMs when they come out later.
Click to expand...
Click to collapse
If I manually flash M, I'll lose root ? Oh, say it isn't so .
530farm said:
Are you guys getting the red "Corrupt..." triangle during boot when using this w/ TWRP?
Click to expand...
Click to collapse
Can you boot into the system? My nexus 6 will just turns itself off after the message
redlee90 said:
Can you boot into the system? My nexus 6 will just turns itself off after the message
Click to expand...
Click to collapse
Yes, it boots fine.
I can even get root by flashing an M-based kernel, then the SuperSU 2.49 zip. However when I flash apps that install as System Apps (like ViPER4Android), they don't seem to install. It's almost like TWRP doesn't have root access.
ok finally flash the image M Using Nexus Root ToolKIt
Don't use toolkits if you don't know what you're doing. Use manual fastboot steps.
danarama said:
Don't use toolkits if you don't know what you're doing. Use manual fastboot steps.
Click to expand...
Click to collapse
Good point.
Have a good guide to do this for us noobs?
IF YOU PLAN ON INSTALLING ANY CUSTOM ROM CHECK THAT YOUR RECOVERY IS ACCESSABLE!!!
If you have lost access to your stock recovery on your Amazon Fire 7 5th Gen (Ford) for whatever reason I would highly recommend restoring your recovery before doing any further customization to your device. Without recovery you have absolutely nothing to fall back on if your device becomes inoperable. If you have tried flashing any type of custom recovery directly to your device its more then likely you have lost access to your stock recovery. Hopefully youv made it to this thread before it was too late and luckily its a pretty simple process to restore your access.
Before we begin you must have a working OS for this process to work. If your device will not successfully boot then you can not complete the steps necessary to restore access to your recovery.
First lets
• Download Fire 7 Stock Recovery Image https://app.box.com/s/tjju5dptvsmsfjienf37siip8j6ch7wo
• Download and install the Flashfire App http://download.chainfire.eu/950/FlashFire/FlashFire-v0.30-20160331135212.apk
Next we'll
• Open the Flashfire App and allow it root access
• Press the red "+" button and select "Flash Firmware Package"
• Browse to the folder containing the Fire 7 Stock Recovery Image you previously downloaded and select it then press the "√" in the upper right corner
• Change Reboot option from "Normal" to "Recovery"
• Press the "FLASH" then "OK"
• Flashfire will reboot into recovery when its complete (Usually only takes a couple mins but its possible it may run for more)
It is also possible to restore access to recovery using Flashify
• Download and install Flashify
http://www.apkmirror.com/apk/christian-gollner/flashify/
• Press "Select Recovery Image" then choose file
• Browse to the Fire 7 Stock Recovery Image you downloaded earlier, select it and choose "Yup"
• Once complete reboot to recovery to confirm
That's it now you're back in action!!!
Has any one try flashing in fastboot mode?
Sent from my XT1080 using XDA Labs
sd_shadow said:
Has any one try flashing in fastboot mode?
Sent from my XT1080 using XDA Labs
Click to expand...
Click to collapse
Thought about that this morning as well. If no one else confirms before I get off work here shortly I will try then. (Especially like to see someone with a hard brick attempt it) In theory it seems it should work since the image seems to carry the signature from Amazon. Well at least that's what I picked up from researching for a fix to restore access to recovery on two of my fires.
Doesn't appear to work. My recovery randomly stopped working while I was trying to get SlimLP to install (unsuccessfully). Details Here
If I try to flash it:
sending 'recovery' (16384 KB)...
OKAY [ 0.474s]
writing 'recovery'...
FAILED (remote: Flashing not allowed)
finished. total time: 0.480s
Click to expand...
Click to collapse
If I try to boot to it, same error as if you try to boot to TWRP:
D:\Downloads\android-sdk-windows\platform-tools>fastboot boot fire7-stock-recovery.img
downloading 'boot.img'...
OKAY [ 0.531s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.535s
Click to expand...
Click to collapse
knicknut said:
Doesn't appear to work. My recovery randomly stopped working while I was trying to get SlimLP to install (unsuccessfully). Details Here
If I try to flash it:
sending 'recovery' (16384 KB)...
OKAY [ 0.474s]
writing 'recovery'...
FAILED (remote: Flashing not allowed)
finished. total time: 0.480s
If I try to boot to it, same error as if you try to boot to TWRP:
D:\Downloads\android-sdk-windows\platform-tools>fastboot boot fire7-stock-recovery.img
downloading 'boot.img'...
OKAY [ 0.531s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.535s
Click to expand...
Click to collapse
used ?
Code:
fastboot -i 0x1949 flash fire7-stock-recovery.img
Sent from my XT1080 using XDA Labs
sd_shadow said:
used ?
Code:
fastboot -i 0x1949 flash fire7-stock-recovery.img
Sent from my XT1080 using XDA Labs
Click to expand...
Click to collapse
Took me a minute to realize I had to put "recovery" after flash, but even after I did, I sadly got the same result:
sending 'recovery' (16384 KB)...
OKAY [ 0.534s]
writing 'recovery'...
FAILED (remote: Flashing not allowed)
finished. total time: 0.541s
Click to expand...
Click to collapse
knicknut said:
used ?
Took me a minute to realize I had to put "recovery" after flash, but even after I did, I sadly got the same result:
sending 'recovery' (16384 KB)...
OKAY [ 0.534s]
writing 'recovery'...
FAILED (remote: Flashing not allowed)
finished. total time: 0.541s
Click to expand...
Click to collapse
yes, my bad
Sent from my XT1080 using XDA Labs
Now that flashfire allows us to restore backups from fastboot could we restore a back up of stock recovery or system to get flashfire bricked tablets working again?
vuvious said:
Now that flashfire allows us to restore backups from fastboot could we restore a back up of stock recovery or system to get flashfire bricked tablets working again?
Click to expand...
Click to collapse
Unfortunately I don't believe so. We need a key to unlock the actual ability to flash via Fastboot. As far as I know at least
vuvious said:
Now that flashfire allows us to restore backups from fastboot could we restore a back up of stock recovery or system to get flashfire bricked tablets working again?
Click to expand...
Click to collapse
I suspect that capability is coming (foundation is in v0.32) but probably not for this device due to fastboot restrictions I posed by Amazon.
Sorry cross posted removed
Robin Son said:
stuck with 5.1 will not boot to stock recovery
was going to try using fastboot with 5.3.1 stock img.file but can't find one
TGT123 super tool will reboot my A-fire but will not install stock recovery
O yeah and i lost root and no playstore
Anyone had this problem and fixed???
Click to expand...
Click to collapse
Please don't cross post. Answered here: http://forum.xda-developers.com/ama...stom-rom-fireos-5-3-1-0-t3418541/post70006008
Hi guys!
Download : Click Here
Only for Testing.
XDA:DevDB Information
TWRP 3.1.1 for Mi-A1 (tissot_sprout), Tool/Utility for the Xiaomi Mi A1
Contributors
pvineeth97
Source Code: https://github.com/PVineeth/android_device_xiaomi_tissot_sprout_recovery
Version Information
Status: Testing
Created 2017-10-02
Last Updated 2017-10-11
Reserved
Reserved
Nice work ! Tks, waiting for uptades ... I will get the A1 soon and is nice to see the development for this device
When there isn't any recovery partition , why u want to flash it to recovery
Instead of flashing directly, boot into recovery.
fastboot boot twrp.img
Sent from my Mi A1 using XDA Labs
m.atif said:
When there isn't any recovery partition , why u want to flash it to recovery
Click to expand...
Click to collapse
Yeah you are right. I need to make ZIP of some sorts. I know it is A/B system so recovery is stored in boot partition. I will update the flashing part in some time.
Ron1209 said:
Instead of flashing directly, boot into recovery.
fastboot boot twrp.img
Sent from my Mi A1 using XDA Labs
Click to expand...
Click to collapse
When i used ,,fastboot boot boot.img", it did not boot up into twrp, instead it rebooted itself into android, with this output:
Code:
downloading 'boot.img'...
OKAY [ 0.812s]
booting...
OKAY [ 0.587s]
finished. total time: 1.432s
ves626 said:
When i used ,,fastboot boot boot.img", it did not boot up into twrp, instead it rebooted itself into android, with this output:
Code:
downloading 'boot.img'...
OKAY [ 0.812s]
booting...
OKAY [ 0.587s]
finished. total time: 1.432s
Click to expand...
Click to collapse
I will fix in next update.
@pvineeth97 , I would like to be a tester, n can also help in making flashable zip, contact me if interested
pvineeth97 said:
When i used ,,fastboot boot boot.img", it did not boot up into twrp, instead it rebooted itself into android, with this output:
I will fix in next update.
Click to expand...
Click to collapse
Same here
Just to report in case
No complaints. Its initial phase and time and repeated tries are key to success.
Best of luck for future
@pvineeth97, I would like to be a tester, n can also make a flashable zip, contact me if interested...
ghpranav said:
@pvineeth97 , I would like to be a tester, n can also help in making flashable zip, contact me if interested
Click to expand...
Click to collapse
I am trying to work on it wait.
Plz inform once a new build is up
Moderator Information,
Thread closed at OP's request.
Why don't you add the twrp recovery in boot.img ? it will be easier to flash and keep the custom recovery. :/
Kudos to developer! Happy to see Mi A1 development started. I wish all the best
abkdmn said:
Why don't you add the twrp recovery in boot.img ? it will be easier to flash and keep the custom recovery. :/
Click to expand...
Click to collapse
Because no one will inject TWRP to each boot, in each ROM.
Displax said:
Because no one will inject TWRP to each boot, in each ROM.
Click to expand...
Click to collapse
I don't own a MI A1 for personally so i can't tell about the partitions tho, but i had a Sony Xperia C3 which condition was same as MI A1 , where boot and recovery were both in boot partition.
ves626 said:
When i used ,,fastboot boot boot.img", it did not boot up into twrp, instead it rebooted itself into android, with this output:
Code:
downloading 'boot.img'...
OKAY [ 0.812s]
booting...
OKAY [ 0.587s]
finished. total time: 1.432s
Click to expand...
Click to collapse
this is incorrect. if you want to boot to twrp recovery then issue the command "fastboot boot twrp.img", not the "boot.img".
I have a moto g6 plus, and whenever i try to flash the official TWRP is get this error.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.2.3-0-evert.img
target reported max download size of 536870912 bytes
sending 'recovery' (29352 KB)...
OKAY [ 0.836s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.841s
The phone itself works perfectly and is rooted, with magisk.
I can however boot into TWRP using fastboot boot twrp-3.2.3-0-evert.img.
If i boot into recovery mode right now my phone says no command.
I'd rather not have to reset my entire phone or blankflash, because of the risk this brings and losing all my files.
Any help is appreciated.
koningboy18 said:
I have a moto g6 plus, and whenever i try to flash the official TWRP is get this error.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.2.3-0-evert.img
target reported max download size of 536870912 bytes
sending 'recovery' (29352 KB)...
OKAY [ 0.836s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.841s
The phone itself works perfectly and is rooted, with magisk.
I can however boot into TWRP using fastboot boot twrp-3.2.3-0-evert.img.
If i boot into recovery mode right now my phone says no command.
I'd rather not have to reset my entire phone or blankflash, because of the risk this brings and losing all my files.
Any help is appreciated.
Click to expand...
Click to collapse
The official twrp bricks the g6+ use the unofficial twrp. The official twrp doesn't decrypt data which is needed. if you actually took the time you read any thread about the g6+ on here you would know that....start reading everything and stop skimming through
I read about this after making the post, my mistake. Nonetheless same problem with unofficial builds.
ninjakira said:
The official twrp bricks the g6+ use the unofficial twrp. The official twrp doesn't decrypt data which is needed. if you actually took the time you read any thread about the g6+ on here you would know that....start reading everything and stop skimming through
Click to expand...
Click to collapse
I contacted TWRP Devs and got them to remove official TWRP for now! Hopefully cuts down and eliminates these posts soon enough!
koningboy18 said:
I read about this after making the post, my mistake. Nonetheless the same problem with unofficial builds.
Click to expand...
Click to collapse
Then where did you read to flash twrp? You didn't because it's been documented many times DO NOT FLASH TWRP. Boot it.
Also, the error explains itself. There is no longer a recovery partition on a/b devices.
Xplorer4x4 said:
I contacted TWRP Devs and got them to remove official TWRP for now! Hopefully cuts down and eliminates these posts soon enough!
Then where did you read to flash twrp? You didn't because it's been documented many times DO NOT FLASH TWRP. Boot it.
Also, the error explains itself. There is no longer a recovery partition on a/b devices.
Click to expand...
Click to collapse
Well i'm new to the whole modding scene, and when i got my phone pretty much every tutorial to root my phone told me to flash TWRP not boot it. Is the recovery partition removed on every Moto g6+? Is there a way to still flash TWRP, once a stable build comes out, or is it only bootable and will be forever? Why is it that in the tutorials people did have the recovery partition? Thanks.
Your tutorials are generic or not specific to our device or out dated. Probably all of the above. All the info you need is in the g6 forums here..but sadly it is spread out in various places.
Eventually we should have flashable TWRP. Its just not a top priority because it works, it's just tedious using fastboot to do it.
I am compiling a very detailed guide specific to our device as we speak. I am also doing my best to keep it noob friendly. I plan to have it done in the next 24 hours but plans can always change. My guide will consolidate all information to one single thread.
Xplorer4x4 said:
Your tutorials are generic or not specific to our device or out dated. Probably all of the above. All the info you need is in the g6 forums here..but sadly it is spread out in various places.
Eventually we should have flashable TWRP. Its just not a top priority because it works, it's just tedious using fastboot to do it.
I am compiling a very detailed guide specific to our device as we speak. I am also doing my best to keep it noob friendly. I plan to have it done in the next 24 hours but plans can always change. My guide will consolidate all information to one single thread.
Click to expand...
Click to collapse
The tutorial was specific to my device, but they probably have a tutorial template, and they just change the name of the device and the TWRP download link. Also, I read your tutorial about installing LineageOS15.1, I might try installing it. Thanks for all the help.