Related
Hi,I just installed android 4.4.3 from 4.4.2 rooted with kernel mat1x v13.5 with the following steps:
adb reboot bootloader
fastboot flash bootloader bootloader-mako-makoz30d.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.02.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Then installed CWM by:
adb reboot bootloader
fastboot flash recovery recovery-clockwork-touch-6.0.4.7.img
fastboot reboot-bootloader
and then I tried to go to recovery mode with:
Code:
fastboot reboot-bootloader
but the command line says:
Code:
<waiting for device>
. If I write:
Code:
fastboot devices
, nothing happens, but if I write:
Code:
adb devices
it does recognizes my phone.
Anyway I went to recovery mode with volume buttons (CWM is properly installed), went to sideload options, USB connected and typed:
Code:
adb sideload UPDATE-SuperSU-v1.99r3.zip
but it says:
Code:
error: device not found
While I'm in Recovery mode (in CWM) adb devices can't find any device.
SDK tools and platform-tools are just updated and PC is just rebooted.
EXTRA INFO: when i go out of CWM it says:
Code:
Root access is missing. Root device? THIS CANNOT BE UNDONE.
and options are
-no
-Yes - Root device (/system/xbin/su)
When I choose Yes it just starts with no problems.
Anything?
oliverm91 said:
Hi,I just installed android 4.4.3 from 4.4.2 rooted with kernel mat1x v13.5 with the following steps:
adb reboot bootloader
fastboot flash bootloader bootloader-mako-makoz30d.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.02.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Then installed CWM by:
adb reboot bootloader
fastboot flash recovery recovery-clockwork-touch-6.0.4.7.img
fastboot reboot-bootloader
and then I tried to go to recovery mode with:
Code:
fastboot reboot-bootloader
but the command line says:
Code:
<waiting for device>
. If I write:
Code:
fastboot devices
, nothing happens, but if I write:
Code:
adb devices
it does recognizes my phone.
Anyway I went to recovery mode with volume buttons (CWM is properly installed), went to sideload options, USB connected and typed:
Code:
adb sideload UPDATE-SuperSU-v1.99r3.zip
but it says:
Code:
error: device not found
While I'm in Recovery mode (in CWM) adb devices can't find any device.
SDK tools and platform-tools are just updated and PC is just rebooted.
EXTRA INFO: when i go out of CWM it says:
Code:
Root access is missing. Root device? THIS CANNOT BE UNDONE.
and options are
-no
-Yes - Root device (/system/xbin/su)
When I choose Yes it just starts with no problems.
Click to expand...
Click to collapse
Try reboot the phone and then reboot to recovery and see if that works. If not, try TWRP recovery.
taodan said:
Try reboot the phone and then reboot to recovery and see if that works. If not, try TWRP recovery.
Click to expand...
Click to collapse
You mean turn off the phone and turn on to recovery? Because I've already done that as I mentioned in the first post.
Not sure but aren't recovery mode and fastboot mode different?
Can you manually boot into fastboot mode on your phone rather than using adb commands?
audit13 said:
Not sure but aren't recovery mode and fastboot mode different?
Can you manually boot into fastboot mode on your phone rather than using adb commands?
Click to expand...
Click to collapse
I just used fastboot to go into recovery with my pc because i'm lazy, I can do it with the mobile, but when i tried I discovered the <waiting for device> error. And I need to use adb coomands to sideload SuperSU. I think i can flash it from the phone, but it still bothers me the fact that there is something wrong, because I use my phone to test personals apks.
oliverm91 said:
I just used fastboot to go into recovery with my pc because i'm lazy, I can do it with the mobile, but when i tried I discovered the <waiting for device> error. And I need to use adb coomands to sideload SuperSU. I think i can flash it from the phone, but it still bothers me the fact that there is something wrong, because I use my phone to test personals apks.
Click to expand...
Click to collapse
Are you using a Windows PC? If you are, boot into task mamager and kill all ADB services. Relaunch the command prompt and try it.
audit13 said:
Are you using a Windows PC? If you are, boot into task mamager and kill all ADB services. Relaunch the command prompt and try it.
Click to expand...
Click to collapse
I am, Windows 8. But this problems happens even after rebooting my PC.
oliverm91 said:
I am, Windows 8. But this problems happens even after rebooting my PC.
Click to expand...
Click to collapse
I assume the drivers load the first time you connect your phone. Does running the command prompt as an admin make a difference?
audit13 said:
I assume the drivers load the first time you connect your phone. Does running the command prompt as an admin make a difference?
Click to expand...
Click to collapse
I use PowerShell as admin
No clue?
Revoke USB debugging authorizations for all the devices from the developer options and try again..
Sent from my Nexus 4 using Tapatalk
Adb and fastboot are two different things. Use adb commands when you're booted into recovery or normally booted. Use fastboot commands when you boot into the bootloader
Sent from my Nexus 5 using XDA Free mobile app
karthi89 said:
Revoke USB debugging authorizations for all the devices from the developer options and try again..
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Did this, but ADB still doesn't recognize my phone while in recovery.
jd1639 said:
Adb and fastboot are two different things. Use adb commands when you're booted into recovery or normally booted. Use fastboot commands when you boot into the bootloader
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Ok, but ADB won't recognize my device when it's on CWM (CWM v6.0.4.7)
I realised that in "device manager" of Windows a yellow triangle appears on "Other devices" -> Nexus 4 (when im in Recovery)
and when I normally boot my phone it appears normally under "Android device" -> android composite adb interface
No clue?
Hello,
Can anyone assist me in fixing my issue? My phone couldn't boot to recovery mode, i see the TWRP bluescreen and it immediately enters the boot loop. I can boot to fastboot&rescue mode but adb is not detecting my devices. I tried reinstalling the driver and also restart the adb server, but no luck. Tried different USB ports \cable\laptop, but no luck.
Need some assistance or direction to address this issue.
Regards
sri1225 said:
Hello,
Can anyone assist me in fixing my issue? My phone couldn't boot to recovery mode, i see the TWRP bluescreen and it immediately enters the boot loop. I can boot to fastboot&rescue mode but adb is not detecting my devices. I tried reinstalling the driver and also restart the adb server, but no luck. Tried different USB ports \cable\laptop, but no luck.
Need some assistance or direction to address this issue.
Regards
Click to expand...
Click to collapse
adb does not work in the bootloader (Fastboot mode)
in bootloader use
fastboot boot twrp.img
just be sure twrp has the correct name and is in the same folder as adb / fastboot
@sri1225,
Adding to clsA post:
If the phone is in fastboot mode, "fastboot devices" should work to confirm PC connection is good and produces a similar response as "adb devices" does when in adb mode.
What led up to the phone getting broken? You said it's bricked - so it won't boot up to normal operating mode?
clsA said:
adb does not work in the bootloader (Fastboot mode)
in bootloader use
fastboot boot twrp.img
just be sure twrp has the correct name and is in the same folder as adb / fastboot
Click to expand...
Click to collapse
divineBliss said:
@sri1225,
Adding to clsA post:
If the phone is in fastboot mode, "fastboot devices" should work to confirm PC connection is good and produces a similar response as "adb devices" does when in adb mode.
What led up to the phone getting broken? You said it's bricked - so it won't boot up to normal operating mode?
Click to expand...
Click to collapse
I tried to flash with the B180+Stock+Rom, after that I cannot go back to TWRP or in recovery mode.
When I do the "fastboot boot twrp.img", in the fastboot&rescue mode, the phone reboots to twrp screen and goes back to the boot loop again. I have tried both the twrp images available in the forum for this device.
Regards
sri1225 said:
I tried to flash with the B180+Stock+Rom, after that I cannot go back to TWRP or in recovery mode.
When I do the "fastboot boot twrp.img", in the fastboot&rescue mode, the phone reboots to twrp screen and goes back to the boot loop again. I have tried both the twrp images available in the forum for this device.
Regards
Click to expand...
Click to collapse
The B180 stock rom replaces TWRP with stock recovery
If you want TWRP again flash it from the bootloader
fastboot flash recovery twrp.img
when you enter TWRP
goto Wipe/Format Data/ and type yes
now you can root the phone or leave it as is
Fwiw, the 'boot' command only boots twrp, it doesn't flash it. Thats useful for testing that twrp works. The proper command to flash is immediately above this post. Take it from me - always test first. If it boots, it works.
clsA said:
The B180 stock rom replaces TWRP with stock recovery
If you want TWRP again flash it from the bootloader
fastboot flash recovery twrp.img
when you enter TWRP
goto Wipe/Format Data/ and type yes
now you can root the phone or leave it as is
Click to expand...
Click to collapse
Tried flashing TWRP but didn't work. Couldn't get to TWRP screen at all.
sri1225 said:
Tried flashing TWRP but didn't work. Couldn't get to TWRP screen at all.
Click to expand...
Click to collapse
Try the command 'fastboot devices', what does it output..? Are you sure you are in fastboot mode, with the screen and the Android with its chest popped open..?
Hi.
Recently I decided to flash lineage os 15.1 on my MiA1
For that I have downgrade to Android nougat.
After downgrading I booted my device.
After setting up device I booted device in fastboot mode to follow further steps like flashing TWRP and all but the problem is my device goes in fastboot mode and it is not identified by abd and after that it is automatically getting restarted and is not holding in fastboot mode.
Please help??
Odd issue. What are you using to flash? If you are using XiaoMiFlash.exe, you'll want to try the (THIS WILL REMOVE ALL YOUR DATA) "clean all" option. Please note that this removes all your data.
I have used MiFlash tool for this and now My device automatically reboot from fastboot mode so I am not able to use adb as well to flash rom or twrp also Now MiFlash tool is not recognising the device.
MrUsamahh said:
I have used MiFlash tool for this and now My device automatically reboot from fastboot mode so I am not able to use adb as well to flash rom or twrp also Now MiFlash tool is not recognising the device.
Click to expand...
Click to collapse
Hmm. What ROM version are you trying to flash on this? If your device isn't recognized by your PC when in fastboot mode, I'm not sure how you'd flash it.
oreo27 said:
Hmm. What ROM version are you trying to flash on this? If your device isn't recognized by your PC when in fastboot mode, I'm not sure how you'd flash it.
Click to expand...
Click to collapse
I flashed Android N Fastboot rom by selecting Clean and lock option.
After that the problem started
MrUsamahh said:
I flashed Android N Fastboot rom by selecting Clean and lock option.
After that the problem started
Click to expand...
Click to collapse
It should boot if you've fully flashed it and cleaned the user data partition. If it still isn't, you'll want to wait for other members with more experience in bricks to chime in.
oreo27 said:
It should boot if you've fully flashed it and cleaned the user data partition. If it still isn't, you'll want to wait for other members with more experience in bricks to chime in.
Click to expand...
Click to collapse
My device is booting up without any problems.
But the problem is bootloader is still unlocked. So i am not able to update via OTA.
And as the device does not holds in fastboot mode so I am not able to do other flash work.
Is there any way I can share a video of my problem with you?
MrUsamahh said:
My device is booting up without any problems.
But the problem is bootloader is still unlocked. So i am not able to update via OTA.
And as the device does not holds in fastboot mode so I am not able to do other flash work.
Is there any way I can share a video of my problem with you?
Click to expand...
Click to collapse
Oh. If it's booting up fine, then you shouldn't be worried too much.
If it keeps restarting in Fastboot mode, it could be a driver issue which is preventing your PC from recognizing your device and vice versa. I'm on Windows 10 which installs drivers automatically so I've never had experience with it.
oreo27 said:
Oh. If it's booting up fine, then you shouldn't be worried too much.
If it keeps restarting in Fastboot mode, it could be a driver issue which is preventing your PC from recognizing your device and vice versa. I'm on Windows 10 which installs drivers automatically so I've never had experience with it.
Click to expand...
Click to collapse
https://photos.app.goo.gl/TyLendNH7XaY74bs1
Please see this video.
If i boot in fastboot mode the device should be in fastboot mode till power button is not pressed for at least 10 seconds.
But in this case it gets switched off.
I have not connected the USB to pc and nothing else.
MrUsamahh said:
https://photos.app.goo.gl/TyLendNH7XaY74bs1
Please see this video.
If i boot in fastboot mode the device should be in fastboot mode till power button is not pressed for at least 10 seconds.
But in this case it gets switched off.
I have not connected the USB to pc and nothing else.
Click to expand...
Click to collapse
I think that's expected behavior? If it doesn't recognize itself being connected to a device, it'll exit fastboot mode.
I think you need to connect it to the USB cable and into your PC for it to not restart/power off.
oreo27 said:
I think that's expected behavior? If it doesn't recognize itself being connected to a device, it'll exit fastboot mode.
I think you need to connect it to the USB cable and into your PC for it to not restart/power off.
Click to expand...
Click to collapse
No when I connect it to pc at that time also same happens.
Previously when booted in fastboot mode it will stay ther by the time juice is out.
MrUsamahh said:
No when I connect it to pc at that time also same happens.
Previously when booted in fastboot mode it will stay ther by the time juice is out.
Click to expand...
Click to collapse
Yup. I just tested it out. It looks like you're right.
oreo27 said:
Yup. I just tested it out. It looks like you're right.
Click to expand...
Click to collapse
So do you know how can I help myself out?
wait.. what exacly did you do when you booted into fastboot? did you type "adb devices" or "fastboot devices"? also, try rebooting into fastboot mode by typing "adb reboot bootloader" in cmd, with your phone plugged into your pc, and with the proper platform-tools installed. it shouldn't really go away from fastboot mode like that.
Mizuru said:
wait.. what exacly did you do when you booted into fastboot? did you type "adb devices" or "fastboot devices"? also, try rebooting into fastboot mode by typing "adb reboot bootloader" in cmd, with your phone plugged into your pc, and with the proper platform-tools installed. it shouldn't really go away from fastboot mode like that.
Click to expand...
Click to collapse
Hy man, I know basic of adb and I use cmd "adb devices"
My device is recognised when it is on.
I can also give various cmd like boot in recovery or fastboot mode or reboot and the device follow the instructions.
Please see the video that I've shared.
Once fastboot mode is on the device is automatically restarted in about 10 to 15 sec and within this time MiFlash tool or adb cmd prompt bot does not recognise my device.
I have tried to flash OTA via adb side load but it is showing error.
Help me with your input!
MrUsamahh said:
Hy man, I know basic of adb and I use cmd "adb devices"
My device is recognised when it is on.
I can also give various cmd like boot in recovery or fastboot mode or reboot and the device follow the instructions.
Please see the video that I've shared.
Once fastboot mode is on the device is automatically restarted in about 10 to 15 sec and within this time MiFlash tool or adb cmd prompt bot does not recognise my device.
I have tried to flash OTA via adb side load but it is showing error.
Help me with your input!
Click to expand...
Click to collapse
Your device doesn't get detected in your CMD prompt when it's in fastboot AND you type "fastboot devices"?
If it doesnt then you might have flashed something incorrectly.
Also, make sure to have your android drivers up to date in your pc. It's very, very likely that you don't have them installed on your PC, or they are outdated. See this: https://developer.android.com/studio/run/oem-usb.html
And this: https://developer.android.com/studio/releases/platform-tools.html
I have faced this issue. Yesterday i dirty flashed a custom rom. but i forgot how to dirty flash. i just simply flashed the rom and restarted the phone. it was mandatory to flash custom recovery and gapps after flashing a rom dirtily or normally. but i didn't. After the reboot completed, i remembered that i didn't flashed the twrp and gapps. So, i go back recovery mod, guessed i could flash twrp now. But i didn't see any custom recovery on my phone. But the phone boots, and i can use the phone. Still, i'm on that phone, while i'm typing this comment. i didn't lost my data cause i flashed dirtily. But the problem is, as i didn't flashed gapps or magisk (for root access), now i can't use google apps like, play store, and more. As i don't have root access on my phone so, i can't run flasify, to flash custom recovery. neither i can run other apps that need root. As i didn't flash custom recovery, now i can't flash gapps, magisk and whatever that needs a custom recovery.
I told some rom porter about the matter. They told me to flash stock rom. So, i was trying to flash stock rom. but flashing stock rom requires a fastboot mode. But my fastboot logo doesn't appear and it's blank. I told this to a rom porter. But he said, He doesn't know about that and he can't help.
I was installing a magisk module when the phone bootlooped, I tried to use fastboot but adb wont recongize it, does anyone know what to do
yellk20 said:
I was installing a magisk module when the phone bootlooped, I tried to use fastboot but adb wont recongize it, does anyone know what to do
Click to expand...
Click to collapse
You're getting you tools messed up...
For fastboot you need to be in the bootloader (vol- and pwr)
rignfool said:
You're getting you tools messed up...
For fastboot you need to be in the bootloader (vol- and pwr)
Click to expand...
Click to collapse
yeah im in the bootloader, my computer will recongize that there is something in fastboot, but adb wont recongize so i cant flash anything
yellk20 said:
yeah im in the bootloader, my computer will recongize that there is something in fastboot, but adb wont recongize so i cant flash anything
Click to expand...
Click to collapse
From fastboot... You could
1) flash the stock kernel, reboot to recovery, and factory reset
2) flash TWRP to boot, reboot to recovery, use adb to push whatever you want to /sdcard/, then flash that
3) download either from the BTS thread or from Essential, a back to stock fastboot flashable
If none of those sound good...
Fastboot flash the stock kernel, reboot to recovery, and sideloadable an OTA from the Essential website...
yellk20 said:
I was installing a magisk module when the phone bootlooped, I tried to use fastboot but adb wont recongize it, does anyone know what to do
Click to expand...
Click to collapse
Update, i sideloaded a image and that seemed to work, but fastboot still wont be recongized
Thank you, but I got it figured out and I re rooted and I installed twrp just in case something goes wrong
howto flash the one without working volume controls??
is this possible?
Yes, it is possible. LineageOS has an option to boot to recovery or fastboot via the standard reboot dialogue.
You can also use adb commands "adb reboot recovery" or "adb reboot fastboot".
kekerosberg said:
Yes, it is possible. LineageOS has an option to boot to recovery or fastboot via the standard reboot dialogue.
You can also use adb commands "adb reboot recovery" or "adb reboot fastboot".
Click to expand...
Click to collapse
thanks for the reply. is there any manual to do so?
for im´m an absolute newbie on this. adb and faastboot are installed on my ubuntu machine.
Depends on what you are trying to accomplish.
Flash TWRP recovery? You may also use LineageOS recovery instead of TWRP if you want. Follow their instructions https://twrp.me/oneplus/oneplusone.html
Flash LineageOS? Follow the wiki instructions https://wiki.lineageos.org/devices/bacon/install
Beware that unlocking the bootloader will erase all data on the phone.
kekerosberg said:
Yes, it is possible. LineageOS has an option to boot to recovery or fastboot via the standard reboot dialogue.
You can also use adb commands "adb reboot recovery" or "adb reboot fastboot".
Click to expand...
Click to collapse
yes i tried but failed because in the last step i had to reboot in recovery with the volume control and start button, because at that point iḿ in fastboot mode and adb reboot recovery won work?!
yes i tried but i failed because in the last step i had to reboot in recovery with the volume control and start button, because at that point i'm in fastboot mode and adb reboot recovery won't work?!
While in fastboot mode, you may boot into recovery using "fastboot reboot recovery". Almost there, good luck!
kekerosberg said:
While in fastboot mode, you may boot into recovery using "fastboot reboot recovery". Almost there, good luck!
Click to expand...
Click to collapse
doesn't work on my ubuntu machine. "unkown rebbot target recvery..
i tried .guess i check it on my win machine.
You can also reboot to recovery from within the OS by using "adb reboot recovery". It should work if you were able to reboot to fastboot using this method.
unfortunately it does not work while being in fastboot mode.
adb says device 'null'not found..
Yes, you are supposed to use adb from whatever OS you have installed, CM, CyanogenOS, LOS, ...
but?
is flashing possible without being in fastboot mode? just using adb?
I understood that you had already flashed the recovery. Now you need to boot into the recovery to flash an OS.
Fastboot is used to flash the recovery.
Recovery is used to flash the OS.
yes i think that's it and therefore i had to reboot to recovery without working controls..
koeskemc said:
yes i think that's it and therefore i had to reboot to recovery without working controls..
Click to expand...
Click to collapse
any idea?
kekerosberg said:
I understood that you had already flashed the recovery. Now you need to boot into the recovery to flash an OS.
Fastboot is used to flash the recovery.
Recovery is used to flash the OS.
Click to expand...
Click to collapse
yes, and that's my prob how to boot into recovery without using any controls?
or is there another way?e.g adb sideload??
You have a working operating system installed? Cyanogenmod, LineageOS or something similar?
Use the power button to boot into the operating system. Then connect the phone to your PC and "adb reboot recovery".
hello again.
i got a new prob. i've istalled twrp(don know how!)
with terp i imstalled lineage 18.1...zip.
but after booting i alwasy get twrp and not the os.
whats my fault
or do ihavr to istall the .img file??instead of.zip?
hello again,
everything's fine so far. i got lineage os on boot up! but how to get back to twrp again to install gapps??