Related
Hi,
my MI4c is bricked (there is no OS installed and usb debugging is not activated): I have TWRP installed, but I can't install a new OS from my PC because I can't use command prompts (usb debugging is not activated). I was thinking about buying a usb pen (type C) to try and install a custom ROM that way, but I'm not sure that will work. Anybody have any other ideas?
Thanks for any help.
Fastboot flash the MIUI and start from there.
jonvdw said:
Hi,
my MI4c is bricked (there is no OS installed and usb debugging is not activated): I have TWRP installed, but I can't install a new OS from my PC because I can't use command prompts (usb debugging is not activated). I was thinking about buying a usb pen (type C) to try and install a custom ROM that way, but I'm not sure that will work. Anybody have any other ideas?
Thanks for any help.
Click to expand...
Click to collapse
Can you copy files over MTP?
Problem solved. I was able to install a miui China rom using miflash. I then requested unlock permission from xiaomi, which was granted, and now I'm running a Superluminal marshmallow rom.
Hello, is there a way to enable usb debugging on the download or fastboot mode? I looked around but didnt find a final answer
survivor_evil said:
Hello, is there a way to enable usb debugging on the download or fastboot mode? I looked around but didnt find a final answer
Click to expand...
Click to collapse
Why? You don't need usb debugging if your phone is bricked... The only purpose of usb debugging is to enable adb connection from a booted rom. Only fastboot commands works from the bootloader and you don't need usb debug to use fastboot commands neither to use adb commands from a custom recovery.
alray said:
Why? You don't need usb debugging if your phone is bricked... The only purpose of usb debugging is to enable adb connection from a booted rom. Only fastboot commands works from the bootloader and you don't need usb debug to use fastboot commands neither to use adb commands from a custom recovery.
Click to expand...
Click to collapse
so how am I supposed to flash a fresh rom on it?
survivor_evil said:
so how am I supposed to flash a fresh rom on it?
Click to expand...
Click to collapse
You dont need usb debug to flash a ROM... Roms are flashed using TWRP or you can flash RUU using fastboot(or your sd card)
I had stock rom and it wasnt rooted neither so to install TWRP i have to enable usb debugging first.
survivor_evil said:
I had stock rom and it wasnt rooted neither so to install TWRP i have to enable usb debugging first.
Click to expand...
Click to collapse
Like said previously, the only purpose of usb debugging is to use adb commands from a booted rom. Your phone is bricked right? So it cant boot the rom. Usb debugging on/off makes no differences when the phone is booted in bootloader, download or recovery mode.
You dont need usb debug to install TWRP (fastboot flash recovery TWRP.img)
Once booted in TWRP you can flash your rom. And you can also use adb commands when booted in TWRP even is usb debug is off bcause again, usb debug doesn't matters when youre not booted in a ROM.
And if you want to stay on stock rom and flash a ruu instead of a ROM, you dont need usb debug neither (you dont even need adb).
As I said before you need to enable usb debugging to input fastboot commands and install a custom recovery.
survivor_evil said:
As I said before you need to enable usb debugging to input fastboot commands and install a custom recovery.
Click to expand...
Click to collapse
Then explain me why
edit
are you confusing "usb debugging" with "oem unlocking" which will prevent to unlock the BL if it was turned off?
alray said:
Then explain me why
edit
are you confusing "usb debugging" with "oem unlocking" which will prevent to unlock the BL if it was turned off?
Click to expand...
Click to collapse
every manual explaining how to install TWRP mentions that usb debugging has to be activated. My device didnt have the bootloader unlocked or the usb debugging activated.
Flash an RUU then to go stock, boot your phone enable OEM unlock and USB debugging and do as you please after that.
Στάλθηκε από το HTC 10 μου χρησιμοποιώντας Tapatalk
survivor_evil said:
every manual explaining how to install TWRP mentions that usb debugging has to be activated.
Click to expand...
Click to collapse
Misconception.
Fastboot and adb are 2 differents protocol.
In bootloader and download you can only use fastboot to communicate with the phone.
When booted in a custom recovery you can use adb to communicate with the phone (fastboot unavailable There)
When booted in the rom you can use adb only and usb debug must be on.
Usb debugging has no effect on fastboot, neither on adb from custom recovery. Its only needed to use adb from a booted Android os.
If you cant use fastboot check your drivers, usb debugging isnt in cause.
To unlock your bootloader you need to activate "oem unlocking". If it was off you wont be able to unlock but still you can use fastboot to flash a ruu to restore your phone.
If you need help with the RUU I can help.
If you still want to debate about usb debugging ill pass my turn.
survivor_evil said:
every manual explaining how to install TWRP mentions that usb debugging has to be activated. My device didnt have the bootloader unlocked or the usb debugging activated.
Click to expand...
Click to collapse
To flash anything from fastboot you open a command prompt and type
Code:
htc_fastboot flash zip <file_name>.zip
This is NOT related to
Code:
adb <whatever command you want>
fastboot != adb
as said in the previous posts, installing TWRP or any ROM does not require USB debugging.
Using adb, short for Android Debug Bridge, requires USB debugging to be on in the running rom's developer settings.
I have a problem with my Moto G 1st gen. It seems while attempting to flash a new ROM onto the device, I have somehow managed to delete the OS. I am trying to flash the stock ROM back onto the device, but unfortunately I am unable to as the device does not appear on my computer when I plug it in using a USB cable. I am using the TWRP custom recovery. I would like to be able to restore the original ROM and use the device as normal. Any help would be greatly appreciated.
Device:
Moto G 1st Gen (XT1033)
TWRP Recovery installed
OS is missing
When I attempt to boot the device, it gives me the unlocked bootloader warning.
To recover your ROM, use your backup. If you do not have a backup ... it's bad.
Have you tried booting in fastboot? Does your mobile show up in the taskbar icons tray as ADB Device or Motorola ADB Composite Device? If not, check if you've proper drivers installed or not. Once you've the phone being detected, you can easily flash the stock rom using mfastboot commands.
niun01 said:
To recover your ROM, use your backup. If you do not have a backup ... it's bad.
Click to expand...
Click to collapse
My backup appears to have been deleted as well.
SpiralX15 said:
Have you tried booting in fastboot? Does your mobile show up in the taskbar icons tray as ADB Device or Motorola ADB Composite Device? If not, check if you've proper drivers installed or not. Once you've the phone being detected, you can easily flash the stock rom using mfastboot commands.
Click to expand...
Click to collapse
I am able to get the device in fastboot mode, and I have confirmed that the correct drivers have been installed, but the phone is still not detected.
SpiralX15 said:
Have you tried booting in fastboot? Does your mobile show up in the taskbar icons tray as ADB Device or Motorola ADB Composite Device? If not, check if you've proper drivers installed or not. Once you've the phone being detected, you can easily flash the stock rom using mfastboot commands.
Click to expand...
Click to collapse
Ok it seems the phone is detected by the computer, the phone is shown when I go to 'Devices and Printers' on my computer, but for some reason it shows as 'XT1032' instead of 'XT1033'. Probably attempted to install something designed for the XT1032 model instead.
https://forum.xda-developers.com/showthread.php?t=2542219
follow this thread to install stock lollipop ROM
Windows_95 said:
Ok it seems the phone is detected by the computer, the phone is shown when I go to 'Devices and Printers' on my computer, but for some reason it shows as 'XT1032' instead of 'XT1033'. Probably attempted to install something designed for the XT1032 model instead.
Click to expand...
Click to collapse
It's probably TWRP Recovery that changed the model detection. Now, either install the stock ROM or flash a custom ROM.
SpiralX15 said:
It's probably TWRP Recovery that changed the model detection. Now, either install the stock ROM or flash a custom ROM.
Click to expand...
Click to collapse
I cannot, as the phone does not appear in the 'This PC' in File Explorer on my computer, so I cannot transfer any files between the computer and the phone.
Windows_95 said:
I cannot, as the phone does not appear in the 'This PC' in File Explorer on my computer, so I cannot transfer any files between the computer and the phone.
Click to expand...
Click to collapse
make sure that you have enabled MTP in TWRP..
in twrp recovery select Mount >> Enable MTP
change USB cable if you still facing problem
SunilSuni said:
make sure that you have enabled MTP in TWRP..
in twrp recovery select Mount >> Enable MTP
change USB cable if you still facing problem
Click to expand...
Click to collapse
It still doesn't work. I cannot transfer files between the computer and the phone.
Windows_95 said:
It still doesn't work. I cannot transfer files between the computer and the phone.
Click to expand...
Click to collapse
Then reboot to fastboot mode and install stock ROM
SunilSuni said:
Then reboot to fastboot mode and install stock ROM
Click to expand...
Click to collapse
I cannot get the stock ROM onto the phone because I cannot transfer anything between the phone and computer, even in fastboot mode.
Windows_95 said:
I cannot get the stock ROM onto the phone because I cannot transfer anything between the phone and computer, even in fastboot mode.
Click to expand...
Click to collapse
Im talking about flashing stock ROM.. Use good USB cable and flash stock ROM
SunilSuni said:
Im talking about flashing stock ROM.. Use good USB cable and flash stock ROM
Click to expand...
Click to collapse
I managed to recover the device using Cyanogenmod ROM using the adb push command. Thanks for the help.
hello guys
how do i root this phone please.
none of the google searched guides seem to work.
1. i've unlocked the bootloader using the asus app
2. i have adb installed on my pc
3. i've enabled usb debug mode on phone and allowing installation unknown apps
4. i've installed magisk v23 by downloading from github and just installing the apk file normally
5. i've downloaded a 2.9gb zip file from asus for androind 11 firmware onto phone and pc (but its a zip file that extracts a bin file, no image file)
my problem seems to be i don't know how to CREATE AND PATCH an image file or install twrp and install image file that way.
Could someone help, there doesn't seem to be any guides for rooting in this phones forum.
Look in the twrp thread: https://forum.xda-developers.com/t/recovery-official-twrp-for-asus-zenfone-7-series.4161719/
after twrp you can flash the magisk.zip
Seosam said:
Look in the twrp thread: https://forum.xda-developers.com/t/recovery-official-twrp-for-asus-zenfone-7-series.4161719/
after twrp you can flash the magisk.zip
Click to expand...
Click to collapse
i keep getting era waiting for device when i want to flash the phoben with twrp.
adb reboot bootloader (works and i enter the recovery menu start, bootloader, recovery, power off etc)
fastboot flash recovery_a twrp.img (when i type this cmd power shell just says waiting for device)
i have universal drivers installed and android sdk installed. not sure why it isn't recognising the phone?
When my phone is switched on normally, cmd recognises it, when i use adb devices. but as soon as i reboot into recovery mode using cmd "adb reboot bootloader" it stops recognising the phone on the list of devices using the cmd "adb devices"
so you don`t get an answer from your phone by "fastboot devices" ?
Have you tried another usb cable and or port?
Seosam said:
so you don`t get an answer from your phone by "fastboot devices" ?
Have you tried another usb cable and or port?
Click to expand...
Click to collapse
no answer from phone when in fastboot mode.
but i do get a reply in cmd when phone is switched on normally.
I'll try with another cable, but if it responds to adb when in normal mode. doesn't it mean it's not a cable issue but a software driver issue?
Seosam said:
so you don`t get an answer from your phone by "fastboot devices" ?
Have you tried another usb cable and or port?
Click to expand...
Click to collapse
seems when i do adb reboot bootloader it goes into what i thought was called fastboot. It even says fastboot.
but in that mode my phone isn't recognised by cmd when type adb devices, it doesn't come up.
it has 4 options reboot system now, botloader, enter recovery, reboot to bootloader, power off.
if i then select enter recovery. it enters a smaller text screen with lots of small blue writing. when inside that screen (recovery mode) cmd seems to recognise my device.
but it says it is unauthorized. this is in recovery mode.
i'm not sure why it says it is unauthorized. i've authorised my pc to control the phone through the fingerprint, when the message popped up.
but i can't push the twrp.img file through because of this.
since cmd doesn't seem to recognise phone in fastboot mode.
and cmd doesn't seem to have authorisation in recovery mode.
any ideas?
is it possible to root using adb sideload or install twrp using adb sideload?
articoceanic said:
seems when i do adb reboot bootloader it goes into what i thought was called fastboot. It even says fastboot.
but in that mode my phone isn't recognised by cmd when type adb devices, it doesn't come up.
it has 4 options reboot system now, botloader, enter recovery, reboot to bootloader, power off.
if i then select enter recovery. it enters a smaller text screen with lots of small blue writing. when inside that screen (recovery mode) cmd seems to recognise my device.
but it says it is unauthorized. this is in recovery mode.
i'm not sure why it says it is unauthorized. i've authorised my pc to control the phone through the fingerprint, when the message popped up.
but i can't push the twrp.img file through because of this.
since cmd doesn't seem to recognise phone in fastboot mode.
and cmd doesn't seem to have authorisation in recovery mode.
any ideas?
Click to expand...
Click to collapse
Thats the right mode.
Does the phone at normal start show that the bootloader is unlocked?
Your debugging mode is turned on in developer settings?
A sideload isn`t possible I think.
Seosam said:
Thats the right mode.
Does the phone at normal start show that the bootloader is unlocked?
Your debugging mode is turned on in developer settings?
A sideload isn`t possible I think.
Click to expand...
Click to collapse
yes, shows bootloader is unlocked when i start the phone.
usb debugging mode is turned on.
i think for some reason in fastboot mode the device driver is not recognised in windows. have googled seems it was a very old problem that happned on phones 6 years ago. nut i haven't found anything recent to solve same error.
articoceanic said:
yes, shows bootloader is unlocked when i start the phone.
usb debugging mode is turned on.
i think for some reason in fastboot mode the device driver is not recognised in windows. have googled seems it was a very old problem that happned on phones 6 years ago. nut i haven't found anything recent to solve same error.
Click to expand...
Click to collapse
So you can just try it on another pc.
Have you changed from USB 3 port to a USB 2?
My Xiaomi mix2s had sometimes this too. That's worked for me.
Seosam said:
So you can just try it on another pc.
Have you changed from USB 3 port to a USB 2?
My Xiaomi mix2s had sometimes this too. That's worked for me.
Click to expand...
Click to collapse
i think its definitely a driver issue. windows 10 seems to be overriding the drivers and installing wrong ones. and won't let me install right ones.
haven't tried in a different pc. will need to get hold of one and try.
Seosam said:
So you can just try it on another pc.
Have you changed from USB 3 port to a USB 2?
My Xiaomi mix2s had sometimes this too. That's worked for me.
Click to expand...
Click to collapse
dont'know what happened. but weirdly i used usb 2.0 as you said and the driver listed on page 2 of this link got recognised.
[RECOVERY][OFFICIAL] TWRP for ASUS ZenFone 7 Series
*** Disclaimer *** All flashing is done at your own risk! While nothing from this thread should break your device, don't come back here blaming anyone if it does! Introduction Team Win Recovery Project 3.x, or twrp3 for short, is a custom...
forum.xda-developers.com
all this time windows 10 wouldn't let me install it. kept saying the drivers i already had was the best ones. but weirdly this time it did.
thanks friend. i think i have root access now. magisk keeps asking me to install the app tho. not sure why. i have version 23.0 installed.
but when i opne magisk it shows install icons for magisk and an unknown App. both listed as version 23.0.
Seosam said:
So you can just try it on another pc.
Have you changed from USB 3 port to a USB 2?
My Xiaomi mix2s had sometimes this too. That's worked for me.
Click to expand...
Click to collapse
last question friend, thanks for all your help.
where do i download apps like ad block plus adaway minmingaurd etc.
magisk dowsn't seem to have an option for that.
articoceanic said:
last question friend, thanks for all your help.
where do i download apps like ad block plus adaway minmingaurd etc.
magisk dowsn't seem to have an option for that.
Click to expand...
Click to collapse
how solve com.asus.service keep stopping after install twrp? android 11 stock rom please answer
decade 1 said:
how solve com.asus.service keep stopping after install twrp? android 11 stock rom please answer
Click to expand...
Click to collapse
I'm not sure.
i only managed to root it by following the instructions here years ago.
maybe try updating the asus apps in play store? or ask some of the other people here who know more than me. or disable the asus apps. i don't use them.
sorry i couldn't help more
articoceanic said:
I'm not sure.
i only managed to root it by following the instructions here years ago.
maybe try updating the asus apps in play store? or ask some of the other people here who know more than me. or disable the asus apps. i don't use them.
sorry i couldn't help more
Click to expand...
Click to collapse
I try factory reset normal again I hope no recurrence
My phone. - Galaxy A51, One UI Version is 4.1, Android version is 12, Product Name – SM-A515F.
Stock ROM up to date.
I can boot into download mode, +/- volume, connect to pc. Works just fine.
But + volume & power boots into safe mode; - volume & power boots into safe mode; +/- volume & power boots into safe mode; +/- volume only boots into safe mode. I have ran out of button sequences to try.
What is wrong with my phone, is it impossoble to boot into recovery mode on my model of phone. This is why I cannot install TWRP as when I install via Odin, it will not boot into recovery post installation.
I am stumped.
Hello!
What is about phone: is it bootlooping or is it in downloading mode?
Other question: from what source did you download the twrp.tar file?
You should be able to force a reboot to recovery using ADB. Enable developer options, then enable USB Debugging. Download the SDK Platform Tools and open a command line in the platform tools directory (where you find the fastboot, adb, etc programs)
First, type adb devices. ADB will then start the ADB daemon.
Next, connect your device via USB cable while unlocked. You should get a prompt on the device screen requesting USB debugging authorization. Go ahead and grant it.
Then, type adb devices again. If you authorized USB debugging correctly, you should see your device listed.
Now, type adb reboot recovery. Your device should reboot into TWRP.
V0latyle said:
You should be able to force a reboot to recovery using ADB. Enable developer options, then enable USB Debugging. Download the SDK Platform Tools and open a command line in the platform tools directory (where you find the fastboot, adb, etc programs)
First, type adb devices. ADB will then start the ADB daemon.
Next, connect your device via USB cable while unlocked. You should get a prompt on the device screen requesting USB debugging authorization. Go ahead and grant it.
Then, type adb devices again. If you authorized USB debugging correctly, you should see your device listed.
Now, type adb reboot recovery. Your device should reboot into TWRP.
Click to expand...
Click to collapse
Guy, to complete the TWRP installation, it is needed to flash Disable_Dm-Verity_ForceEncrypt from TWRP, otherwise the device will not boot properly
vmirrimv said:
Other question: from what source did you download the twrp.tar file?
Click to expand...
Click to collapse
It's in Stock now. But it was stuck in a bootloop, but could boot into download mode. These are the recovery's which all installed but I could not boot into. I cannot boot into recovery now I am in Stock. It's as if there is no recovery option for my A51.
Twrp+vbmeta_A11.tar,
TWRP-11-3.6.0-a51-20220210-1636.tar,
TWRP-11-3.6.1-a51-20220228-2050.tar,
TWRP-11-3.6.1-a51-20220321-1406-hotfix.tar,
TWRP-11-3.6.2-a51-20220602-0515.tar,
twrp-a51-3.5.0_10-1_ianmacd.tar
vmirrimv said:
Guy, to complete the TWRP installation, it is needed to flash Disable_Dm-Verity_ForceEncrypt from TWRP, otherwise the device will not boot properly
Click to expand...
Click to collapse
I was stuck in a bootloop and could not boot into TWRP..
Unless there is a way to flash Disable_Dm-Verity_ForceEncrypt in downlad mode using Odin?
V0latyle said:
You should be able to force a reboot to recovery using ADB. Enable developer options, then enable USB Debugging. Download the SDK Platform Tools and open a command line in the platform tools directory (where you find the fastboot, adb, etc programs)
First, type adb devices. ADB will then start the ADB daemon.
Next, connect your device via USB cable while unlocked. You should get a prompt on the device screen requesting USB debugging authorization. Go ahead and grant it.
Then, type adb devices again. If you authorized USB debugging correctly, you should see your device listed.
Now, type adb reboot recovery. Your device should reboot into TWRP.
Click to expand...
Click to collapse
Hi I am back in stock now, so no TWRP installed. Would this method boot you into Stock recovery?
Do I need to be in download mode or just normal mode when connecting the phone to the pc?
Hello, can you say what version of Android your phone on?
If it is on 12th, then I would say, that the problem is, that this version may not fully supported for TWRP working
Because as I tried, there was a fail in the procces.
Sorry, i did not see that you have already written about it
Yep, think I will have to download Android 10 stock rom; and hopefully be able to install 10 via Odin from 12 back to 10.
Sign1 said:
Hi I am back in stock now, so no TWRP installed. Would this method boot you into Stock recovery?
Do I need to be in download mode or just normal mode when connecting the phone to the pc?
Click to expand...
Click to collapse
ADB commands must be issued in system. The alternative would be from fastboot but it doesn't seem you can access that.
Try flashing TWRP again, but immediately hold Volume Up during boot to force booting into TWRP. Newer Samsung firmware does seem to have some sort of security measure that will replace a custom recovery, so you'll have to flash the Multidisabler to disable stock recovery auto-restoration.
Sign1 said:
Yep, think I will have to download Android 10 stock rom; and hopefully be able to install 10 via Odin from 12 back to 10.
Click to expand...
Click to collapse
I do not want to mislead you, but you will not be able to roll back from Android 12 to Android 10, because the current binary version of your phone (5) cannot be changed to lower one (4).
Maximum as you can do, is to downgrade to the 11th version and there, as I think and tried, the Twrp+vbmeta_A11.tar recovery file will be flashed sucessfuly and you will be able to enter TWRP without issues like bootloop.
Other problems are, as I think, that you may forgot to enable USB Debugging on your phone and authorize it with your computer, you may forgot to set the default USB Configuration as data transfer (MTP), or even you may not unlocked the bootloader.
I think they are the reasons because of which you could not enter TWRP, because, as I have tried to flash One UI 4.1 Android 12 according to this thread recently: https://forum.xda-developers.com/t/...ecovery-project-v3-6-2-android-11-12.4400869/
everything has been sucessful, both flashing and entering and following rebooting to Stock system.
Or you may even not removed the check mark from the parameter "Auto Reboot" in Odin
vmirrimv said:
I do not want to mislead you, but you will not be able to roll back from Android 12 to Android 10, because the current binary version of your phone (5) cannot be changed to lower one (4).
Maximum as you can do, is to downgrade to the 11th version and there, as I think and tried, the Twrp+vbmeta_A11.tar recovery file will be flashed sucessfuly and you will be able to enter TWRP without issues like bootloop.
Click to expand...
Click to collapse
Cheers for that, just downloaded Android 10, took me twelve hours to download, so its no use to me. I need to download Android 11.
vmirrimv said:
Or you may even not removed the check mark from the parameter "Auto Reboot" in Odin
Click to expand...
Click to collapse
Yep did that.