Develop Bugs

Nexus 5x Recovery Startup Loop

Hi
When I start up the boot loader or hit start, it just goes into recovery mode
When I turn my phone off normally and start it up, it just goes into recovery mode
I have an unlocked phone that's rather new, and I can't start it up
Thanks for the help

RingPvP said:
Hi
When I start up the boot loader or hit start, it just goes into recovery mode
When I turn my phone off normally and start it up, it just goes into recovery mode
I have an unlocked phone that's rather new, and I can't start it up
Thanks for the help
Click to expand...
Click to collapse
Running stock rom and stock kernel? Or custom rom kernel? Twrp recovery? Any other info
Sent from my Nexus 5X using Tapatalk

The_Automator said:
Running stock rom and stock kernel? Or custom rom kernel? Twrp recovery? Any other info
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I did *fastboot flash boot twrp.img. I mean't to flash it, but I was thinking twrp.img when trying to use boot.img
I couldn't undo it, and I knew I damaged my phone from this, but if there is a possible chance to fix it I am in even if I loose my data.
I was pretty sure this was the reason my Nexus 5x doesn't work, but I did nothing else other then that. Thanks for the help

RingPvP said:
I did *fastboot flash boot twrp.img. I mean't to flash it, but I was thinking twrp.img when trying to use boot.img
I couldn't undo it, and I knew I damaged my phone from this, but if there is a possible chance to fix it I am in even if I loose my data.
I was pretty sure this was the reason my Nexus 5x doesn't work, but I did nothing else other then that. Thanks for the help
Click to expand...
Click to collapse
So you can not boot to bootloader but can boot straight into twrp? But you can't flash the boot image from twrp because you cant use fastboot commands in twrp correct? maybe try this thread dedicated to unbricking phones
http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
Sent from my Nexus 5X using Tapatalk

The_Automator said:
So you can not boot to bootloader but can boot straight into twrp? But you can't flash the boot image from twrp because you cant use fastboot commands in twrp correct? maybe try this thread dedicated to unbricking phones
http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
No no no, I can boot into the bootloader. When I turn on my phone normally, it goes into recovery mode or in twrp. When I load the bootloader and start, it also goes into twrp.
I am pretty sure I can still fastboot commands in twrp, so that's good.
Sorry that I didn't add that, but I hope you know what the problem is because I really want my phone back.

RingPvP said:
No no no, I can boot into the bootloader. When I turn on my phone normally, it goes into recovery mode or in twrp. When I load the bootloader and start, it also goes into twrp.
I am pretty sure I can still fastboot commands in twrp, so that's good.
Sorry that I didn't add that, but I hope you know what the problem is because I really want my phone back.
Click to expand...
Click to collapse
To be clear recovery mode is the same as twrp and you can not use fastboot commands within TWRP you can use adb shell commands (im less familiar with these). You can not flash stock images from twrp only aftermarket roms, kernels, zips etc. Factory images are flashed from the bootloader using fastboot.
But if you can boot into the bootloader and use fastboot (verify by typing fastboot devices)
Download chainfires modified boot image (select bullhead for the Nexus 5X)
http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
extract the file so you have the .img file
Verify that your fastboot commands work fastboot devices (should always work from bootloader)
place chainfires image in the same folder as your fastboot exe.
fastboot flash boot boot.img
this should over write the boot image.
You could also just download the factory google image
https://developers.google.com/android/nexus/images?hl=en
Latest bullhead image ends with M. Extract the tar and place the extracted content in your (fastboot/adb folder) on your computer and just double click the flash-all.bat (note this will erase all data and give you a clean phone)
leave your phone until it says press any key to exit.

The_Automator said:
If you can boot into bootloader than the simplest thing to do is to download the nexus 5x image from googles factory image site. Extract that zip into your fastboot folder and double click flash all.bat. This will restore youre ur phone to factory defaults on the latest factory image. Alternatively you can just extract the boot image and use fastboot flash boot boot.img (but for this method youd have to download the factory image you already have installed which is why googlea self installer (flash-all.bat) would be easier
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I just flashed all.bat double clicking it, and it said finished. I turned on my phone already on bootloader, and it went back to twrp. I might have set my fastboot folder wrong, but the location is
C:\Program Files (x86)\Android\android-sdk\bullhead-mda89e if that helps.
Sorry if I am taking to much of your time away, but you've helped me a lot already

RingPvP said:
I just flashed all.bat double clicking it, and it said finished. I turned on my phone already on bootloader, and it went back to twrp. I might have set my fastboot folder wrong, but the location is
C:\Program Files (x86)\Android\android-sdk\bullhead-mda89e if that helps.
Sorry if I am taking to much of your time away, but you've helped me a lot already
Click to expand...
Click to collapse
usually the folder you would want to place the image into is the platform tools folder and you would want to place the files in the directory (not a sub directory) and the mda89e is the first release the newest release from google is
6.0.0 (MDB08M) Link f5233f827a44f99e26722e349f3c9445 5867cc27a23257a47688fe180ec272f1152ddde2
But within the factory image there should be a zip called something like image-bullhead-MDB08M.zip open that zip and extract just the boot.img to your platform tools folder. Then you should be able to use
fastboot flash boot boot.img

RingPvP said:
I just flashed all.bat double clicking it, and it said finished. I turned on my phone already on bootloader, and it went back to twrp. I might have set my fastboot folder wrong, but the location is
C:\Program Files (x86)\Android\android-sdk\bullhead-mda89e if that helps.
Sorry if I am taking to much of your time away, but you've helped me a lot already
Click to expand...
Click to collapse
In your case, it should be: C:\Program Files (x86)\Android\android-sdk\platform-tools\bullhead-mda89e
In this folder your should see fastboot.exe

The_Automator said:
To be clear recovery mode is the same as twrp and you can not use fastboot commands within TWRP you can use adb shell commands (im less familiar with these). You can not flash stock images from twrp only aftermarket roms, kernels, zips etc. Factory images are flashed from the bootloader using fastboot.
But if you can boot into the bootloader and use fastboot (verify by typing fastboot devices)
Download chainfires modified boot image (select bullhead for the Nexus 5X)
http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
extract the file so you have the .img file
Verify that your fastboot commands work fastboot devices (should always work from bootloader)
place chainfires image in the same folder as your fastboot exe.
fastboot flash boot boot.img
this should over write the boot image.
You could also just download the factory google image
https://developers.google.com/android/nexus/images?hl=en
Latest bullhead image ends with M. Extract the tar and place the extracted content in your (fastboot/adb folder) on your computer and just double click the flash-all.bat (note this will erase all data and give you a clean phone)
leave your phone until it says press any key to exit.
Click to expand...
Click to collapse
I don't know what to say, but thank you so much! I literally had a heart attack when it happened. You deserve more than a thanks for this .

RingPvP said:
I don't know what to say, but thank you so much! I literally had a heart attack when it happened. You deserve more than a thanks for this .
Click to expand...
Click to collapse
Happy to help glad you got your phone sorted
Sent from my Nexus 5X using Tapatalk

January security update?

I received the download on my 5x that's rooted. Will this break root for me?

Yes but you can easily re-root after re-installing TWRP

bg1906 said:
Yes but you can easily re-root after re-installing TWRP
Click to expand...
Click to collapse
I don't get this answer. I'm not able to install the security update on my rooted 5X, it reboots into TWRP and after I manually boot to system nothing happened. Tried it 3 times and still have root access.
Is the only way to get the security update by flashing an entire Android image? Or more specifically, can I update without wiping the phone?

Yeah OTA isn't going to work. You need to manually do it. You will need USB Drivers and ADB/Fastboot files. Create a folder on your desktop called Android and put the ADB files there. Now download the image. The image is an archive file. Extract the contents of archive files (there is one archive inside the original archive file you download), and after you have all the files extracted, modify the flash-all file (.bat if you are on Windows) with a text editor (Notepad) to remove the -w and save. This will prevent a wipe of your device. Connect your phone via USB and reboot to the bootloader. Open the folder you are in and if on Windows hold shift and right click and select Open Command Prompt. This will open a Command Prompt Window at the folder's location. Next type the command fastboot devices and press Enter. If everything is right, a device id will be returned. If that works, then go back to the folder and double click the flash-all.bat (Windows) and this will install the update. Root will be lost as will TWRP recovery. After the install, the phone will attempt to reboot. I always stop the reboot and go back to bootloader. Choose Recovery and go to the default recovery. You will see an Android figure with a red X. Simultaneously press the power and volume up & down buttons together repeatedly until you get the recovery menu (this may take a few times). Wipe Cache. Then reboot and you will have the update. You can then reinstall the latest version of TWRP by going to the TWRP website and downloading the latest version of TWRP. I usually put it in the same folder as the Android files and when it downloads rename it to twrp.img. Make sure you are in the bootloader and then at the command prompt all you need type is fastboot flash recovery twrp.img and this will install TWRP. You can then go to TWRP and flash SuperSU. I use the latest beta 2.66. But read here (http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3) for the details on the various versions of SuperSU Beta. *I take no responsibility for what may/may not happen to your phone as that depends on your level of comfort flashing/rooting etc*
Hope this helps. IF the flash-all gives you an error, you will need to flash the various parts of the update individually. If that happens, follow the instructions here for the update: https://www.androidpit.com/how-to-get-android-m-preview

This is exactly what I was looking for, thanks! Couldn't find it anywhere with Google which btw somehow returns mostly Nexus 5 results even when using "nexus 5x"...
I'll try this later on and reply with the results.

bosbeest said:
This is exactly what I was looking for, thanks! Couldn't find it anywhere with Google which btw somehow returns mostly Nexus 5 results even when using "nexus 5x"...
I'll try this later on and reply with the results.
Click to expand...
Click to collapse
Yes please let me know how this goes

Download the factory image and extract boot.img, system.img, and vendor.img. Nothing changed in the bootloader or radio with this update, so you do not need those.
Then, run the following:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot into TWRP and flash SuperSu again.
Then wipe cache/dalvik and reboot into system.
Info taken from This thread with the help of dmudd

bosbeest said:
This is exactly what I was looking for, thanks! Couldn't find it anywhere with Google which btw somehow returns mostly Nexus 5 results even when using "nexus 5x"...
I'll try this later on and reply with the results.
Click to expand...
Click to collapse
It's the same process with both phones.

Tomyk89 said:
Download the factory image and extract boot.img, system.img, and vendor.img. Nothing changed in the bootloader or radio with this update, so you do not need those.
Then, run the following:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot into TWRP and flash SuperSu again.
Then wipe cache/dalvik and reboot into system.
Info taken from This thread with the help of dmudd
Click to expand...
Click to collapse
Tried it, worked. Thanks a bunch!
Yaz75 said:
It's the same process with both phones.
Click to expand...
Click to collapse
Still doesn't make sense that you can't search for "5X"

Tomyk89 said:
Download the factory image and extract boot.img, system.img, and vendor.img. Nothing changed in the bootloader or radio with this update, so you do not need those.
Then, run the following:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot into TWRP and flash SuperSu again.
Then wipe cache/dalvik and reboot into system.
Info taken from This thread with the help of dmudd
Click to expand...
Click to collapse
Does this wipe data?

ch.ch1 said:
Does this wipe data?
Click to expand...
Click to collapse
Nope. The fastboot command has to have "userdata" included to do that.
Sent from my Nexus 5X using Tapatalk

ch.ch1 said:
Does this wipe data?
Click to expand...
Click to collapse
No

ch.ch1 said:
Does this wipe data?
Click to expand...
Click to collapse
No
Sent from my Nexus 5X using Tapatalk

ch.ch1 said:
Does this wipe data?
Click to expand...
Click to collapse
Nope!

SlimSnoopOS said:
Nope. The fastboot command has to have "userdata" included to do that.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Not true- the -w flag will wipe userdata when flashing other partitions.
fastboot -w flash system system.img will wipe data
fastboot flash system system.img will not wipe data.

gee one said:
Not true- the -w flag will wipe userdata when flashing other partitions.
fastboot -w flash system system.img will wipe data
fastboot flash system system.img will not wipe data.
Click to expand...
Click to collapse
Oh, I learned something new
Sent from my Nexus 5X using Tapatalk

jhester1967 said:
I received the download on my 5x that's rooted. Will this break root for me?
Click to expand...
Click to collapse
I doubt it will install. The install will simply fail.

Im not so good at this...
So I just copy the 3 img files to the same folder adb is installed and I run the 4 commands? Do I have to install TWRP again? Do I have to root again?
I did the command "adb reboot bootloader" which rebooted my phone in the bootloader home page, but when I did the next command "fastboot flash boot boot.img" I got the msg "<waiting for any devices>"

ch.ch1 said:
Im not so good at this...
So I just copy the 3 img files to the same folder adb is installed and I run the 4 commands? Do I have to install TWRP again? Do I have to root again?
I did the command "adb reboot bootloader" which rebooted my phone in the bootloader home page, but when I did the next command "fastboot flash boot boot.img" I got the msg "<waiting for any devices>"
Click to expand...
Click to collapse
Keep this guide by Heisenberg for reference, it is very helpful when updating firmware or returning to stock. You want to refer to section 10 to update via fastboot.
If going from MMB29P to MMB29Q OTA, flash in fastboot: boot, system, and vendor. Radio and bootloader are unchanged if you are using MMB29P. Recovery does not need to be flashed since you want to keep TWRP.
Yes, you will need to root again in TWRP.

Cant flash any of 3 factory images ? Solved system was using 19.99 gb's

" SOLVED - System was using 19.99 gb's required user data format. " Cant flash any of 3 factory images ? Anyone have a clue why ? I have a verizon pixel Xl with unlocked bootloader rooted with the newest supersu and every time I try to flash any of the three factory images for pixel XL my adb tools gives me the error " error: failed to load 'image-marlin-nde63l.zip': Not enough space " I flashed images just fine a couple weeks ago on both my Nexus 6 and my Nexus 9 but for some reason I keep getting this problem.
I have tried using flash-all.bat and that is what I get. I never have had any luck using flash-all.bat in the past with my Nexus 6 & 9 so I would use the manual method which I"am listing below but there are a lot more things to flash on these pixel XL. So hopefully someone can list how to manually flash an image on the pixel XL because its totally different. Hopefully someone can tell me what is the problem ?
Run fastboot commands
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Add next step for Nexus 9
fastboot flash vendor vendor.img

I have also tried the following steps and on the last step flashing the image I still get " error: failed to load 'image-marlin-nde63l.zip': Not enough space "
Steps I tried are:
fastboot flash bootloader bootloader-marlin-8996-012001-1608281716.img
fastboot reboot-bootloader
fastboot flash radio radio-marlin-8996-012511-1609150631.img
fastboot reboot-bootloader
fastboot -w update image-marlin-nde63l.zip

I just checked my setting and I have 19.99 gb's used by the system. That seems way too much. Could that be the problem ?

M9guy said:
I just checked my setting and I have 19.99 gb's used by the system. That seems way too much. Could that be the problem ?
Click to expand...
Click to collapse
Yeah sounds like it to me might have to wipe userdata that will wipe your phone completely

When I flash the images I use the flash-all.sh.
This works for me "sudo sh flash-all.sh"

I had same issue. I have sideloaded the update zip temporarily. I still wonder what's wrong in flashing zip file. I dont think its the issue with size because i had almost 90GB space left.

M9guy said:
I just checked my setting and I have 19.99 gb's used by the system. That seems way too much. Could that be the problem ?
Click to expand...
Click to collapse
When I flash the images I use the flash-all.sh.
This works for me "sudo sh flash-all.sh"

M9guy said:
I have a verizon pixel Xl with unlocked bootloader rooted with the newest supersu and every time I try to flash any of the three factory images for pixel XL my adb tools gives me the error " error: failed to load 'image-marlin-nde63l.zip': Not enough space "
Click to expand...
Click to collapse
You don't use ADB to flash factory image. You use fastboot, from your bootloader...

cam30era said:
You don't use ADB to flash factory image. You use fastboot, from your bootloader...
Click to expand...
Click to collapse
I was in bootloader fastboot mode and i saw same issue.

rootSr. said:
I was in bootloader fastboot mode and i saw same issue.
Click to expand...
Click to collapse
Just to confirm, you unzipped the factory image and did: fastboot flash system system.img?
If so, you might need to update your Android SDK...

cam30era said:
You don't use ADB to flash factory image. You use fastboot, from your bootloader...
Click to expand...
Click to collapse
I put phone in bootloader mode and held down shift button and righted clicked on my folder with my adb tool that I extracted all files to.

http://androiding.how/flash-firmware-factory-image-google-pixel/
jaythenut said:
Yeah sounds like it to me might have to wipe userdata that will wipe your phone completely
Click to expand...
Click to collapse
The method at the link below I had tried it previously and it did format my data but now each time I boot the phone I get " There"s an internal problem with your device. Contact your manufacturer for details. "
http://androiding.how/flash-firmware-factory-image-google-pixel/

zaksimmermon said:
When I flash the images I use the flash-all.sh.
This works for me "sudo sh flash-all.sh"
Click to expand...
Click to collapse
I have windows 10, which for windows your supposed to use flash-all.bat which that gave me the same error on the last step flashing the system image.

rootSr. said:
I had same issue. I have sideloaded the update zip temporarily. I still wonder what's wrong in flashing zip file. I dont think its the issue with size because i had almost 90GB space left.
Click to expand...
Click to collapse
I have the update downloaded to the phone it just wont install it think because I was rooted, even after formatting user data starting over it still would not install the update with no supersu installed.
Do you remember where the update was downloaded to on your phone what folder, or did you download the update somewhere else to your computer ?

cam30era said:
Just to confirm, you unzipped the factory image and did: fastboot flash system system.img?
If so, you might need to update your Android SDK...
Click to expand...
Click to collapse
It makes sense, I will update and verify. Thanks for quick reply Cam

rootSr. said:
It makes sense, I will update and verify. Thanks for quick reply Cam
Click to expand...
Click to collapse
I just tried updating my Minimal ADB and Fastboot [10-22-16] and still same error. I thought I had already updated but I tried again anyway and still no go, and that was updated on 10-22-16
http://forum.xda-developers.com/showthread.php?t=2317790

M9guy said:
I have windows 10, which for windows your supposed to use flash-all.bat which that gave me the same error on the last step flashing the system image.
Click to expand...
Click to collapse
What version is your pixel running now? I'm on NDE63P.

zaksimmermon said:
What version is your pixel running now? I'm on NDE63P.
Click to expand...
Click to collapse
I"am on NDE63L

You need to try updating the SDK through the SDK manager. It'll have a box to check of to update SDK 25.
Sent from my Pixel XL using Tapatalk

rootSr. said:
It makes sense, I will update and verify. Thanks for quick reply Cam
Click to expand...
Click to collapse
It did work without any issues. I have cleared old SDK and downloaded new. Worked flawless. Thanks. :good:

[Magisk] TWRP/Root-less Module Uninstall by allowing ADB in Recovery

I had trouble finding this information, and since we have no working TWRP yet, here is a way to get low-level access to al lot of files.
Full credits go to: @s3axel, Source
So you flashed a module that is now causing a bootloop?
Follow these steps:
0. check if you can boot using stock boot.img, if that does not work, then you have a bigger problem then I had and this guide may not work for you.
1. Get the stock recovery.img by extracting it from the same OTA file as your current build, using payload_dumper
2. Follow s3axel's guide to get adb to work in recovery mode (after you unlock the drive)
s3axel said:
It's actually pretty easy and this would most probably also work for the 7T...
Prerequisites:
Android Image Kitchen (credit to osm0sis for providing this tool)
the original recovery image file (henceforth called "recovery.img"). You can extract this yourself from an update zip file by unpacking "payload.bin" and then use a tool like payload_dumper (credit to vm03 for providing this) to extract the recovery.img file
Now do the following:
unpack image with Image Kitchen --> this will create a "ramdisk" and a "Split_img" directory with the unpacked content within
navigate into the "ramdisk" folder and use a text editor (on windows preferably Notepad++) to edit the file "prop.default"
look for entry "ro.adb.secure" and change entry value from "1" to "0". Note this entry can occur multiple times (I noticed twice), change each --> this will prevent adb from asking for authorization (the recovery does not provide such a dialogue)
look for entry "ro.debuggable" and change this from "0" to "1" --> this actually enables adb
look for entry "ro.secure" and change this from "1" to "0" --> may be unnecessary but I wanted to avoid brick in case a modified recovery would result in such a behaviour
save textfile
repack the image with Android Image Kitchen and voila:
you have a new modified recovery image you can flash
Click to expand...
Click to collapse
3. rename the image_new.img to unsecure_adb_recovery.img
4. flash usecure recovery
Code:
fastboot flash recovery unsecure_adb_recovery.img
5. get into the adb shell
Code:
adb shell
then find the magisk module folder
Code:
cd /data/adb/modules
6. remove the module
Code:
rm -rf name_of_module
7. exit shell
8. reboot back to fastboot (See notes below)
9. flash stock recovery
Code:
fastboot flash recovery recovery.img
10. boot patched boot image to try if magisk worked
Code:
fastboot boot patched_magisk.img
Hopefully, if it boots again with root and Magisk
This worked very well and was very easy to do.
11. Use Magisk apk to install magisk to boot img. Or flash your patched magisk.
Notes:
DO NOT try adb reboot fastboot, I was hoping this would work (I was tired, ok...)
I got stuck in a bootloop (it kept asking me to unlock my device)
to break out of this loop, I used the forced off method: hold power + volume up & down until screen blacks out
From power off to bootloader:
press & hold volume down and power
and hold down until you get back to recovery, reboot to fastboot then flash stock recovery back to secure your ADB and return to as much stock as possible :good:

Here is my patched prop.default

Question: if a patched recovery.img with adb is created for 9.0.4/9.0.5 could anyone use it?
Also, instead of fastboot flash recovery unsecure_recovery.img couldn't you just run fastboot boot recovery unsecure_recovery.img? I was able to boot and not flash the test TWRP build. That way you wouldn't have to reflash everything. It is this per device due to encryption?
Thanks for any info. Good find!

Y not create a core only boot image from magisk andThat share here so it would b really helful to all....

grandpajiver said:
Question: if a patched recovery.img with adb is created for 9.0.4/9.0.5 could anyone use it?
Also, instead of fastboot flash recovery unsecure_recovery.img couldn't you just run fastboot boot recovery unsecure_recovery.img? I was able to boot and not flash the test TWRP build. That way you wouldn't have to reflash everything. It is this per device due to encryption?
Thanks for any info. Good find!
Click to expand...
Click to collapse
The Recovery.img is from stock, so not a per-device thing.
I was just too lazy to find a place to upload large files.
I am currently on 10.0.4 but with 10.0.5 showing up, it would need updating later on.
I am not sure if you can flashboot boot recovery, certainly worth a try? Not sure how all this works, so I just flashed recovery and then flashed stock after I was done.
I also tested the TWRP build by not flashing it but booting it directly, but that was not very productive given it's current state.

hafiz.hasan said:
Y not create a core only boot image from magisk andThat share here so it would b really helful to all....
Click to expand...
Click to collapse
I was actually looking for this, but the how-to-build magisk guide has a lot more to do.
When I saw this guide I was like, oh I already have all the tools required Noice!

If only I didn't have tons of crap at work. This may be the gateway to v4a.
I have the images but not the extractor. Hmmmmm.

FreezyExp said:
I was actually looking for this, but the how-to-build magisk guide has a lot more to do.
When I saw this guide I was like, oh I already have all the tools required Noice!
Click to expand...
Click to collapse
Nice.. So are you gonna help building core only boot img for our device.?

hafiz.hasan said:
Nice.. So are you gonna help building core only boot img for our device.?
Click to expand...
Click to collapse
Nope sorry, not at this time.
There is a pull request on the magisk github that allows us to build Core-Only, so I will be waiting for that.
This guide contains the information that solved my immediate issue with not being in possesion of core-only.
Without having to deal with a lot of unknowns, just download some tools, extract some files, edit a few lines then patch it back up.

Bah. I've had no luck getting payload_dumper.py to work. failing on extracting logo, of all things.
Using windows 10 pro... python is installed, all requirements met... just cannot extract the .bin. Android Image Kitchen isn't for OTA bins either.. that wasn't helpful, unfortunately. Grr. I'm sure its either a stupid Windows thing or a stupid python thing... I installed 3.8 vs 3.6. Dunno. I prefer Perl
I'm not giving up though. I'll probably install Linux for Windows and run through that. Dunno.

grandpajiver said:
Bah. I've had no luck getting payload_dumper.py to work. failing on extracting logo, of all things.
Using windows 10 pro... python is installed, all requirements met... just cannot extract the .bin. Android Image Kitchen isn't for OTA bins either.. that wasn't helpful, unfortunately. Grr. I'm sure its either a stupid Windows thing or a stupid python thing... I installed 3.8 vs 3.6. Dunno. I prefer Perl
I'm not giving up though. I'll probably install Linux for Windows and run through that. Dunno.
Click to expand...
Click to collapse
Try with python 2.7
Sent from my OnePlus7TPro using XDA Labs

Lossyx said:
Try with python 2.7
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
This isn't fun to work on through a locked down Windows 10 pc. gonna try again on my chromebook after I get the 1.0.0.6 build.

here unsecure_adb_recovery 10.0.6 AB
to delete module
rm -rf /data/adb/modules/name of modules

every_one said:
here unsecure_adb_recovery 10.0.6 AB
to delete module
rm -rf /data/adb/modules/name of modules
Click to expand...
Click to collapse
You are awesome.
Found out 1.0.0.6 is Indian only. I guess I best make some coffee and try to work on US unlocked 1.0.0.5.

grandpajiver said:
You are awesome.
Found out 1.0.0.6 is Indian only. I guess I best make some coffee and try to work on US unlocked 1.0.0.5.
Click to expand...
Click to collapse
I got updated to 1.0.0.6.. I went from the '0' version to 'I'. Shrug.
fastboot boot recovery.img nor fastboot boot recovery recovery.img works... sigh.
I do have the full OTA. OnePlus7TOxygen_14.I.08_OTA_008_all_1911061912_10a180d3.zip. Dunno if anyone needs it.

I am on Linux. I used mktool to unpack and repack. I set all the flags properly between entered fastboot and Flash the new image to recovery as specified. device immediately hangs. I hold the keys to enter fastboot mode again and of course I can't run shell as ADB is not available in fastboot.

every_one said:
here unsecure_adb_recovery 10.0.6 AB
to delete module
rm -rf /data/adb/modules/name of modules
Click to expand...
Click to collapse
Hi, I'm stuck, I can't apply this tutorial to get a unsecure recovery. I'm on 10.0.6 international and when I try to boot to the file you provide, phone is stuck on "Fastboot Mode" screen. Is it from Indian variant? Could someone share the modified file from International 10.0.6 variant by any chance?
Or is it safe to flash this one? I don't want to try as I doesn't work with "fastboot boot unsecure_adb_recovery10.0.6.img".
I feel so dumb as I could flash back stock fastboot.img and my phone boots normally but then I don't have root access so can't delete the faulty module. If I boot a magisk patched boot.img then the phone doesn't boot, as the module is still there and activated....
Thanks

morback said:
Hi, I'm stuck, I can't apply this tutorial to get a unsecure recovery. I'm on 10.0.6 international and when I try to boot to the file you provide, phone is stuck on "Fastboot Mode" screen. Is it from Indian variant? Could someone share the modified file from International 10.0.6 variant by any chance?
Or is it safe to flash this one? I don't want to try as I doesn't work with "fastboot boot unsecure_adb_recovery10.0.6.img".
I feel so dumb as I could flash back stock fastboot.img and my phone boots normally but then I don't have root access so can't delete the faulty module. If I boot a magisk patched boot.img then the phone doesn't boot, as the module is still there and activated....
Thanks
Click to expand...
Click to collapse
You have to flash the recovery in order to boot into it.
If the recovery doesn't work you can just flash the stock one and you should be fine.
Sent from my OnePlus7TPro using XDA Labs

Lossyx said:
You have to flash the recovery in order to boot into it.
If the recovery doesn't work you can just flash the stock one and you should be fine.
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
Well, that worked! Thanks for your help
I've never really used adb until now so I was a bit lost as the shell window doesn't send any command confirmation when we enter the folder then delete the files, I felt a bit blind. But it worked.
Is there a place I can find the stock recovery from 10.0.6 international to avoid downloading the full rom? I should be able to extract the recovery.img from fastboot full ROM should I?

morback said:
Well, that worked! Thanks for your help
I've never really used adb until now so I was a bit lost as the shell window doesn't send any command confirmation when we enter the folder then delete the files, I felt a bit blind. But it worked.
Is there a place I can find the stock recovery from 10.0.6 international to avoid downloading the full rom? I should be able to extract the recovery.img from fastboot full ROM should I?
Click to expand...
Click to collapse
I have not fiddled around with fastboot ROMs. But you should be able to download your OOS rom with Oxygen Updater.
If someone else haven't uploaded the stock recovery, you'll need to use a tool like this to extract the payload bin inside the zip. The recovery is named recovery.img
https://github.com/cyxx/extract_android_ota_payload
Sent from my OnePlus7TPro using XDA Labs

Can I use the redmi note 8's rom on my 8T?

I have an 8T, it's the same of 8 only with the Nfc, can i use the ginkgo rom?

If you are referring to the MIUI EU ROM you could try, but it will probably fail and nobody has tried it yet.
The issue is we have no way (yet) to recover the device if will bootloop. We have the full ROM file, but it's a recovery zip: inside the zip I can't find a recovery we could flash in fastboot.
EDIT:
Download this recovery for RN8 https://www.androidfilehost.com/?fid=4349826312261617206
Extract the file and rename it to recovery.img
Reboot the device in fastboot and run
"fastboot boot [recovery.img]"
This will NOT flash the recovery but only boot it. If it loops, just reboot the device and will be back to normal.

olivercervera said:
If you are referring to the MIUI EU ROM you could try, but it will probably fail and nobody has tried it yet.
The issue is we have no way (yet) to recover the device if will bootloop. We have the full ROM file, but it's a recovery zip: inside the zip I can't find a recovery we could flash in fastboot.
EDIT:
Download this recovery for RN8 https://www.androidfilehost.com/?fid=4349826312261617206
Extract the file and rename it to recovery.img
Reboot the device in fastboot and run
"fastboot boot [recovery.img]"
This will NOT flash the recovery but only boot it. If it loops, just reboot the device and will be back to normal.
Click to expand...
Click to collapse
Ok thx, what about the custom aosp roms?

zikam12 said:
Ok thx, what about the custom aosp roms?
Click to expand...
Click to collapse
Well, try this step first. Without TWRP, you can't flash anything.

zikam12 said:
I have an 8T, it's the same of 8 only with the Nfc, can i use the ginkgo rom?
Click to expand...
Click to collapse
Yes it loading (but without Nfc and maybe wifi won't work)

soket1 said:
Yes it loading (but without Nfc and maybe wifi won't work)
Click to expand...
Click to collapse
you've tried?

zikam12 said:
you've tried?
Click to expand...
Click to collapse
Instructions

soket1 said:
Instructions
Click to expand...
Click to collapse
Can u translate it? Pls?

zikam12 said:
Can u translate it? Pls?
Click to expand...
Click to collapse
Instructions from Pilprod
Conditions: unlocked bootloader, access to Fastboot, computer with ADB and all drivers.
TWRP
Ginkgo v10.3.5.0.PCOMIXM firmwares for fastboot
1. Load the phone in Fastboot and connect to the PC.
2. Download the firmware and recovery from adb on the links above.
3. Unpack the recovery with adb in the folder (for sample: C:\\adb)
4. Unpack the firmware .
From the image folder, copy system.img, recovery.img and the boot.img, to folder with TWRP and adb.
5. Open the command line and write .
cd C:\adb
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
Click to expand...
Click to collapse
If everything is done correctly, the phone should start booting from the bootleg Redmi Note 8
6. After booting into the system, you can try and experiment with the firmware from RN8.
If you want to return to Redmi note 8T firmware and / or put TWRP and ROOT, then again load the phone in fastbut and continue.
fastboot flash recovery twrp.img
Click to expand...
Click to collapse
Loading into recovery.
After downloading TWRP, if you want to firmware Redmi note 8T, then do Wipe Data, System and all caches, without closing TWRP, copy to the phone this firmware, flash and boot into the system.

Hi all !!!
so did anyone manage to flash a ROM from the redmi note 8 on the 8T ?