Database Info

Stuck in TWRP

Hey there,
I´ve received my used Oppo today and couldn´t do stuff with it so I decided to flash it with CM13 and after some more things I did, I couldn´t restore my backups properly anymore (why I find odd and this has never happened to me before). Then I decided to switch back to ColorOS 2 following the instructions on oppoforums.com. Somehow I think that when I finished step 4: To make a clean install please select "Wipe data and cache", press "Yes" when it's done. my entire internal storage was wiped :-/ instead of wiiping data and cache it turned off and on and so on....it didn´t boot into ColorOS so I went with booting into TWRP again. There I found that I can only see some folders of Interal Storage
{
"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"
}
(open in new tab). I managed to adb-move the file "cm-13.0-20160311-NIGHTLY-r7plus.zip" into /sdcard and tried to install it from there which it apparently does successfully
.
When I click reboot -> system it still boots into TWRP everytime :crying:
How can I boot into an OS again? My computer recognizes my phone and I have adb access.

hmm... try use msm download tool

I have the same issue couple of days before... do this
Download Stock Recovery.
Boot in to fastboot
and flash stock recovery using this command fastboot flash recovery stock.img
After flash use command fastboot reboot
if you see wiping data and gone black screen then follow this....
Use this command. fastboot boot stockrecovery.img
now you can boot to stock recovery and you will see fully loaded wiping bar and it shoul reboot the phone. Now its done.
Power of the phone by press and hold. And boot to recovery asusal u do...flash the rom.
for qurey whatsapp me +919790397283

sriszone said:
I have the same issue couple of days before... do this
Download Stock Recovery.
Boot in to fastboot
and flash stock recovery using this command fastboot flash recovery stock.img
After flash use command fastboot reboot
if you see wiping data and gone black screen then follow this....
Use this command. fastboot boot stockrecovery.img
now you can boot to stock recovery and you will see fully loaded wiping bar and it shoul reboot the phone. Now its done.
Power of the phone by press and hold. And boot to recovery asusal u do...flash the rom.
for qurey whatsapp me +919790397283
Click to expand...
Click to collapse
Thanks, this actuually did it for me! I tried adb sideload, but that didn´t work.

https://goo.gl/photos/vSRMhRjyxr4MW8CA7

No ... Dont side load.
Just boot to twrp. Not flash.
Go to Fastboot. and boot . use this command. fastboot boot twrp.img
then you can mount internal storage.

oneplus 6 stuck in fastboot mode help plz

hello my oneplus 6 has been blocked on fastboot mode.:crying:
the problem is that I format the phone system with the twrp by mistake. now the phone is empty neither system nor twrp. I tried several methods like msmdownloadtool but the phone does not connect.
i tried to install the twrp with the command prompt when i put the command adb devices the list of phones attached remains empty.
please help me
{
"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"
}

Try too flash stockrom via fastboot, following this thread https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Please read the instruction carefully.

elbachiri said:
hello my oneplus 6 has been blocked on fastboot mode.:crying:
the problem is that I format the phone system with the twrp by mistake. now the phone is empty neither system nor twrp. I tried several methods like msmdownloadtool but the phone does not connect.
i tried to install the twrp with the command prompt when i put the command adb devices the list of phones attached remains empty.
please help me
Click to expand...
Click to collapse
in fast boot mode, only fastboot commands work like "fastboot boot twrp.img" will boot you into twrp

MrSteelX said:
in fast boot mode, only fastboot commands work like "fastboot boot twrp.img" will boot you into twrp
Click to expand...
Click to collapse
When i try the commands fastboot boot twrp.img
The commands gives me failed:error

elbachiri said:
hello my oneplus 6 has been blocked on fastboot mode.:crying:
the problem is that I format the phone system with the twrp by mistake. now the phone is empty neither system nor twrp. I tried several methods like msmdownloadtool but the phone does not connect.
i tried to install the twrp with the command prompt when i put the command adb devices the list of phones attached remains empty.
please help me
Click to expand...
Click to collapse
how Is your phone recognized?

°Washy said:
how Is your phone recognized?
Click to expand...
Click to collapse
Recognized like android phone
despite the drivers are installed

ndp_singe said:
Try too flash stockrom via fastboot, following this thread https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Please read the instruction carefully.
Click to expand...
Click to collapse
https://ibb.co/ctgDjft

extract the images.zip (on the same directory - not a sub directory i.e images\ ).
extract Others_flashall.zip.
Your directory will look like this:
then run flash-all-partitions.bat.
Warning: that will wipe all your data

thanks i put the .bat files in the official rom 9.0.2 Oxyegen.rar
after I install the rom with the program tool all in one.
now all its running well thanks for your help

Fastboot commands error

Hi everybody, I'm trying to install a custom recovery on my Asus Zenfone Max Pro M1, following the instructions to install the Pixel Experience ROM, but every time I give a command in fastboot mode the screen goes black and on the top left angle appears the message: press any key to shutdown. I've already unlocked the bootloader with the official unlock app, and I tried to do this thing on the stable Pie version and the on the Android Q beta, same thing appened. I'm not an expert but is a strage error, I've not found any help on the internet. Any suggestion? Thanks.

With regards to this thread's title here my 2 cents:
Fastboot commands per se aren't erroneous, at least I've neither encountered it ever, nor heard of this or read this.
The reality is that FastBoot isn't always Fastboot as expected, it depends on how OEM/carrier implemented Fastboot, will say not all Fastboot commands work on all devices.
Always run
Code:
fastboot --help
to get supported commands / their synthax listed.

jwoegerbauer said:
With regards to this thread's title here my 2 cents:
Fastboot commands per se aren't erroneous, at least I've neither encountered it ever, nor heard of this or read this.
The reality is that FastBoot isn't always Fastboot as expected, it depends on how OEM/carrier implemented Fastboot, will say not all Fastboot commands work on all devices.
Always run
Code:
fastboot --help
to get supported commands / their synthax listed.
Click to expand...
Click to collapse
Ok, I tried again and I had the same problem, but this time I gave the command "adb reboot bootloader" to go in fastboot mode and as soon the device booted in fastboot the same message appeared, "press any key to shutdown". i mean, it is a lot frustrating, because I'm working to install the ROM since october but this error is recent, before I had problem with booting and flashing the recovery. I'll attach an image of the error. Thanks for help.
{
"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"
}

Riccardo De Lucia said:
Ok, I tried again and I had the same problem, but this time I gave the command "adb reboot bootloader" to go in fastboot mode and as soon the device booted in fastboot the same message appeared, "press any key to shutdown". i mean, it is a lot frustrating, because I'm working to install the ROM since october but this error is recent, before I had problem with booting and flashing the recovery. I'll attach an image of the error. Thanks for help.
View attachment 5183239
Click to expand...
Click to collapse
What do you expect to be displayed on phone's display when phone is booted into fastboot mode? Fastboot doesn't offer an on-screen menu like recovery. You have to enter the fastboot commands on Windows computer's CMD and/or Powershell.
Code:
fastboot devices
fastboot <FASTBOOT-SUBCOMMAND>

Yes, when fastboot is booted there's no menu like recovery, but the image I attached is what I see every time I give a command, even "fastboot devices", using CMD on the Windows 10 laptop (I have a Ryzen 5 SoC).

Question Made A Mess - ROG 5 CN Fastboot Loop

Was trying to flash my CN ROM to the WW ROM.
Forgot to turn on USB Debugging in Developer Tools.
Couldn't get it work using HunterTik's guide.
Ran flashall_ATF from windows explorer.
Command prompt flashed on screen then vanished.
Tried running flashall_ATF in an elevated command prompt.
It failed but has apparently wiped the ROM. Device is now stuck in boot loop to fastboot.
Whatever option I choose reboots the device back to fastboot.
Windows can see the device but adb devices returns List of Devices Attached is blank.
How do I recover the phone from here?

Found this thread Rog phone 5 stucked on fastboot
Ran this command: fastboot -v flash all WW_ZS673KS_18.0830.2101.75_M2.13.24.14.1-ASUS_1.1.63_Phone-user.raw
Received these lines of text & now device boots to splash screen, gets stuck there, reboots a few times then sends me back to fastboot.
Still can't access recovery mode
{
"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"
}

Device is now back in a fastboot loop with no access to any options but power off & restart.

Your phone is broken
Buy a new phone and don't try to mess with it next time

Flash back to CN and try again.
or, get a dump of the official firmware, then sent boot / recovery / super over fastboot manually.
[Windows] Asus OTA payload auto extractor
Since nobody is doing it, I thought I'd package it and just put it here to help people This is a packaged version of Vm03's payload dumper make to work with windows without installing python and other stuff I also included a single line script...
forum.xda-developers.com
also, you might want to try 9008 rescue. it seems like whatever you're trying to do wiped / repart the partitions. that's why the BL is confused.
also, if you're on win11, some driver related **** can mess things up causing flashing fail.

yurishouse said:
also, you might want to try 9008 rescue. it seems like whatever you're trying to do wiped / repart the partitions. that's why the BL is confused.
also, if you're on win11, some driver related **** can mess things up causing flashing fail.
Click to expand...
Click to collapse
9008 rescue is the direction I was headed & you're right. Although, on reflection, the partitions were already deleted prior to running the 'fastboot -v flash all xx.raw' command. Not sure how, since that command was the only thing I did which resulted in something happening.

1st step to jailbroke

{
"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"
}
The only thing to do is to get a kernel exploit or something to turn **get_unlock_ability** into 1 qnd then just unlock the bootloader in fastboot mode.
Sound easy but will not be as it requires editing a root filesystem file.

ZModder said:
View attachment 5599971
The only thing to do is to get a kernel exploit or something to turn **get_unlock_ability** into 1 qnd then just unlock the bootloader in fastboot mode.
Sound easy but will not be as it requires editing a root filesystem file.
Click to expand...
Click to collapse
what? you didn't do anything. you found a story file talking about fastboot which anyone can radio access by sideloading a android root browser apk.... this has been known since the oculus go first dropped in like 2015....
you need a bootloader unlock code or script which only facebook can give you...it doesnt exist anywhere on the device and is not hidden...
you can try tool "mod" a system file but even if you somehow got the device to bypass the files intregity checks, it wouldnt actually work because you are "sandboxed". any changes you make will not alter system. functions or settings at all until you escape the "sandbox" which can only be done via a unlocked bootloader.
if still you somewhere tricked your device into saving any mods you made to system files, your device either will stop booting the OS or most basic device functions will stop worki g..

so i tried to go to fastboot mode. but something went wrong (i pressed vol- and vol+ and pwr at bad timing) now the screen is black, no buttons are working, you cant even hold pwr to reset the devices. and it looks like its a bootloader mode. i got this in my devicer manager.
but fastboot does nothing and adb even too.... what is this? is it any usefull?

raeumler said:
so i tried to go to fastboot mode. but something went wrong (i pressed vol- and vol+ and pwr at bad timing) now the screen is black, no buttons are working, you cant even hold pwr to reset the devices. and it looks like its a bootloader mode. i got this in my devicer manager. View attachment 5628753
but fastboot does nothing and adb even too.... what is this? is it any usefull?
Click to expand...
Click to collapse
That mode is used to flash the device but I doubt you can flash unofficial firmware.

Zillion said:
View attachment 5599971
The only thing to do is to get a kernel exploit or something to turn **get_unlock_ability** into 1 qnd then just unlock the bootloader in fastboot mode.
Sound easy but will not be as it requires editing a root filesystem file.
Click to expand...
Click to collapse
How about the new DirtyCred exploit?