Database Develop

Issues with flashing TWRP to tablet

I am trying to go through the process of flashing a custom recovery so that I can get off of stock and on to a custom rom. I have gone through the following steps:
1) downloaded the latest drivers
2) downloaded the latest version of fastboot
3) downloaded twrp 2.8.1.0 and checked the MD5 for the program
4) enabled the usb debugging, signed on as an administrator in my pc, and am using a 2.0 usb port
5) have verified the conenction between tablet and PC.
I get the following result:
C:\>fastboot devices
15C3E100910000000XXXXXXXX fastboot (I edited out a few numbers and replaced them with with x's, but got a pure result)
C:\>fastboot -i 0x0B05 flash recovery twrp.blob
target reported max download size of 643825664 bytes
sending 'recovery' (7024 KB)...
OKAY [ 0.964s]
writing 'recovery'...
OKAY [ 0.241s]
finished. total time: 1.213s
C:\>fastboot reboot
rebooting...
finished. total time: 0.021s
The recovery is not actually flashing over to the device. When I attempt the flash I do a fastboot reboot and power down afterwards, then try to boot back up to the recovery and instead I get the bried vision of the android and the blue bar underneath before it's promptly replaced by the dead android. The twrp.blob file is in the same directory as fastboot. I have tried deleting and re-downloading both the blob file and the drivers. I have tried using 2.8.0.1 and 2.8.1.0. Because TWRP wasn't working I tried flashing CWM and got exactly the same result. There doesn't seem to be an issue with the cable, since I can move other forms of data between the devices with no issue. I'm beating my head against the wall here, and am hoping that you guys might be able to provide me with some direction as to what else I might try/look for. Thanks all.

Are you sure you are using the correct recovery for your device? There is no version of TWRP that works with the TF701T.

Sleeepy2 said:
Are you sure you are using the correct recovery for your device? There is no version of TWRP that works with the TF701T.
Click to expand...
Click to collapse
I had been advised that the version for the TF700 would also work with the TF701T. However, I did use a CWM version specific to the TF701T with the same result you saw in the command window in my OP.

talion777 said:
I had been advised that the version for the TF700 would also work with the TF701T. However, I did use a CWM version specific to the TF701T with the same result you saw in the command window in my OP.
Click to expand...
Click to collapse
I am not sure who told you that but it is 100% wrong.
I am also not sure what the commands that you are sending are however you should just be doing
fastboot flash recovery recovery.img
Get the recovery from this link
http://droidbasement.com/asus/tf701t/recovery/

Sleeepy2 said:
I am not sure who told you that but it is 100% wrong.
I am also not sure what the commands that you are sending are however you should just be doing
fastboot flash recovery recovery.img
Get the recovery from this link
http://droidbasement.com/asus/tf701t/recovery/
Click to expand...
Click to collapse
Thanks Sleeepy, but as I mentioned in the OP I did the flash for the CWM recovery already, using exactly the link you sent me, with the exact same commands, and with the same results. No go.
P.P.S. - also tried juggling around the MTP and PTP modes (plug/unplug while on/off) to ensure recognition and it seems fine both ways. Someone else had said they freed up their drivers that way but it made no difference on my end.
P.S. - Here, just so that you see, here are the command window results for th CWM recovery, just for clarity's sake:
C:\adb 2>fastboot devices
15C3E100910000000XXXXXXXX fastboot
C:\adb 2>fastboot flash recovery recovery.img
target reported max download size of 643825664 bytes
sending 'recovery' (6646 KB)...
OKAY [ 0.910s]
writing 'recovery'...
OKAY [ 0.230s]
finished. total time: 1.140s
C:\adb 2>fastboot reboot
rebooting...
finished. total time: 0.020s
C:\adb 2>

That's really odd.
I just downloaded the most recent version and tried re-flashing just to make sure and I had no issues...
Can you boot the recovery without flashing it?
fastboot boot recovery.img
Sorry, this defiantly not strong point but I will try to help.

Sleeepy2 said:
That's really odd.
I just downloaded the most recent version and tried re-flashing just to make sure and I had no issues...
Can you boot the recovery without flashing it?
fastboot boot recovery.img
Sorry, this defiantly not strong point but I will try to help.
Click to expand...
Click to collapse
yes, I can boot the recovery. Am I able to use the temp image to install the recovery into the tablet, or to import the files I need to do so?

talion777 said:
yes, I can boot the recovery. Am I able to use the temp image to install the recovery into the tablet, or to import the files I need to do so?
Click to expand...
Click to collapse
The temp image will work just like normal.

Sleeepy2 said:
The temp image will work just like normal.
Click to expand...
Click to collapse
except that I will always need to be connected to my PC to use it. How do I actually make that the default recovery in my tablet? It just seems bizarre to me that I can boot the image but that I can't flash it. Also, assuming I used the image to flash a custom ROM what happens when the temp image is shut off and the recovery reverts to stock? Would the ROM work with a stock recovery?
Was able to use the CWM image to install SuperSU and root the tablet. Still can't get the recovery to flash over.

Wait... what version of bootloader do you have?
You are unlocked and updated to the most recent ASUS version right...

Sleeepy2 said:
Wait... what version of bootloader do you have?
You are unlocked and updated to the most recent ASUS version right...
Click to expand...
Click to collapse
I'm on 11.4.1.17, and yes I'm on the latest ASUS update.

Damn... that was my last guess. You need to get the attention of someone smarter than me like pershoot or berndblb
Sorry I can't help any better.

Thanks Sleeepy, you've already been a big help and I really appreciate the effort!

talion777 said:
Thanks Sleeepy, you've already been a big help and I really appreciate the effort!
Click to expand...
Click to collapse
Just for kicks try to flash the CWM image with this:
Code:
fastboot -i 0x0B05 flash recovery recovery.img
The vendor ID should not be necessary - but it certainly wouldn't hurt to try....
And post the exact output please.

berndblb said:
Just for kicks try to flash the CWM image with this:
Code:
fastboot -i 0x0B05 flash recovery recovery.img
The vendor ID should not be necessary - but it certainly wouldn't hurt to try....
And post the exact output please.
Click to expand...
Click to collapse
You sir, would appear to be a genius. CWN successfully flashed to the tab. Excellent! Thanks so very much to both you and Sleeepy for your help. This was driving me absolutely bananas!

berndblb said:
Just for kicks try to flash the CWM image with this:
Code:
fastboot -i 0x0B05 flash recovery recovery.img
The vendor ID should not be necessary - but it certainly wouldn't hurt to try....
And post the exact output please.
Click to expand...
Click to collapse
God damn it. You step in with one comment and boom, like magic it works
And @talion777 glad you've got it working now

Sleeepy2 said:
God damn it. You step in with one comment and boom, like magic it works
And @talion777 glad you've got it working now
Click to expand...
Click to collapse
A lucky guess.. LOL
Actually I worked with talion on the Transformer forums on his problem, so it was not quite as magical as it may sound. [emoji56]

[Q] Unable to flash factory images

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?

Recovey change that goes worng

Hi all,
I'm trying to understand what did I do wrong.
I bought my device with an unlocked bootloader miui V8 (global rom).
I tried to flash TWRP recovey and MIUI PRO rom. I follow the steps that are mentioned here
and got soft brick - the device got stuck on the mi logo (with the unlock sign), even when I wait in patience the device just turned off.
- At the beginning I flashed the TWRP recovery by xuefer, boot into it and flashed the dm-verity disabler (as mentioned in the guide) and got error 1.
I reboot the device and it didn't boot.
- I boot to the recovery again and wipe the data - didn't boot.
Boot to recovery again and wipe to factory
-I flashed the MIUI PRO rom and the device still didn't boot.
I tired to flash the TWRP recovery by iscle - now the dm-verity disabler succeed but the device still didn't boot.
made the wiping steps as above again - and the device still got stuck at the mi logo.
At any step I manged to boot into the TWRP recovery and fastboot mode.
My lest option was to go back to the global stock rom using MiFlash
Now I'm on Global MIUI 9 with locked bootloadr
What did I do wrong?
I want to unlock the bootloader and to get back my control on my device.
Please advice
Thanks

Download the latest TWRP on this forum. Flash it. After, go to twrp, wipe data, cache, flash MIUI PRO rom, and after flash also flash the latest SuperSU zip. Then try again and see if it's gonna boot up.

how sure were you that the device had an unlocked bootloader when you purchased it? if it was brand new, certainly its bootloader is locked.

Do you have an open padlock when your phone is booting ?
Remember to boot to twrp just after flashing and before booting to the rom.

Thank you all for your answers!
Thank you all for your answers!
ekin_strops said:
Download the latest TWRP on this forum. Flash it. After, go to twrp, wipe data, cache, flash MIUI PRO rom, and after flash also flash the latest SuperSU zip. Then try again and see if it's gonna boot up.
Click to expand...
Click to collapse
This is exectly what I've done. and I't didn't worked.
Can you please point me to exact TWRP that you meant?
What about the dm-verity disabler ? it isn't necessary?
ondoy1943 said:
how sure were you that the device had an unlocked bootloader when you purchased it? if it was brand new, certainly its bootloader is locked.
Click to expand...
Click to collapse
I've checked the bootloader status in the Dev menu and with fastboot (fastboot oem device-info).
In addtion to all I had the open padlock sign when the turned on the device.
lightman33 said:
Do you have an open padlock when your phone is booting ?
Remember to boot to twrp just after flashing and before booting to the rom.
Click to expand...
Click to collapse
I had the open padlock sign.
Now unfortunately I flashed with MiFlash the global rom and my bootloader is locked.
I want to know the mistake I've done - so I don't fail with it again after I'll get the approval to open my bootloader.
Thanks

no mistake, they are three batches files in the rom zip. One of them is relocking the bootloader.
Flash_all with without erase data
Flash_all with wipe data
Flash_all with relock bootloader
I don't know miflash interface but you unfortunately choose the third choice. You need now to unlock your bootloader again (maybe by creating a new xiaomi account, not sure of this).

lightman33 said:
no mistake, they are three batches files in the rom zip. One of them is relocking the bootloader.
Flash_all with without erase data
Flash_all with wipe data
Flash_all with relock bootloader
I don't know miflash interface but you unfortunately choose the third choice. You need now to unlock your bootloader again (maybe by creating a new xiaomi account, not sure of this).
Click to expand...
Click to collapse
I'm sorry if you miss understood me, but I meant to the mistake I've made with the TWERP and rom flashing.
I can't figured out what I've did wrong.

Sorry if was not clear but the problem could be here :
Now unfortunately I flashed with MiFlash the global rom and my bootloader is locked.
II think you choose in Mi Flash tool an option to flash with re-lock the bootloader (don"t know how it's designed in the app because I flashed my phone manually, using one of the 3 batch files).
Hope it will help you.

lightman33 said:
Sorry if was not clear but the problem could be here :
Now unfortunately I flashed with MiFlash the global rom and my bootloader is locked.
II think you choose in Mi Flash tool an option to flash with re-lock the bootloader (don"t know how it's designed in the app because I flashed my phone manually, using one of the 3 batch files).
Hope it will help you.
Click to expand...
Click to collapse
Thank you for your answer.
I will open my bootloader,
I'm just trying to understand which TWRP version to flash for the miui pro rom (or any other)
And what is the process (or "the correct steps") to :
* Flash the TWRP recovery
* And to flash any other different rom from the miui stock.
Thanks

I took the TWRP from this forum, this is my md5 if you want to check yours :
f52ff052971b67df097d4cfa8a2ec162 twrp-3.2.0-0-oxygen.img
And this is my howto :
$ sudo fastboot flash recovery twrp-3.2.0-0-oxygen.img
target reported max download size of 536870912 bytes
sending 'recovery' (16196 KB)...
OKAY [ 0.504s]
writing 'recovery'...
OKAY [ 0.095s]
finished. total time: 0.600s
$ sudo fastboot boot twrp-3.2.0-0-oxygen.img
downloading 'boot.img'...
OKAY [ 0.487s]
booting...
OKAY [ 0.576s]
finished. total time: 1.063s
For the ROM, I took file here : http://bigota.d.miui.com/7.12.8/oxy....8_20171208.0000.00_7.1_global_93a8045184.tgz
Filename : oxygen_global_images_7.12.8_20171208.0000.00_7.1_global_93a8045184
From forum : http://en.miui.com/thread-1273027-1-1.html
and the command to flash was (after unzip the file) :
$ sudo ./flash_all_except_storage.sh
Beginning of the log :
product: oxygen
erasing 'boot'...
OKAY [ 0.027s]
finished. total time: 0.027s
erasing 'sec'...
OKAY [ 0.021s]
finished. total time: 0.021s
target reported max download size of 536870912 bytes
sending 'crclist' (0 KB)...
OKAY [ 0.040s]
writing 'crclist'...
OKAY [ 0.020s]
finished. total time: 0.060s
target reported max download size of 536870912 bytes
sending 'sparsecrclist' (0 KB)...
OKAY [ 0.040s]
writing 'sparsecrclist'...
Hope it will help you...

ymca said:
Thank you for your answer.
I will open my bootloader,
I'm just trying to understand which TWRP version to flash for the miui pro rom (or any other)
And what is the process (or "the correct steps") to :
* Flash the TWRP recovery
* And to flash any other different rom from the miui stock.
Thanks
Click to expand...
Click to collapse
Hi! As others have already told you,
What I would do is to completely format the phone with Mi Flash (download the latest global stable fastboot version from http://en.miui.com/a-234.html), then flash it to the phone using the Flash All option, then flash my recovery or the one from xuefer (the one you prefer, both work), if you are flashing miui pro I think there is no need to flash the dm-verity file, so just wipe system + data + cache and flash miuipro.zip

Thank you all for your replais !
I will try and update right after I'll get the bootloader unlock approval.
Meanwhile you all have a great day !

Having trouble flashing twrp.

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.

Can't flash vendor.img but i have TWRP [What to do ?]

Hi guys , i was running AOSIP PIE rooted and bootloader unlocked. I did an update of Magisk. And then i couldn't flash twrp it was not working , i could still boot phone normally and phone run smooth. Someone told me to flash TWRP with flashify and i did. Here the problems started , i started having error , can't boot anywhere etc...
I followed this tutorial https://forum.xda-developers.com/hua...g-to-t3932203/ for last solution .
But unfortunatly i can't flash VENDOR.img in fastboot , i can flash all except VENDOR.img it says
C:\ADB>fastboot flash vendor VENDOR.img
target reported max download size of 471859200 bytes
sending sparse 'vendor' 1/2 (460796 KB)...
OKAY [ 10.697s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
finished. total time: 10.711s
I have flashed with success TWRP twrp-3.3.1-0-charlotte , i can get to it but there is no files inside the phone and it's not supporting SD cards to i don't have any ROM to flash ...
Do you guys have any idea about what to do ?
Thank you very much

I need help :'(

I had that.
Phone was completely dead, needed a new board.

chrissyyyw said:
I had that.
Phone was completely dead, needed a new board.
Click to expand...
Click to collapse
Are you sure of it ? did you buy it ?
You succefuly booted to twrp and tried to flash ROM ?
Because i used ADB command PUSH and managed to get ROM into /data/ folder in my phone , so i'm trying to flash them but it's not working at the end i reboot to fastboot
DId that happen to you too ?

benkiller47 said:
Are you sure of it ? did you buy it ?
You succefuly booted to twrp and tried to flash ROM ?
Because i used ADB command PUSH and managed to get ROM into /data/ folder in my phone , so i'm trying to flash them but it's not working at the end i reboot to fastboot
DId that happen to you too ?
Click to expand...
Click to collapse
I booted into fastboot, flashed the individual firmware files and it kept failing on the vendor.
I had a black screen with a red flashing LED on reboot. I claimed on my insurance and they replaced the board on the phone.
I checked on here and online for a resolution and it generally points to a hard brick.

benkiller47 said:
Hi guys , i was running AOSIP PIE rooted and bootloader unlocked. I did an update of Magisk. And then i couldn't flash twrp it was not working , i could still boot phone normally and phone run smooth. Someone told me to flash TWRP with flashify and i did. Here the problems started , i started having error , can't boot anywhere etc...
I followed this tutorial https://forum.xda-developers.com/hua...g-to-t3932203/ for last solution .
But unfortunatly i can't flash VENDOR.img in fastboot , i can flash all except VENDOR.img it says
C:\ADB>fastboot flash vendor VENDOR.img
target reported max download size of 471859200 bytes
sending sparse 'vendor' 1/2 (460796 KB)...
OKAY [ 10.697s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
finished. total time: 10.711s
I have flashed with success TWRP twrp-3.3.1-0-charlotte , i can get to it but there is no files inside the phone and it's not supporting SD cards to i don't have any ROM to flash ...
Do you guys have any idea about what to do ?
Thank you very much
Click to expand...
Click to collapse
You must use OTG! Probably Flashify borked a partition,but i don't think it borked vendor.
However, you should still be able to flash a FullOTA with TWRP + NoCheck combo.
If you can't manage that, hit me on Telegram,i'm @Pretoriano80 in there!

You can flash EMUI based FW using an OTA method. It should work. But it will lock your bootloader and you will have to unlock it again.

benkiller47 said:
Hi
Click to expand...
Click to collapse
Are you flashing the same or later firmware??