Hi,
Would like some help with a little issue i'm having,
Got a HD1910 model of the phone running the global rom and it seems to be stuck in 'fastboot' mode. Every time the phone reboots or pressing 'start' it will return back to fastboot mode.
Extra details:
It's locked and the developer tools were never enabled.
Occasionally it has shown `qualcomm crash dump mode` with no extra details.
Using this MSM tool it completes successfully but still continues booting into fastboot mode.
All buttons and ports are working.
Using ADB `fastboot reboot` reboots the device but still into fastboot mode
It started to happen after I woke up from installing the latest OTA official oneplus update.
Any help would be appreciated
funnycube said:
Hi,
Would like some help with a little issue i'm having,
Got a HD1910 model of the phone running the global rom and it seems to be stuck in 'fastboot' mode. Every time the phone reboots or pressing 'start' it will return back to fastboot mode.
Extra details:
It's locked and the developer tools were never enabled.
Occasionally it has shown `qualcomm crash dump mode` with no extra details.
Using this MSM tool it completes successfully but still continues booting into fastboot mode.
All buttons and ports are working.
Using ADB `fastboot reboot` reboots the device but still into fastboot mode
It started to happen after I woke up from installing the latest OTA official oneplus update.
Any help would be appreciated
Click to expand...
Click to collapse
Try this might work need to download full ROM
1.Boot into recovery
2.Tap on upgrade from USB
3.Go to your computer and open a command window
"Click Shift and Right click simultaneously"
4. Type the following command
Adb sideload file name.zip
5.Wait for the process to complete
6.Reboot your device
jaythenut said:
Try this might work need to download full ROM
1.Boot into recovery
2.Tap on upgrade from USB
3.Go to your computer and open a command window
"Click Shift and Right click simultaneously"
4. Type the following command
Adb sideload file name.zip
5.Wait for the process to complete
6.Reboot your device
Click to expand...
Click to collapse
Thanks for the reply, but it seems entering into recovery just reboots back into fastboot mode.
Hmm, seems from your description as if your recovery is broken. You could flash a stock recovery in fastboot with the "fastboot flash recovery <filename.img>" command, for download of recoveries you could take a look at this thread and find one suitable for your device/regional version. Once you got a working recovery you can proceed as written above...
Good luck !
s3axel said:
Hmm, seems from your description as if your recovery is broken. You could flash a stock recovery in fastboot with the "fastboot flash recovery <filename.img>" command, for download of recoveries you could take a look at this thread and find one suitable for your device/regional version. Once you got a working recovery you can proceed as written above...
Good luck !
Click to expand...
Click to collapse
Thanks,
But it seems the requirements state it requires a `unlocked bootloader` which mine is not. :/
funnycube said:
Thanks,
But it seems the requirements state it requires a `unlocked bootloader` which mine is not. :/
Click to expand...
Click to collapse
You can try to reboot into stock recovery instead of flash it
"fastboot reboot recovery recovery.img"
And then follow the other steps explained on 2nd post
Related
Dear Community,
I got my Note 3 Pro Snapdragon Version today and I tried unlocking the bootloader, installing root and TWRP.
Unfortunately after I installed TWRP, WiFi didnt work anymore so I wanted to go back to where I was before.
i tried flashing the GlobalRom with the MiFlash Tool but somehow I'm now stuck with a bootloop.
The phone starts up and shows the MI Logo but doesnt go on. I tried booting TWRP temporarily via fastboot commands so that I can try to flash flashable zip files
but it doesnt let me execute "fastboot boot xyz.img" anymore because my device is locked.
I would really love to hear any solutions or ideas. I dont want any root or something anymore. If someone has an idea Im very happy!!!
thanks a lot in advance and tell me if you need any more infos
Paul/shisaya24
1. keep vol + and vol - pressed while connecting USB to enter adb mode
2. check if phone is connected with "adb devices" in command line, if phone shows up, enter "adb reboot edl"
3. now you can flash via MiFlash
Alex3oe said:
1. keep vol + and vol - pressed while connecting USB to enter adb mode
2. check if phone is connected with "adb devices" in command line, if phone shows up, enter "adb reboot edl"
3. now you can flash via MiFlash
Click to expand...
Click to collapse
First of all, HUGE thanks for your fast answer!
Unfortunately I couldnt get this to work. Since I am stuck at the Logog screen here is what I tried:
Pressing both volume buttons while Logo Screen and plugging USB.
Pressing both colume buttons while fastboot screen is up.
These two didnt enter adb mode, I guess because of the bootloop I'm in
I also tried antering recovery mode with volume up + power button. Pressing both volume buttons didnt help either but when I am in recovery like that it shows my device in adb as "sideload" device.
Maybe that helps ? Can you give further advice or am I doomed?
My idea would be: Is it possible to reflash the device completely only usinf fastboot? The only thing I seem to be able to enter is fastboot...
Is there a way from fastboot to "working phone" ?
or maybe through the "adb sideload" state?
thanks a lot in advance!
Paul
EDIT
tried installing via "adb sideload xyz.zip" command but after shortly showing a status bar on phone screen it aborted and said "Total xfer: 0.00x" on PC screen .
Also: I read "adb reboot edl" brings you to download mode so you can flash something. Tried it but the phone just rebooted the normal system, so it stuck on Logo again...
search miui forum for unbrick, there is 2 or 3 method without opening your device
exp: http://en.miui.com/forum.php?mod=viewthread&tid=257227
Unfortunately they all do not work because they always require either a phone in download mode, and i only get to fastboot and adb sideboard or they require flashing something via fastboot but I can't do that either because it says my device is locked if I try...
Any suggestions how to flash a ROM with fastboot only or with adb sideload?
Thanks a lot
Paul
shisaya24 said:
Unfortunately they all do not work because they always require either a phone in download mode, and i only get to fastboot and adb sideboard or they require flashing something via fastboot but I can't do that either because it says my device is locked if I try...
Any suggestions how to flash a ROM with fastboot only or with adb sideload?
Thanks a lot
Paul
Click to expand...
Click to collapse
I Had The Same Issue Brother ! There are only 2 Things which you can do now .
1. Test Point Method to enter EDL
2.Give it to Service Center . I Gave Mine to Service Center ,They Fixed it in 30 mins or less and it was free
Dharani_V said:
I Had The Same Issue Brother ! There are only 2 Things which you can do now .
1. Test Point Method to enter EDL
2.Give it to Service Center . I Gave Mine to Service Center ,They Fixed it in 30 mins or less and it was free
Click to expand...
Click to collapse
Can I do the test point thing myself or is it risky?
What kind of service center? A general mobile phone repair shop or a Xiaomi special one?
shisaya24 said:
First of all, HUGE thanks for your fast answer!
Unfortunately I couldnt get this to work. Since I am stuck at the Logog screen here is what I tried:
Pressing both volume buttons while Logo Screen and plugging USB.
Pressing both colume buttons while fastboot screen is up.
These two didnt enter adb mode, I guess because of the bootloop I'm in
I also tried antering recovery mode with volume up + power button. Pressing both volume buttons didnt help either but when I am in recovery like that it shows my device in adb as "sideload" device.
Maybe that helps ? Can you give further advice or am I doomed?
My idea would be: Is it possible to reflash the device completely only usinf fastboot? The only thing I seem to be able to enter is fastboot...
Is there a way from fastboot to "working phone" ?
or maybe through the "adb sideload" state?
thanks a lot in advance!
Paul
EDIT
tried installing via "adb sideload xyz.zip" command but after shortly showing a status bar on phone screen it aborted and said "Total xfer: 0.00x" on PC screen .
Also: I read "adb reboot edl" brings you to download mode so you can flash something. Tried it but the phone just rebooted the normal system, so it stuck on Logo again...
Click to expand...
Click to collapse
I've been facing the same (or a similar?) problem about a week ago but managed to get out. Knowing me for having a head like a sieve I made some notes, sadly quite rudimentary
Did you try to flash with MiFlash after "adb reboot edl"? If I remember rightly after "adb reboot edl" you got the logo like booting another way, but the light is blinking red. Then I could flash via MiFlash.
I'm quite sure that if you get a "reboot" after entering "adb reboot edl", your phone will be in edl mode.
I will try that this evening when I am at home again and report. Thanks
Alex3oe said:
I've been facing the same (or a similar?) problem about a week ago but managed to get out. Knowing me for having a head like a sieve I made some notes, sadly quite rudimentary
Did you try to flash with MiFlash after "adb reboot edl"? If I remember rightly after "adb reboot edl" you got the logo like booting another way, but the light is blinking red. Then I could flash via MiFlash.
I'm quite sure that if you get a "reboot" after entering "adb reboot edl", your phone will be in edl mode.
Click to expand...
Click to collapse
Unfortunately this doesnt work. Phone reboots and shows MI Logo but red light doesnt blink and MiFlash doesnt recognize any devices.
Do you have another idea? :/
How did you unlock the bootloader, via official permission or that unofficial hack?
Sent from my Moto G using Tapatalk
I didnt use the official way :/ Im so hoping my phone isnt broken. I wish i owuld have been more patient
shisaya24 said:
I didnt use the official way :/ Im so hoping my phone isnt broken. I wish i owuld have been more patient
Click to expand...
Click to collapse
Only options you have right now are:
1) using test points method which is a but cumbersome and voids warranty if you care about that.
2) go to a xiaomi service center of you have any nearby.
It is hard bricked.
So there is absolutely no option to unlock bootlader via adb sideload or fastboot ?
shisaya24 said:
So there is absolutely no option to unlock bootlader via adb sideload or fastboot ?
Click to expand...
Click to collapse
Apparently, no! Whenever using unofficial methods, read precautions carefully and you missed all as I can see. Wait if someone can help you out.
apply official unlock. then unlock your device from fastboot mode.
asaharaSK said:
apply official unlock. then unlock your device from fastboot mode.
Click to expand...
Click to collapse
That sounds nice and easy. I already applied for official unlock.
But: do you know if u can use the official unlock now? I can only access fastboot and adb sideload mode. Is it possible to activate official unlock from there? Or do I need a working ROM rather?
I would have thought that official unlock doesn't work from fastboot /adb sideload...
shisaya24 said:
That sounds nice and easy. I already applied for official unlock.
But: do you know if u can use the official unlock now? I can only access fastboot and adb sideload mode. Is it possible to activate official unlock from there? Or do I need a working ROM rather?
I would have thought that official unlock doesn't work from fastboot /adb sideload...
Click to expand...
Click to collapse
Does anyone know this?
I have the same problem. I made the same mistakes as shisaya24. I have followed every procedure for unbricking and nothing works. I even applied for an unlock code and got it from Xiomi. I used their mi-unlock app which requires fastboot (pwr/vol-) but it gets to 50% and bombs out. It states it can't verify the phone. Can anyone please help me??
smiley1960 said:
I have the same problem. I made the same mistakes as shisaya24. I have followed every procedure for unbricking and nothing works. I even applied for an unlock code and got it from Xiomi. I used their mi-unlock app which requires fastboot (pwr/vol-) but it gets to 50% and bombs out. It states it can't verify the phone. Can anyone please help me??
Click to expand...
Click to collapse
out of sheer desperation I tried MiPhone again and after a few tries, MiPhone started updating the OS. My phone now works again and I have an unlock code as well.
Hello guys,
i have a bricked rooted oneplus x
I had issues with the rooted rom so i flashed the newest stock rom via twrp
The phone boots up and showed the usual otimizing apps message. After the proccess is done it just the usual "let me helpt set up your phone page" and then restarts
I cant acces twrp anymore and when i try to acces the stock recovery it just shows a oneplus logo
I do have access to fastboot though (i hope that leaves some hope)
I have tried the MegaUnbrickGuide here in the forum but i wasn't able to install the drivers i need for that method
One more thing whenever i try
Code:
fastboot boot recovery.img
i get the "remote dtb not found" message
Does that have to do with developer options not being unlocked?
Any ideas on how to just get some form of working os installed on the device
(i dont care wheter rooted or not at this point have been trying stuff for hours now)
regards
Jan
First download Minimal ADB and Fastboot and install it.
Go into fastboot mode.
1. Re-unlock your bootloader using the command - fastboot oem unlock
2. After doing that, download the latest version of TWRP(which at the time of writing this is 3.1.0) and rename it to 'recovery.img'
3. Open a command window in the place you have downloaded the recovery by pressing the shift key and right clicking and then choosing the option Open Command WIndow Here... Flash the recovery using the command fastboot flash recovery recovery.img
4. Boot into it using the command fastboot boot recovery.img
5. If it still gives 'remote dtb not found' then follow this guide: https://forum.xda-developers.com/oneplus-x/help/opx-remote-dtb-solution-t3480274
6. If it boots into recovery, your phone is now fine and go ahead and flash whatever ROM you want.
Cheers!
Hello everyone, this is my first post on the forum.
I have a xiaomi redmi note 4 snapdragon with bootloader unlocked and when I try to install TWRP by ADB it installs it, but when I put the command "flashboot boot twrp.img" it stays in the fastboot logo.
Try using power and volume + to enter the recovery, but enter the original recovery
Can anyone help me? Thank you
Merli- said:
Hello everyone, this is my first post on the forum.
I have a xiaomi redmi note 4 snapdragon with bootloader unlocked and when I try to install TWRP by ADB it installs it, but when I put the command "flashboot boot twrp.img" it stays in the fastboot logo.
Try using power and volume + to enter the recovery, but enter the original recovery
Can anyone help me? Thank you
Click to expand...
Click to collapse
Which output do you get in ADB after you type in the command?
Merli- said:
Hello everyone, this is my first post on the forum.
I have a xiaomi redmi note 4 snapdragon with bootloader unlocked and when I try to install TWRP by ADB it installs it, but when I put the command "flashboot boot twrp.img" it stays in the fastboot logo.
Try using power and volume + to enter the recovery, but enter the original recovery
Can anyone help me? Thank you
Click to expand...
Click to collapse
Could be possible due to old drivers.
Try these platform tools
https://drive.google.com/file/d/13Sjej5zIJPm_yiJQOVR4rEocwbhDc9oh/view?usp=drivesdk
Noter2017 said:
Which output do you get in ADB after you type in the command?
Click to expand...
Click to collapse
downloading 'boot.img'...
OKAY [ 0.792s]
booting...
OKAY [ 0.558s]
finished. total time: 1.353s
After that, it disconnects from the PC and stays in the fastboot logo
MyNameIsRage said:
Could be possible due to old drivers.
Try these platform tools
Try and it does not work, the same thing happens :S
Click to expand...
Click to collapse
MyNameIsRage said:
Could be possible due to old drivers.
Try these platform tools
Click to expand...
Click to collapse
Try and it does not work, the same thing happens :S
Merli- said:
Try and it does not work, the same thing happens :S
Click to expand...
Click to collapse
What process do you follow?
I happened to do it, by copying the recovery file inside the platform tools folder.
Then inside the folder hold shift and right click. It will show an option to open command prompt window or open powershell window here. From there i wrote the commands, fastboot flash recovery recovery.img , and then manually booted to twrp by holding the vol up and power
MyNameIsRage said:
What process do you follow?
I happened to do it, by copying the recovery file inside the platform tools folder.
Then inside the folder hold shift and right click. It will show an option to open command prompt window or open powershell window here. From there i wrote the commands, fastboot flash recovery recovery.img , and then manually booted to twrp by holding the vol up and power
Click to expand...
Click to collapse
I followed that process and it did not work, try two different versions of Twrp and it still did not work. I resigne myself, and try to install the RedWolf recovery with the same process, and this time it works! :fingers-crossed: I could finally install another rom. Thanks for the help
Same problem here, really strange. First time I've this kind of problem.
Edit : Ok, problem solved. There is 2 things to do in addition of the main installation process (found here : https://wiki.lineageos.org/devices/mido/install#installing-a-custom-recovery-using-fastboot )
Firstly, you have to enable OEM Unlocking in Developer option menu. And not only enable USB Debugging. To enable it, click twice on the button "OEM Unlock" (if you click once, it will disable automatically when exiting Dev' menu).
Secondly, once you ran
Code:
fastboot flash recovery twrp-x.x.x-x-mido.img
, you also have to ran
Code:
fastboot boot twrp-x.x.x-x-mido.img
in order to reboot in recovery mode. Otherwise default recovery will automatically erase and replace TWRP.
These 2 steps are quite never documented, but are mandatory for Mido (Redmi Note 4) !!
Skip88 said:
Same problem here, really strange. First time I've this kind of problem.
Click to expand...
Click to collapse
In my case the problem appeared since repair and replace the screen. The unique twrp I could install from ADB was twrp RedWolf
Merli- said:
In my case the problem appeared since repair and replace the screen. The unique twrp I could install from ADB was twrp RedWolf
Click to expand...
Click to collapse
I've edited my post. There is 2 missing steps to be able to install TWRP correctly (then LineageOS^^).
thanks a lot u r a lifesaver.....
Skip88 said:
Same problem here, really strange. First time I've this kind of problem.
Edit : Ok, problem solved. There is 2 things to do in addition of the main installation process (found here : https://wiki.lineageos.org/devices/mido/install#installing-a-custom-recovery-using-fastboot )
Firstly, you have to enable OEM Unlocking in Developer option menu. And not only enable USB Debugging. To enable it, click twice on the button "OEM Unlock" (if you click once, it will disable automatically when exiting Dev' menu).
Secondly, once you ran
Code:
fastboot flash recovery twrp-x.x.x-x-mido.img
, you also have to ran
Code:
fastboot boot twrp-x.x.x-x-mido.img
in order to reboot in recovery mode. Otherwise default recovery will automatically erase and replace TWRP.
These 2 steps are quite never documented, but are mandatory for Mido (Redmi Note 4) !!
Click to expand...
Click to collapse
Thanks a lot u r a lifesaver.....trying it since last 2 days...now finally it worked after i followed ur above mentioned steps...now i just to wait to see if it isnt in bootloop and then i ll check my root status....thanks
Hi:
My unlocked bootloader SS2 phone got stucked in Download Mode after successfully installed/flashed AICP ROM
It booted once and when i rebooted to enter recovery got stucked. Tried pushing buttons combos but still stucked in Dmode.
Have no access to fastboot from Windows but can get limited access to fastboot in Debian: can flash several twrp recoveries, can flash
AICP ROM again but can not get fastboot oem commands working.
Can't enter to recovery because phone never turn off.
Tried also to come back to Nougat but can't enter recovery to flash ss2_old_bootloader.
I do not know what to do.
Any help?
Also have this problem... any help?
have u try to connect into computer, use adb, and use this command :
Code:
fastboot reboot
what's the result with that?
No connection.
But i have reinstalled OST Treble ROM and phone now working.
gsausalito said:
Hi:
My unlocked bootloader SS2 phone got stucked in Download Mode after successfully installed/flashed AICP ROM
It booted once and when i rebooted to enter recovery got stucked. Tried pushing buttons combos but still stucked in Dmode.
Have no access to fastboot from Windows but can get limited access to fastboot in Debian: can flash several twrp recoveries, can flash
AICP ROM again but can not get fastboot oem commands working.
Can't enter to recovery because phone never turn off.
Tried also to come back to Nougat but can't enter recovery to flash ss2_old_bootloader.
I do not know what to do.
Any help?
Click to expand...
Click to collapse
I also have problem after flashing to AICP and sometimes phone (after power off) stuck in Download mode.
Just enter:
fastboot --set-active=a reboot
rgr1 said:
I also have problem after flashing to AICP and sometimes phone (after power off) stuck in Download mode.
Just enter:
fastboot --set-active=a reboot
Click to expand...
Click to collapse
I have the same problem. I tried to follow your advice, but fastboot in my PC doesn't recognize the parameter (all I get is fastboot help page).
Regards.
EDIT: reinstalled treble v3.1 via OST and it fixed the download mode issue.
thanks!
hi,
got the same problem, stuck at download mode but phones can`t to pc via usb so I am unable to use fastreboot.
Any other suggestions how to fix it ?
internety1 said:
hi,
got the same problem, stuck at download mode but phones can`t to pc via usb so I am unable to use fastreboot.
Any other suggestions how to fix it ?
Click to expand...
Click to collapse
in my xperience is connect your phone to the PC then open cmd ... make sure in folder of adb and fastboot .exe stored ...
type:
Code:
fastboot continue
longu said:
I have the same problem. I tried to follow your advice, but fastboot in my PC doesn't recognize the parameter (all I get is fastboot help page).
Regards.
EDIT: reinstalled treble v3.1 via OST and it fixed the download mode issue.
Click to expand...
Click to collapse
Maybe use other fastboot.
Sometimes you must enter:
Code:
fastboot --set-active=_a reboot
("_a" instead of "a")
BTW. My Aquos sometimes stuck in download mode after installing AICP.
I fixed this by entering:
Code:
adb shell
bootctl mark-boot-successful
Hello, i have the same exact problem. I tried to use adb program to fix this problem, but my laptop couldn't recognize my device. Any other solutions would be helpful. Thanks for your attention! (I'm a beginner in technology, so please forgive me)
Hi guys I am having an interested issue,
I want to install custom rom in my phone
I have downloaded in depth test and applied for un depth test
my mobile do connect to computer when it prompt to select mod I do select file transfer and my mobile do connect to laptop
and it shows in "adb devices" but when it goes into bootloader mod my mobile gets disconnected I have done everything I could
I have install every possible driver i got from articles but non worked is it the issue with my windows 10 ? or driver issue I have spent my whole night on this but couldn't find the way
fastboot devices
0purple said:
fastboot devices
Click to expand...
Click to collapse
what does it mean ?
when i connect my phone it prompt me with this and usb debugging is on
i tried adb devices but it didn't showed anything but when i chose transfer file it do connect to the laptop and shows in adb devices
najam489 said:
what does it mean ?
Click to expand...
Click to collapse
Try it once you are in fastboot
wow its showing
najam489 said:
wow its showing
Click to expand...
Click to collapse
0purple said:
Try it once you are in fastboot
Click to expand...
Click to collapse
i have another problem now my device is showing with fastboot devices but my devices status is locked when i tried this command "fastboot flash recovery recovery.img" it didnt work i am follwing this article https://www.guidetoroot.com/root-realme-3-pro/
thank you for your help my bootloader wasn't unlock it is now thanks a lot
It appears your device's bootloader is locked. Try:
fastboot oem unlock
fastboot flashing unlock
If that doesn't help, search for a guide on how to unlock bootloader for your specific brand.
It also looks like don't really know what you are doing. Make sure you are following trusted guide. If no, I'll be happy to help.
0purple said:
It appears your device's bootloader is locked. Try:
fastboot oem unlock
fastboot flashing unlock
If that doesn't help, search for a guide on how to unlock bootloader for your specific brand.
It also looks like don't really know what you are doing. Make sure you are following trusted guide. If no, I'll be happy to help.
Click to expand...
Click to collapse
well i did installed custom roms few time but i dont know much, i did unlock bootloader now the problem is i do install custom recovery twrp and it do installed and rom manager shows that custom recovery is installed but pressing volume down + power button just shows fastboot logo and it restart my phone, and with command "
adb reboot bootloader" i am able to boot into fastboot mood and when i go to recovery from their it open stock recovery instead of twrp
Stolen from my guide:
7. Go into fastboot mode
8. fastboot flash recovery recovery.img
9. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
10. fastboot reboot recovery
12. Sometimes recovery doesn't want to stick as a permanent one. To test it, hold the power button and select "Reboot to recovery". If you reboot to TWRP, you can move on, but if you reboot to stock one, flash recovery using fastboot again and from recovery flash recovery again (sounds crazy, right?). I won't give you instructions on this, research it yourself. Make sure guide you will find is for your device and your recovery.