i was trying to install twrp in my rog 2 but while installing twrp from fastboot and adb i got stuck in fastboot mode and cannot boot into main OS PLEASE HELP ME
Check current slot and then switch to other slot and boot.
First try
fastboot devices (make sure your device is listed)
if it boots to fastboot again
fastboot getvar current-slot
fastboot --set-active=a or fastboot --set-active=b
fastboot reboot
rabunz1105 said:
Check current slot and then switch to other slot and boot.
First try
fastboot devices (make sure your device is listed)
if it boots to fastboot again
fastboot getvar current-slot
fastboot --set-active=a or fastboot --set-active=b
fastboot reboot
Click to expand...
Click to collapse
Have the same problem. Did all that you say but keeps restarting.
ED_STUFF said:
Have the same problem. Did all that you say but keeps restarting.
Click to expand...
Click to collapse
I had this problem, and I had to download the RAW firmware files and run the "flashall.bat" file through fastboot.
ED_STUFF said:
Have the same problem. Did all that you say but keeps restarting.
Click to expand...
Click to collapse
Did you manage to solve this issue? I have the same problem.
rabunz1105 said:
Check current slot and then switch to other slot and boot.
First try
fastboot devices (make sure your device is listed)
if it boots to fastboot again
fastboot getvar current-slot
fastboot --set-active=a or fastboot --set-active=b
fastboot reboot
Click to expand...
Click to collapse
I was in csc fastboot mode then i mistakenly did some fastboot adb commands from github rog phone 2(am having rog 3, works same) try those and you will get into fast boot mode from csc fastboot mode after than try above for any query contaact me on my mail [email protected]
Thanks xda love you
rabunz1105 said:
Check current slot and then switch to other slot and boot.
First try
fastboot devices (make sure your device is listed)
if it boots to fastboot again
fastboot getvar current-slot
fastboot --set-active=a or fastboot --set-active=b
fastboot reboot
Click to expand...
Click to collapse
Flash fastboot Raw firmware
My phone is stuck in a bootloop. Original firmware, rom, everything, not rooted, bootloader locked. It just restarted by itself randomly and has been stuck in a bootloop ever since. I've flashed raw firmware but it didn't help. Help please
shinnsan said:
My phone is stuck in a bootloop. Original firmware, rom, everything, not rooted, bootloader locked. It just restarted by itself randomly and has been stuck in a bootloop ever since. I've flashed raw firmware but it didn't help. Help please
Click to expand...
Click to collapse
Have you fixed your issue? if not, have you tried flashing both slots, _a and _b, using the same raw rom? use fastboot cmd's to set either slot_a or slot_b to active so you know you're flashing each slot
Related
Hello, please help me with the following.
My Moto X4 (XT1900-7) recently got the Android 9 (Pie) update. Since then I have problems with wifi and it's always dropping. Because of that I reset the phone, but now I can't even log into Play Store, because wifi keeps dropping all the time. I can't use the phone at all. Every guide I've tried getting back Android 8.1 back didn't work so far. Maybe the guides were **** or I simply didn't understand them. Also, my recovery mode doesn't even start.
I've downloaded "PAYTON_OPW27.57-40_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml". Would that be the correct version to install?
Please help.
Thanks in advance.
curious45 said:
Hello, please help me with the following.
My Moto X4 (XT1900-7) recently got the Android 9 (Pie) update. Since then I have problems with wifi and it's always dropping. Because of that I reset the phone, but now I can't even log into Play Store, because wifi keeps dropping all the time. I can't use the phone at all. Every guide I've tried getting back Android 8.1 back didn't work so far. Maybe the guides were **** or I simply didn't understand them. Also, my recovery mode doesn't even start.
I've downloaded "PAYTON_OPW27.57-40_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml". Would that be the correct version to install?
Please help.
Thanks in advance.
Click to expand...
Click to collapse
This one:
PAYTON_OPWS28.46-21-16_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
but two things:
1) Your bootloader needs to be unlocked. If you have a locked bootloader and try to go 9 -> 8.1 you are bootlooped.
2) You will still get prompts to upgrade to Android 9. You can ignore them but they won't ever go away.
Yeah, I first need to unlock the bootloader, but that's where the problems start. I found a guide on motorola web page: motorola-global-portal[.]custhelp[.com]/app/standalone/bootloader/unlock-your-device-b
I've downloaded Android SDK (1 GB??!) and installed it. Then I've installed Motorola Device Manager. I've set my X4 to Fastboot Mode. The next step "On your desktop, open a command prompt or terminal, and go to the directory where you installed the Android SDK tools (or make sure fastboot is in your $PATH)" I don't even understand. How do I "go to the directory", and what's my "$PATH"? That guide is as bad as it gets. I doesn't explain anything.
Edit: I've tried it through minimal adb fastboot command and could get my unlock-key. let's see how it goes from now on.
Thanks so far.
curious45 said:
Yeah, I first need to unlock the bootloader, but that's where the problems start. I found a guide on motorola web page: motorola-global-portal[.]custhelp[.com]/app/standalone/bootloader/unlock-your-device-b
I've downloaded Android SDK (1 GB??!) and installed it. Then I've installed Motorola Device Manager. I've set my X4 to Fastboot Mode. The next step "On your desktop, open a command prompt or terminal, and go to the directory where you installed the Android SDK tools (or make sure fastboot is in your $PATH)" I don't even understand. How do I "go to the directory", and what's my "$PATH"? That guide is as bad as it gets. I doesn't explain anything.
Edit: I've tried it through minimal adb fastboot command and could get my unlock-key. let's see how it goes from now on.
Thanks so far.
Click to expand...
Click to collapse
I only get error messages when entering all the fastboot commands.
FAILED (command write failed (Unknown error))
I could flash it using my laptop now, but when turning it on it says "verity mode is set to logging" and keeps on rebooting in a loop. Then I tried using twrp and mount it using an sd card, but that gave me error messages. are you sure this version is the right one for me? How difficult can it be? I wanna smash the phone against a wall.
curious45 said:
I could flash it using my laptop now, but when turning it on it says "verity mode is set to logging" and keeps on rebooting in a loop. Then I tried using twrp and mount it using an sd card, but that gave me error messages. are you sure this version is the right one for me? How difficult can it be? I wanna smash the phone against a wall.
Click to expand...
Click to collapse
It is the correct Oreo firmware for your device.
Re-verify the commands you're entering to flash are:
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash boot boot.img
fastboot flash logo logo.bin
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
Bootloader is unlocked (the bottom of your fastboot screen says 'flashing_unlocked')?
Are you trying this in windows or linux?
I tried this version: PAYTON_OPWS28.46-21-16_subsidy-DEFAULT_regulatory-DEFAULT very often on my laptop (I guess it was a problem with the usb-ports on my normal pc), but I couldn't get my device to work. It always said "verity mode is set to logging". Then I tried installing PAYTON_OPW27.57-40_subsidy-DEFAULT_regulatory-DEFAULT once (with my laptop) and it worked without any problems. The only thing is, that the device now says it's not the correct os when booting.
curious45 said:
... It always said "verity mode is set to logging"....
Click to expand...
Click to collapse
This will display for everyone with an unlocked bootloader. I know it does for me.
jhedfors said:
This will display for everyone with an unlocked bootloader. I know it does for me.
Click to expand...
Click to collapse
But it didn't boot though. It showed this text and it kept restarting over and over again.
It's fine now with this PAYTON_OPW27.57-40_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml version, but I always get the notifications that I should update to Android 9. I don't have any wifi problems whatsoever.
Do you have a solution on how to really disable / block those?
Hello, I installed Havoc OS on my MI A2, but then an update was requested, I did the update, but when I rebooted the device, it did not start, I went into fastboot mode and I reinstalled the havoc. "androidOne" screen and nothing happens, now I have to enter fastboot mode with the command "fastboot boot twrp.img" and the error "failed to load / authentication boot image" appears, I tried flashing the rom stock using the MiFlash, and the cell phone persists with the same error, now my cell phone is with the bootloader locked and I do not know what to do
gmoura5010 said:
Hello, I installed Havoc OS on my MI A2, but then an update was requested, I did the update, but when I rebooted the device, it did not start, I went into fastboot mode and I reinstalled the havoc. "androidOne" screen and nothing happens, now I have to enter fastboot mode with the command "fastboot boot twrp.img" and the error "failed to load / authentication boot image" appears, I tried flashing the rom stock using the MiFlash, and the cell phone persists with the same error, now my cell phone is with the bootloader locked and I do not know what to do
Click to expand...
Click to collapse
Hi
Enter to fastboot and try this:
open a cmd
fastboot devices
fastboot -w
fastboot getvar current-slot ( you can see it a or b)
fasboot set_active b
Then
Try boot into twrp etc
Have luck pal !!
rodrimx4 said:
Hi
Enter to fastboot and try this:
open a cmd
fastboot devices
fastboot -w
fastboot getvar current-slot ( you can see it a or b)
fasboot set_active b
Then
Try boot into twrp etc
Have luck pal !!
Click to expand...
Click to collapse
Thanks, I was able to repair after unlocking the bootloader again and then unlocking the critical parts, so I flashed a stock rom from August 2018, however didn't block the bootloader again.
I have a moto z3 play and I have already unlocked bootloader and installed a custom recovery and rooted, the only problem is that every single time I boot up my phone it goes to fastboot and in the log it says Fastboot reason: Reboot mode set to Fastboot. I would usually be able to fix it by switching slots in twrp, but now both slots a/b are booting me to fastboot. Any help would be appreciated. EDIT: Worked after reinstalling firmware but after 5 hours it's back to the way it was, also when I boot into slot B in twrp it just bootloops .
Razzarac said:
I have a moto z3 play and I have already unlocked bootloader and installed a custom recovery and rooted, the only problem is that every single time I boot up my phone it goes to fastboot and in the log it says Fastboot reason: Reboot mode set to Fastboot. I would usually be able to fix it by switching slots in twrp, but now both slots a/b are booting me to fastboot. Any help would be appreciated.
Click to expand...
Click to collapse
Code:
fastboot oem fb_mode_clear
fastboot reboot
Sent from my Moto E (4) using Tapatalk
sd_shadow said:
Code:
fastboot oem fb_mode_clear
fastboot reboot
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
I already tried that and it didn't work at all
Hi,
I got TWRP on my Oneplus Nord CE. Which a EU version. Somehow I managed by accident in TWRP setting, to switch the boot to the wrong slot (slot a), and the boot is on slot b.
Now it keeps booting in to a failure screen.
Anyone who can point me in the right direction, to get it back on slot b?
/_13
'fastboot reboot fastboot' to boot to fastbootd
then 'fastboot set_active b'
enritto said:
'fastboot reboot fastboot' to boot to fastbootd
then 'fastboot set_active b'
Click to expand...
Click to collapse
Thanks a lot.
I used this command and it worked just fine
Code:
fastboot --set-active=b
/_13
Hi - not wanting to hijack the thread but ive got a semi bricked unit and spent the last 2 weeks trying to resurect it....ive had no luck with the MSM tool so trying to reflash using the extracted payload.bin files individually...which mode should it be in? (a or b) to reflash the img files?
My PC cannot detect my phone in fastboot mode. It always get stuck on <waiting for device> when enter command fastboot flashing unlock or any fastboot command. How can I fix this?
yarri0 said:
My PC cannot detect my phone in fastboot mode. It always get stuck on <waiting for device> when enter command fastboot flashing unlock or any fastboot command. How can I fix this?
Click to expand...
Click to collapse
Install drivers correctly.
yarri0 said:
My PC cannot detect my phone in fastboot mode. It always get stuck on <waiting for device> when enter command fastboot flashing unlock or any fastboot command. How can I fix this?
Click to expand...
Click to collapse
i agree with humayun.bd, please install your usb drivers correctly