Database Users

For Clarification Purposes Only-NaNdRoId

-------due to the brick phones-------(and im not talking nokia)
I have started this thread to get some clarification on Nandroid back ups. Now i know there is already a thread with step by step instructions in the sticky's. But with all these G1 ones getting bricked due to the new spl incompatibility with the old radio is it safe to use. I ask this only because one of the steps is to have a recovery.img and the only recovery image i can find is for jf1.43 and one other. But none for the adp 1.5 builds. I am worried that if i were to flash a old recovery image, and it down grades my radio i may get bricked. I'm not really sure if that's how it works (if not please correct) and thats why i want to recovery image from the new builds ( i am using Dudes Cupcake 1.1)
Do they exist and if they do and i just haven't search hard enough please tell me. Or is the recovery image what i create when i do the back up. I ask all these perceivable noob questions because i really like my G1 and would hate to brick it.....
Please post some useful Replies... I think this thread could be potentially useful

Doing a nandroid backup creates a boot.img, data.img, and system.img of your phone. Flashing those three, restores your phone exactly as it was when you created the backup. As long as you do a backup of your system when it's stable, then it doesn't matter what you do to your phone. As long as you can get into fastboot, then it can be fixed in less than 5 minutes.
Dunno if that was the answer you were lookin for, but that's how I understand it. And it works....I did a nand backup of my Dude build just yesterday, and flashed over to haykuro's 6.0 to check it out...test drive it. I didn't like it, so I flashed the nandroid backup, and was back up and running in minutes.
You mentioned recovery.img....I don't know what that is or what you do with it.
Assuming you have fastboot setup, just do the steps in this post and you're golden-
http://forum.xda-developers.com/showpost.php?p=3311708&postcount=2

the recovery.img is what the phone boots in recovery mode... the recovery.img that your referring to allows you to create NAnd backups easily with NANDroid... the recovery img is totally independent from your SPL (bootloader), Radio, and Firmware

ESKIMOn00b said:
the recovery.img is what the phone boots in recovery mode... the recovery.img that your referring to allows you to create NAnd backups easily with NANDroid... the recovery img is totally independent from your SPL (bootloader), Radio, and Firmware
Click to expand...
Click to collapse
Right on, thanks for that. Knowledge is power.
So the op says that he found the JF1.43 recover.img....That's the one we all have and the one he needs, right?

yep, they're all the same
All the recent ROMs EXCEPT for the official HTC ADP use the same recovery.img found in the previous JF ROMs (1.42, etc.). You can safely reflash the recovery image from fastboot without touching the radio, the SPL or even data, boot or system if you want and it won't hurt anything.

remember when you orig rooted your phone and the recovery mode didnt have the fractal background and you had to press alt+l to show the text? thats the OLD recovery img, the fractal bkgrnd (v1.43) one is the new one, and so far the latest "cooked" recovery.img

Like i said im kinda noobish. So after i downloaded the drivers, and the sdk for 1.5 i still need to download fastboot (to my pc) as well.

Great post. +1

pshadey said:
Like i said im kinda noobish. So after i downloaded the drivers, and the sdk for 1.5 i still need to download fastboot (to my pc) as well.
Click to expand...
Click to collapse
correct...
the fastboot.exe is how your PC will interface with the FASTBOOT mode in the SPL
if you didnt have it DL'ed when you tried to fastboot, your computer would kickback that fastboot isnt a valid command or the like (depending on os)

so im reading all these tutorials, and im getting confused a little... to use fast boot through adb does my phone need to be at the boot loader (skateDroids) or are there commands that i would need to enter in order to get there....
I appriciate every answer i am trying to learn as much as i can. This has really spark a interest in my life and i really enjoy it.

fastboot is not part of adb, and yes your phone needs to be in bootloader to FASTBOOT, after entering bootloader plug in the usb cable and press the back button, your phone should read FASTBOOT rather than serial0
adb works almost anywhere (after splash1/g1 logo) except bootloader...
for reference ADB stands for Android Debug Bridge

I am still slightly confused how do i create a nandroid back up, i am using dudes cupcake 1.1. Is it the same as JF's alt-b

pshadey said:
I am still slightly confused how do i create a nandroid back up, i am using dudes cupcake 1.1. Is it the same as JF's alt-b
Click to expand...
Click to collapse
Yep. Boot your phone with home+power, then Alt+B. It'll create a folder on your sdcard called nandroid. All the .img files will be in there.

i dont think i have the right recovery image though do i just download the zip file. and do the whole rename to update.zip and install alt-s.
I only ask because i opened the file and found a recovery.img which made me ponder.

thats the Nand dump of your recovery partition... you figured it out...
if you made the backup you have the right recovery img.... the old one doesnt have it...

~edit~
I see I misunderstood the question. Duh

ESKIMOn00b said:
thats the Nand dump of your recovery partition... you figured it out...
if you made the backup you have the right recovery img.... the old one doesnt have it...
Click to expand...
Click to collapse
and when i booted in recovery mode i dont have the option alt-b. so i must have the old recovery image.
so now i need to (already have) download the recovery image zip file from jfs blog, rename it update.zip and flash it....right????

This is what your recovery mode will look like after you update it-
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can't answer your question about how to update to it though. Mine's been this way since waaay back when I flashed JF's RC33.

yea, thanks bro. mine definitely does not look like that. but now i need to know for sure how to update it.

pshadey said:
and when i booted in recovery mode i dont have the option alt-b. so i must have the old recovery image.
so now i need to (already have) download the recovery image zip file from jfs blog, rename it update.zip and flash it....right????
Click to expand...
Click to collapse
I am having the same problem... I am on the Dude's Cupcake 1.1a but I dont see ant Alt-B option...
Android system recovery utility
E:Can't open /cache/recovery/command
Home+Back - reboot system now
Alt+L - toggle log text display
Alt+S - apply sdcard:update.zip
Alt+W - wipe data/factory reset
Click to expand...
Click to collapse
Thats all i have on my screen.

No OS installed mate 9

Hello everybody, i was handed a mate 9 handset from a friend in as is condition.
I don't know what have it been through.
The phone's back shows it is MHA-l29
Trying with buttons:-either i can enter erecovery connect to wifi. and the recovery will fail.
I can enter an interface called TRWP.
There is no OS installed on the handset apparently.
I don't know where to start, please help me. I'm willing to grasp concepts quickly, and a step by step guide will be appreciated ! thx.
Edit: i did download an "update.zip" and copied it through computed, tried to install it but got a command error...

scrutnizing said:
Hello everybody, i was handed a mate 9 handset from a friend in as is condition.
I don't know what have it been through.
The phone's back shows it is MHA-l29
Trying with buttons:-either i can enter erecovery connect to wifi. and the recovery will fail.
I can enter an interface called TRWP.
There is no OS installed on the handset apparently.
I don't know where to start, please help me. I'm willing to grasp concepts quickly, and a step by step guide will be appreciated ! thx.
Edit: i did download an "update.zip" and copied it through computed, tried to install it but got a command error...
Click to expand...
Click to collapse
Do you have adb/fastboot drivers installed? If not: https://forum.xda-developers.com/showthread.php?t=2317790
When you have that installed, boot into TWRP then tap on the Reboot button and then on the Bootloader button.
Plug in USB and open a command prompt, type the following command:
fastboot oem get-build-number
Post the result here

i solved this issue just today, i didn't get lucky with stock rom kept boot looping. What i did is get fromfuture mate 9 custom rom, place the zip in twrp folder and install zip from there.
The update.zip wouldn't install this way. At least my phone is working now.
Thanks
Edit: I also tried to flash update.app image components after extraction, using fastboot. It didn't work, I don't recommend this method.
The custom rom is life saving.

scrutnizing said:
i solved this issue just today, i didn't get lucky with stock rom kept boot looping. What i did is get fromfuture mate 9 custom rom, place the zip in twrp folder and install zip from there.
The update.zip wouldn't install this way. At least my phone is working now.
Thanks
Edit: I also tried to flash update.app image components after extraction, using fastboot. It didn't work, I don't recommend this method.
The custom rom is life saving.
Click to expand...
Click to collapse
Ah, then you're on Nougat.
The reason I asked about fastboot was to find out what build/fw you were on, then go from there to install stock firmware.
You could update to Oreo using: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108

hey thanks!
The reason why im statisfied with this is that when flashing stock rom, it worked the first time (no bootloop), but the camera was not working, neither developper mode. Thats why i wiped, reflashed and got stuck in bootloop, no idea why. Also i could only flash a few of the images in update.app, very few. So it was not ideal, other images would yield an error in fastboot when flashing (command failed), i read online and figured this is perhaps due to a bad unlocking in the bootloader (if i understood correctly) at this point i felt that i could no longer process and learn info in android world, after all it was only one day that i'm into android and i felt tired, so i took the ladt chancd and decided to try the custom rom, im now satisfied with results, but many question marks are still in my head.

scrutnizing said:
hey thanks!
The reason why im statisfied with this is that when flashing stock rom, it worked the first time (no bootloop), but the camera was not working, neither developper mode. Thats why i wiped, reflashed and got stuck in bootloop, no idea why. Also i could only flash a few of the images in update.app, very few. So it was not ideal, other images would yield an error in fastboot when flashing (command failed), i read online and figured this is perhaps due to a bad unlocking in the bootloader (if i understood correctly) at this point i felt that i could no longer process and learn info in android world, after all it was only one day that i'm into android and i felt tired, so i took the ladt chancd and decided to try the custom rom, im now satisfied with results, but many question marks are still in my head.
Click to expand...
Click to collapse
It's because you can't flash everything from fastboot with just phone unlocked.
You can flash: System, vendor, boot (ramdisk and kernel for oreo), recovery (recovery_ramdisk, recovery_vendor, recovery_vbmeta for oreo), cache, userdata. (I think those are it)
Flashing anything else requires you to unlock bootloader, but it needs a special code which none of us normal people have. :/

ante0 said:
It's because you can't flash everything from fastboot with just phone unlocked.
You can flash: System, vendor, boot (ramdisk and kernel for oreo), recovery (recovery_ramdisk, recovery_vendor, recovery_vbmeta for oreo), cache, userdata. (I think those are it)
Flashing anything else requires you to unlock bootloader, but it needs a special code which none of us normal people have. :/
Click to expand...
Click to collapse
@ante0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can you give a hand, please ?
I unlocked the bootloader and flashed the recovery, the system booted successfully.
I tried to flash a ROM after that, it showed errors and didn't complete the flashing. since that time the phone has bootloop.
Unlocked bootloader and FRP
fastboot oem get-build-number : MHA-L29 8.0.0.374(C185)
I can access the TWRP recovery and erecovery and bootloader&fastboot
what I have already tried :
1-Fastboot flash ramdisk and kernel .
2-Tried to flash the stock firmware via TWRP.
3-Tried HurUpdater0.3
4- Extract update.app & HOWTA
5-Flash ramdisk and kernel from inside TWRP

is possible unbrik Mate9 Oreo , using only fastboot method ?
can help umbrik only commands fastboot?

Stucked on bootloop and can't be turned off

so, my OP 6t is stuck at bootloop and I cvan not turn it off...
any sugestion and help?
Thanks

maraschino said:
so, my OP 6t is stuck at bootloop and I cvan not turn it off...
any sugestion and help?
Thanks
Click to expand...
Click to collapse
anyway, for others
finally I did manage to turn off the device by pressing volume up + power off button.
after that started phone regulary again and booted normally...
I don't know why this hapend, but made me nervous as hell

got the same problem, find the same solution to boot, however still blocked in a bootloop any advice someone ?

Soujyu51 said:
got the same problem, find the same solution to boot, however still blocked in a bootloop any advice someone ?
Click to expand...
Click to collapse
Some more information would help, bootloader locked or unlocked, in the process of root, flashing stock firmware or whatever you were doing when it bootlooped.

ggrant3876 said:
Some more information would help, bootloader locked or unlocked, in the process of root, flashing stock firmware or whatever you were doing when it bootlooped.
Click to expand...
Click to collapse
sorry, my bad
bootloader unlocked, OP6T root , magisk installed
bootloop appeared in the process of uninstalling 2 modules

Word is that it's a bug in Magisk, I believe I had it on version 17.1 and 17.3 both.

YrrchSebor said:
Word is that it's a bug in Magisk, I believe I had it on version 17.1 and 17.3 both.
Click to expand...
Click to collapse
full wipe is the key or any solution ? XD
possibility to uninstall magisk via the stock recovery ?

Soujyu51 said:
full wipe is the key or any solution ? XD
possibility to uninstall magisk via the stock recovery ?
Click to expand...
Click to collapse
You installed Magisk by fastboot flashing the modified boot.img? Couldn't you just flash the stock boot.img?
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini

Soujyu51 said:
sorry, my bad
bootloader unlocked, OP6T root , magisk installed
bootloop appeared in the process of uninstalling 2 modules
Click to expand...
Click to collapse
There's literally another thread in this forum about another member who is stuck in bootloop after uninstalling a magisk module.
I suggested that he fastboot flash the stock boot.img

That's probably me. But that did not help.

Soujyu51 said:
full wipe is the key or any solution ? XD
possibility to uninstall magisk via the stock recovery ?
Click to expand...
Click to collapse
You should be able to use the button combo to power down and then get it to boot up normally, then just uninstall magisk through the app if you want to prevent it from happening again. Or just run it and deal with it, knowing that it doesn't seem to happen on every reboot or anything

YrrchSebor said:
You should be able to use the button combo to power down and then get it to boot up normally, then just uninstall magisk through the app if you want to prevent it from happening again. Or just run it and deal with it, knowing that it doesn't seem to happen on every reboot or anything
Click to expand...
Click to collapse
seems to be a 100% boot in bootloop Ahah (22/22 run)
well I tried a couple of thing
in the fastboot mode, I flashed the stock boot img ( no success)
in recovery mode I tried to flash the uninstaller no success (error 1)

Full disclosure, I don't have this phone (yet), but isn't it an A/B slot phone?
Are you sure you are flashing stuff to the right slot? Are you sure you are booting from the right slot?
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini

ktmom said:
Full disclosure, I don't have this phone (yet), but isn't it an A/B slot phone?
Are you sure you are flashing stuff to the right slot? Are you sure you are booting from the right slot?
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Click to expand...
Click to collapse
How would we know if we are? Or which slot is booting? I'm coming from a non a b phone so it's all new to me

So I'm guessing this is the core of your problem. You need to read as much as possible about how A/B slot phones work.
In a nutshell, there are two complete sets partitions (things like system, boot, vendor...). One is the A set, the other B. This is done to ensure that a device continues to operate even if there is a failed OTA, and help speed up the upgrade process by doing it to the non-booted slot.
What can be very confusing is that after flashing something, the bootloader may choose to switch to the other slot.
You can find out what the active slot is in adb:
Code:
adb shell getprop ro.boot.slot_suffix
and in fastboot:
Code:
fastboot getvar current-slot
Switching to the other slot is done in fastboot:
Code:
fastboot set_active other
-or-
Code:
fastboot set_active [a,b]
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini

ktmom said:
So I'm guessing this is the core of your problem. You need to read as much as possible about how A/B slot phones work.
In a nutshell, there are two complete sets partitions (things like system, boot, vendor...). One is the A set, the other B. This is done to ensure that a device continues to operate even if there is a failed OTA, and help speed up the upgrade process by doing it to the non-booted slot.
What can be very confusing is that after flashing something, the bootloader may choose to switch to the other slot.
You can find out what the active slot is in adb:
Code:
adb shell getprop ro.boot.slot_suffix
and in fastboot:
Code:
fastboot getvar current-slot
Switching to the other slot is done in fastboot:
Code:
fastboot set_active other
-or-
Code:
fastboot set_active [a,b]
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Click to expand...
Click to collapse
Hi,
I am stuck with the phone ONLY booting into slot A bootloader.
I can't get into recovery mode at all, not with the commands, nor with buttons- always goes into the bootloader.
This happend after installing TWRP and Magisk.
The commands:
"fastboot getvar current-slot" tells me that I am on slot "A"
"fastboot set_active other" and "fastboot set_active " do not work, no error but the long help list of commands comes up.
Am I using the wrong ADB-Version where these commands are not included, because I can't find them in the "help" list?
Can anyone please help, I am stuck.
Thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

stuck at boot loader is unlocked screen
i have issue for oneplus pro 7 also, keep stuck at boot loader is unlocked screen, was pressed volume + and power to restart, come back to the same screen again and stuck.... unable to access other menu and boot the screen... anyone have any ideal what else can i do? please, i really need it urgently... million thanks

have you guys tried pressing and holding vol+, vol-, and power until it turns off or goes to Bootloader screen.? i had a hard time with that on my 6t.

acele7 said:
i have issue for oneplus pro 7 also, keep stuck at boot loader is unlocked screen, was pressed volume + and power to restart, come back to the same screen again and stuck.... unable to access other menu and boot the screen... anyone have any ideal what else can i do? please, i really need it urgently... million thanks
Click to expand...
Click to collapse
First have you asked over in the 7pro side of the house as this is the 6t side... And a bit more info would help.. like what did you do prior to it getting stuck... Are you on a custom rom or stock.. ect...

acele7 said:
i have issue for oneplus pro 7 also, keep stuck at boot loader is unlocked screen, was pressed volume + and power to restart, come back to the same screen again and stuck.... unable to access other menu and boot the screen... anyone have any ideal what else can i do? please, i really need it urgently... million thanks
Click to expand...
Click to collapse
I use a OnePlus6t and know absolutely nothing about the 7 pro but if you guys have msm tool that's where I'd be headed to if I were in your same situation. Any unbricking tools and or guides is where I would read everything.
If i was in exact same situation on my 6t I would try holding my +&- volume keys down and my power button until I see fastboot on screen them release and go from there but I would run the msm tool we have for my device model. If for some reason I couldn't get that going which I don't believe that sort of thing happens much but if it did I'd go over to the collection of unbricking tools thread and memorize the entire thread and see if something there may work. Possibly fastboot flash a fastboot rom..
Maybe If you have another device upload a pic of what screen you're stuck on to help us better understand..

Magisk for Android 12/OOS12 global ( magisk_patched)

Magisk for Android 12/OOS12 global ( magisk_patched)
IN2015_11.C.11 (Global)
boot
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com

suhuf said:
Magisk for Android 12/OOS12 global ( magisk_patched)
IN2015_11.C.11 (Global)
boot
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Click to expand...
Click to collapse
How exactly do we
suhuf said:
Magisk for Android 12/OOS12 global ( magisk_patched)
IN2015_11.C.11 (Global)
boot
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Click to expand...
Click to collapse
Just flash this via fastboot?

scorpio76r said:
How exactly do we
Just flash this via fastboot?
Click to expand...
Click to collapse
fastboot flash boot boot.img

suhuf said:
fastboot flash boot boot.img
Click to expand...
Click to collapse
Just did this and now I'm stuck fastboot. I even tried fastboot reboot and still stuck in fastboot on the device. I'm using Windows PowerShell btw

scorpio76r said:
Just did this and now I'm stuck fastboot. I even tried fastboot reboot and still stuck in fastboot on the device. I'm using Windows PowerShell btw
Click to expand...
Click to collapse
If you're sure the version is global, it should work.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

scorpio76r said:
Just did this and now I'm stuck fastboot. I even tried fastboot reboot and still stuck in fastboot on the device. I'm using Windows PowerShell btw
Click to expand...
Click to collapse
Read the explanation and remove the original boot file and fastboot, the phone will boot.
Put the same boot file in the download section of the phone and patch it with magisk, then upload the patched file to the phone with fastboot process.
[TOOL] A QUICK Android OTA payload dumper
Made with Go. By utilizing goroutines, this can extract img files from (full) OTA payload.bin really quickly. See how fast this is: https://i.imgur.com/adpijqf Source Code: https://github.com/ssut/payload-dumper-go Prebuilt binaries...
forum.xda-developers.com

Apologies but I'm confused by the steps in the posts above... Can someone post a brief step-by-step guide for this? Thanks!
[EDIT] nevermind, extracted and patched on my own, thanks!

scorpio76r said:
Just did this and now I'm stuck fastboot. I even tried fastboot reboot and still stuck in fastboot on the device. I'm using Windows PowerShell btw
Click to expand...
Click to collapse
I also got stuck on fastboot. Any solution will be appreciated.
Edit: Had to restore device with MSM Download Tool.

Hi, just updated to official OOS12 and hate it, it appears it also re locked my bootloader which was unlocked, how do I unlock it again? do I follow the same steps? I want to go back to OOS11 and start flashing custom roms
edit: just checked on fastboot mode. it says unlocked in red letters. would still like to flash magisk!

cjvzla said:
Hi, just updated to official OOS12 and hate it, it appears it also re locked my bootloader which was unlocked, how do I unlock it again? do I follow the same steps? I want to go back to OOS11 and start flashing custom roms
Click to expand...
Click to collapse
You sound like me a week ago. Best bet is to msm your phone and start from scratch. Bring your phone up to 11.10.10 then go with the Jaguar rom. It has March security patch, call record and developers literally responds within a few minutes of a post or question.

scorpio76r said:
You sound like me a week ago. Best bet is to msm your phone and start from scratch. Bring your phone up to 11.10.10 then go with the Jaguar rom. It has March security patch, call record and developers literally responds within a few minutes of a post or question.
Click to expand...
Click to collapse
hi, just checked and I still have the bootloader unlocked, which means I could flash a recovery right? I haven't flashed stuff in android phones in a while and I'm a bit rusty, where should I go first?

cjvzla said:
hi, just checked and I still have the bootloader unlocked, which means I could flash a recovery right? I haven't flashed stuff in android phones in a while and I'm a bit rusty, where should I go first?
Click to expand...
Click to collapse
Yes use fastboot twrp image from the official twrp thread. Then install twrp installer.

krakout said:
Apologies but I'm confused by the steps in the posts above... Can someone post a brief step-by-step guide for this? Thanks!
[EDIT] nevermind, extracted and patched on my own, thanks!
Click to expand...
Click to collapse
hi! how did you extracted and patched? did you follow the video? cause I can't understand what hes saying. can you leave me a step-by-step? thanks. I'm on OOS12, bootloader unlocked

cjvzla said:
hi! how did you extracted and patched? did you follow the video? cause I can't understand what hes saying. can you leave me a step-by-step? thanks. I'm on OOS12, bootloader unlocked
Click to expand...
Click to collapse
I just sent you a personal message with a link that will help you out.

Sorry, couldn't reply earlier.
Higher in this thread there's a link for a very useful program. Use that program to rip everything from the official download update package (have you downloaded that?). Then move boot.img to your phone, and let Magisk Manager patch it. Then copy the patched file over to your PC and use adb to flash it.

krakout said:
Sorry, couldn't reply earlier.
Higher in this thread there's a link for a very useful program. Use that program to rip everything from the official download update package (have you downloaded that?). Then move boot.img to your phone, and let Magisk Manager patch it. Then copy the patched file over to your PC and use adb to flash it.
Click to expand...
Click to collapse
Yes, using windows 10 pc.

krakout said:
Sorry, couldn't reply earlier.
Higher in this thread there's a link for a very useful program. Use that program to rip everything from the official download update package (have you downloaded that?). Then move boot.img to your phone, and let Magisk Manager patch it. Then copy the patched file over to your PC and use adb to flash it.
Click to expand...
Click to collapse
hi thanks for the tutorial, managed to extract the OOS12 stock boot img and patched it with magisk 24, but when I connect in fastboot mode and check with the fastboot devices command I get nothing, and nothing on device manager either. even tho my bootloader is unlocked and fastboot drivers are installed, the pc doesnt seem to "see" my phone?
the adb devices command does show my phone when connected and turned on.

That's a bit tricky and I'm not sure why it would do that, never encountered it... Tried restarting adb?

krakout said:
That's a bit tricky and I'm not sure why it would do that, never encountered it... Tried restarting adb?
Click to expand...
Click to collapse
looked for the latest drivers and installed those, now my devices does show up with the fastboot devices command! do I test the patched boot img first? and did you flash it normally or did you use fastboot flash boot_a and fastboot flash boot_b for the a/b partitions?

Question Help! Stuck in fastboot mode can't do anything

So i try to use the DSU Loader found in Developer Options to flash a GSI, but i forget to unlock the OEM and turn on the usb debug.
After installing a DSU and rebooting, the phone will attempt to boot the GSI but it shows "Your device is corrupt" and will no longer boot.
That said, the phone boot to fastboot mode automatically. But all the options under fastboot is not working, i can't get into the recovery mode and my laptop can't identify my phone when i connect to it.
Is there anyone know how i can fix it?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I had the same problem and flashed the boot.img on it and it was fixed.
If that doesn't work you can follow this guide to restore the system (needs to be in fastbootd mode): https://www.droidwin.com/unbrick-nothing-phone-1-flash-stock-firmware-via-fastboot-commands/

misecia said:
I had the same problem and flashed the boot.img on it and it was fixed.
If that doesn't work you can follow this guide to restore the system (needs to be in fastbootd mode): https://www.droidwin.com/unbrick-nothing-phone-1-flash-stock-firmware-via-fastboot-commands/
Click to expand...
Click to collapse
Thanks mate
But you can do it even you haven't enable OEM unlock and USB debug before the phone get bricked?

-

i have the same problem.. only fastboot commands work, anything i do just reboots the phone back to same menu . cant enter fastbootd. i can flash all partitions apart from product..system and some other. these i get error on. i got the bootloader unlocked but thats about it. i also did DU in dev mode then corrupt device.. anyone got a fix for this??

xera3k said:
i have the same problem.. only fastboot commands work, anything i do just reboots the phone back to same menu . cant enter fastbootd. i can flash all partitions apart from product..system and some other. these i get error on. i got the bootloader unlocked but thats about it. i also did DU in dev mode then corrupt device.. anyone got a fix for this??
Click to expand...
Click to collapse
Do you have the latest android platform tools? Try different cables, different ports?

Yes this is a problem on the phone. . Vi tried Windows and Linux , i can send commmands but only Flash some partitions and dont have or cant access bootloader or fastbootd.. so im stuck :/

xera3k said:
Yes this is a problem on the phone. . Vi tried Windows and Linux , i can send commmands but only Flash some partitions and dont have or cant access bootloader or fastbootd.. so im stuck :/
Click to expand...
Click to collapse
Idk if its because of that but you have typo in that command, should be bootloader instead boodloader

What if have you tried to boot into another slot fastboot --active-slot

layz1319 said:
What if have you tried to boot into another slot fastboot --active-slot
Click to expand...
Click to collapse
What command would i use ?

xera3k said:
What command would i use ?
Click to expand...
Click to collapse
So you may want to use fastboot getvar current-slot to get what slot you are currently using. Then use fastboot --active-slot=(the opposite slot you are using) eg.fastboot --active-slot=a / fastboot --active-slot=b. Lastly, fastboot reboot
Ps. Sometimes fastboot --active-slot=a/b may not work so you can try with fastboot --active-slot= other to boot into non current slot. Anyway wish you all the best

layz1319 said:
So you may want to use fastboot getvar current-slot to get what slot you are currently using. Then use fastboot --active-slot=(the opposite slot you are using) eg.fastboot --active-slot=a / fastboot --active-slot=b. Lastly, fastboot reboot
Ps. Sometimes fastboot --active-slot=a/b may not work so you can try with fastboot --active-slot= other to boot into non current slot. Anyway wish you all the best
Click to expand...
Click to collapse
I also am having this issue and tried what you suggested and got this.
Any ideas on how to fix?

Eventually I was able to change the active slot but sadly still looping.

yquitumadbro said:
View attachment 5677361
Eventually I was able to change the active slot but sadly still looping.
Click to expand...
Click to collapse
Try to change it again. I solved with that.

Good evening, I have the same problem after using the DSU Loader, the mobile is stuck like the screenshot in the first post above. I've tried everything but can't unlock anything. Can someone help me ?

If your PC isn't detecting your device while in Fastboot mode, you don't have the correct drivers installed. This may help.
Never try to install non-factory software on a locked bootloader!
Since you didn't enable OEM unlocking, it's unlikely that you'll be able to recover your device. Still, focus on the driver issue for now and we can go from there. Do you have ADB Platform Tools installed?

I installed GSI directly from the smartphone, I don't think I used unofficial software. The pc recognizes the mobile phone in fastboot and I also tried with ADB platform tool, but every time I get the message of device blocked

Dominicus.1 said:
I installed GSI directly from the smartphone, I don't think I used unofficial software. The pc recognizes the mobile phone in fastboot and I also tried with ADB platform tool, but every time I get the message of device blocked
View attachment 5681643
Click to expand...
Click to collapse
ADB commands do not work in fastboot.
fastboot devices should show the device when connected in fastboot mode.
Try fastboot flashing unlock to unlock the bootloader, which will make recovering your device much easier.

I tried everything, Windows never found my device inn fastboot but i plugged om a Linux then voila. Everything works

xera3k said:
I tried everything, Windows never found my device inn fastboot but i plugged om a Linux then voila. Everything works
Click to expand...
Click to collapse
U can't do anything if u r OEM tab is off and you soft bricked and not booting to system.
If unr able to boot in recovery using fastboot menu there do format data it will boot to system