fastboot and download mode problem - G4 Q&A, Help & Troubleshooting

Hi
i have a problem with my G4 H815, i can't access fastboot mode even throw adb commands or throw quickboot apk the phone restarts immediately
the same thing with download mode it restart few 3 or 4 seconds after showing download mode screen
anyone can help please
thanks in advance

Same Here... Any Idea ?
I actuallay am in the same situation with my brand new LG G4 H815 that I have just unlocked.
Everytime I try to get access to the fastboot mode, I get confirmation that my bootloader is unlocked (message on screen),then directly to a normal boot, so I can't flash anything.
If anyone has an idea to solve that it would be much appreciated.
smich_ayane said:
Hi
i have a problem with my G4 H815, i can't access fastboot mode even throw adb commands or throw quickboot apk the phone restarts immediately
the same thing with download mode it restart few 3 or 4 seconds after showing download mode screen
anyone can help please
thanks in advance
Click to expand...
Click to collapse

Same thing here. I can only enter fastboot from an adb shell, but today's CM14 update doesn't boot so no ADB shell, now I'm stuck with a phone that can't fastboot.
Moreover, CM14 recovery just displays "erasing' then reboots.

Related

[Q] LG G3 Stuck on fastboot! [FIXED!!!!!]

I was trying to install TWRP on my phone (LS990, ZV8) using flashify app. This didn't work and after I did so, every time I would try to "reboot into recovery" the phone would get stuck and I would need to pull the battery out. I then read somewhere that the fix was to delete the aboot.img and install the kitkat aboot.img . I tried to do that, and afterwards my phone won't boot at all. It gets stuck and screen turns black and the LED flashes. It sometimes gives me an error message about the bootloader I think. If I try to boot into Download mode, it (sometimes) takes me straight into fastboot instead. When I try to run fastboot and type "devices" I either get back nothing or now I get back a "?". Maybe I don't have the proper driver. Please Please help!!!
Upsdate: Ok so I played with the drivers and although I still can't get a response to "fastboot devices" I tried to flash a recovery and I can get response on the phone to some degree. It says "fastboot: getwarartition-type:recovery" but the cmd prompt on the computer says "cannot load recovery.img".
Maybe I just need to try and flash a bootloader or a download mode. Anyone know where I can get an laf for download mode. Or Have any directions?
Please help me!!!
UPDATE: FIXED IT!!!! What I did was use fastboot to load up an laf.img that I was able to download from someone on here (took a lot of searching to find an laf.img). Even though I was unable to flash the laf (tried a bunch of times and it always gave me that "failure to write" error right at the end), I was able to use fastboot to boot up the laf.img that was on my computer and that got the phone into download mode. Bear in mind that I still wouldn't get the serial number back from "fastboot devices" so if you're having this problem and it doesn't give you the serial number back it's ok. Just try to run some fastboot commands and see if you get a response on the phone, that way you'll know if fastboot is working. Anyway, I was then able to restore it via LGFlashtool. So yup, its fixable!
MWGiants said:
I was trying to install TWRP on my phone (LS990, ZV8) using flashify app. This didn't work and after I did so, every time I would try to "reboot into recovery" the phone would get stuck and I would need to pull the battery out. I then read somewhere that the fix was to delete the aboot.img and install the kitkat aboot.img . I tried to do that, and afterwards my phone won't boot at all. It gets stuck and screen turns black and the LED flashes. It sometimes gives me an error message about the bootloader I think. If I try to boot into Download mode, it (sometimes) takes me straight into fastboot instead. When I try to run fastboot and type "devices" I either get back nothing or now I get back a "?". Maybe I don't have the proper driver. Please Please help!!!
Upsdate: Ok so I played with the drivers and although I still can't get a response to "fastboot devices" I tried to flash a recovery and I can get response on the phone to some degree. It says "fastboot: getwarartition-type:recovery" but the cmd prompt on the computer says "cannot load recovery.img".
Maybe I just need to try and flash a bootloader or a download mode. Anyone know where I can get an laf for download mode. Or Have any directions?
Please help me!!!
Click to expand...
Click to collapse
Unfortunately its hard bricked and the repair center will know that you tampered with it. The nature of the LG bootloader makes it so that you cant write or boot any images using fastboot.
What was wrong with your method is, when you downgrade to KitKat android bootloader you have to also downgrade the bootloader, laf and recovery partition or other wise it bricks. You should have downgraded your phone using LG Flash Tool to KitKat and then root and install whatever you wanted
In your case the version mismatch between your aboot, bootloader and laf partition is the reason why it doesnt work
MWGiants said:
I was trying to install TWRP on my phone (LS990, ZV8) using flashify app. This didn't work and after I did so, every time I would try to "reboot into recovery" the phone would get stuck and I would need to pull the battery out. I then read somewhere that the fix was to delete the aboot.img and install the kitkat aboot.img . I tried to do that, and afterwards my phone won't boot at all. It gets stuck and screen turns black and the LED flashes. It sometimes gives me an error message about the bootloader I think. If I try to boot into Download mode, it (sometimes) takes me straight into fastboot instead. When I try to run fastboot and type "devices" I either get back nothing or now I get back a "?". Maybe I don't have the proper driver. Please Please help!!!
Upsdate: Ok so I played with the drivers and although I still can't get a response to "fastboot devices" I tried to flash a recovery and I can get response on the phone to some degree. It says "fastboot: getwarartition-type:recovery" but the cmd prompt on the computer says "cannot load recovery.img".
Maybe I just need to try and flash a bootloader or a download mode. Anyone know where I can get an laf for download mode. Or Have any directions?
Please help me!!!
Click to expand...
Click to collapse
If, as you say, you can enter Download Mode, you could try this Method by @hyelton :- http://forum.xda-developers.com/showthread.php?t=2785089. Any problems ask in that Thread, they will try and Help. GOOD LUCK.......:good:
itsbighead said:
Unfortunately its hard bricked and the repair center will know that you tampered with it. The nature of the LG bootloader makes it so that you cant write or boot any images using fastboot.
What was wrong with your method is, when you downgrade to KitKat android bootloader you have to also downgrade the bootloader, laf and recovery partition or other wise it bricks. You should have downgraded your phone using LG Flash Tool to KitKat and then root and install whatever you wanted
In your case the version mismatch between your aboot, bootloader and laf partition is the reason why it doesnt work
Click to expand...
Click to collapse
OK sir, I fixed it so clearly it was not hard bricked (don't say that if you aren't sure, it would have cost me plenty of money to replace that had I not known better). What I did was use fastboot to load up an laf.img that I was able to download from someone on here. Even though I was unable to flash the laf, I was able to use fastboot to boot up the laf.img that was on my computer and that got the phone into download mode. I was then able to restore it via LGFlashtool. So yup, its fixable!
573v3 said:
If, as you say, you can enter Download Mode, you could try this Method by @hyelton :- http://forum.xda-developers.com/showthread.php?t=2785089. Any problems ask in that Thread, they will try and Help. GOOD LUCK.......:good:
Click to expand...
Click to collapse
Yeah, once I got it into download mode (that was the whole problem, I was stuck in fastboot) I was able to fix it.
MWGiants said:
OK sir, I fixed it so clearly it was not hard bricked (don't say that if you aren't sure, it would have cost me plenty of money to replace that had I not known better). What I did was use fastboot to load up an laf.img that I was able to download from someone on here. Even though I was unable to flash the laf, I was able to use fastboot to boot up the laf.img that was on my computer and that got the phone into download mode. I was then able to restore it via LGFlashtool. So yup, its fixable!
Yeah, once I got it into download mode (that was the whole problem, I was stuck in fastboot) I was able to fix it.
Click to expand...
Click to collapse
congrats. it is good to know it is fixable
That's awesome to hear. It seems that booting the laf partition does not actually work under fastboot mode for D855 variants which is why I thought it wouldn't work for you
Sent from my iPad using Tapatalk
That's great. And what fastboot commands did you use to execute the laf from your computer ?
Verstuurd vanaf mijn HTC One_M8 met Tapatalk
Hakem said:
That's great. And what fastboot commands did you use to execute the laf from your computer ?
Verstuurd vanaf mijn HTC One_M8 met Tapatalk
Click to expand...
Click to collapse
Fastboot boot laf.img
But beware this doesnt work for D855. His LS980 has a unlocked bootloader
Ok thanks
Verstuurd vanaf mijn HTC One_M8 met Tapatalk
MWGiants said:
I was trying to install TWRP on my phone (LS990, ZV8) using flashify app. This didn't work and after I did so, every time I would try to "reboot into recovery" the phone would get stuck and I would need to pull the battery out. I then read somewhere that the fix was to delete the aboot.img and install the kitkat aboot.img . I tried to do that, and afterwards my phone won't boot at all. It gets stuck and screen turns black and the LED flashes. It sometimes gives me an error message about the bootloader I think. If I try to boot into Download mode, it (sometimes) takes me straight into fastboot instead. When I try to run fastboot and type "devices" I either get back nothing or now I get back a "?". Maybe I don't have the proper driver. Please Please help!!!
Upsdate: Ok so I played with the drivers and although I still can't get a response to "fastboot devices" I tried to flash a recovery and I can get response on the phone to some degree. It says "fastboot: getwarartition-type:recovery" but the cmd prompt on the computer says "cannot load recovery.img".
Maybe I just need to try and flash a bootloader or a download mode. Anyone know where I can get an laf for download mode. Or Have any directions?
Please help me!!!
UPDATE: FIXED IT!!!! What I did was use fastboot to load up an laf.img that I was able to download from someone on here (took a lot of searching to find an laf.img). Even though I was unable to flash the laf (tried a bunch of times and it always gave me that "failure to write" error right at the end), I was able to use fastboot to boot up the laf.img that was on my computer and that got the phone into download mode. Bear in mind that I still wouldn't get the serial number back from "fastboot devices" so if you're having this problem and it doesn't give you the serial number back it's ok. Just try to run some fastboot commands and see if you get a response on the phone, that way you'll know if fastboot is working. Anyway, I was then able to restore it via LGFlashtool. So yup, its fixable!
Click to expand...
Click to collapse
Hey bro i m having same issue ! Can you please explain laf.img , i tried twrp.img !
What does 'laf' means
bikrame said:
Hey bro i m having same issue ! Can you please explain laf.img , i tried twrp.img !
What does 'laf' means
Click to expand...
Click to collapse
Hi, sorry for the late reply. I hope you've already fixed it, but if you're still having this problem then let me explain. "laf.img" is the "download mode" partition. The reason you can't use twrp.img (which is a recovery partition image) is because you're "too far gone" so to speak and not even at the point to try and get into recovery. You need to restore download mode first. If you have fastboot properly working (not going to explain that, look it up, there is plenty of info about that on here and other sites), then you can do what I did. (Although from what other people are saying if you have a D855 it will have a locked bootloader and this won't work, I cant tell you about that because I don't have one and haven't played around with one). Anyway, if you have fastboot working properly (read my first post about how it can be working as long as the phone is responsive, even if you don't get back the "devices comman", you may need to play around with the drivers to get this to work) then you need to obtain an laf.img from somwhere. I found a complete set of .img's for my model somewhere (don't remember if it was on this site or somewhere else). It took a lot of searching, but I'm sure you can find one. Once you have that and the working fastboot then run the command "fastboot boot [location of your laf.img]laf.img"
GOOD LUCK!!!
itsbighead said:
That's awesome to hear. It seems that booting the laf partition does not actually work under fastboot mode for D855 variants which is why I thought it wouldn't work for you
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
That's interesting...do you have any idea why that would be? Is it a locked bootloader like someone else mentioned? (I don't know much about the D855 model, never got to play with one). Maybe there is a workaround we can come up with...
itsbighead said:
Unfortunately its hard bricked and the repair center will know that you tampered with it. The nature of the LG bootloader makes it so that you cant write or boot any images using fastboot.
What was wrong with your method is, when you downgrade to KitKat android bootloader you have to also downgrade the bootloader, laf and recovery partition or other wise it bricks. You should have downgraded your phone using LG Flash Tool to KitKat and then root and install whatever you wanted
In your case the version mismatch between your aboot, bootloader and laf partition is the reason why it doesnt work
Click to expand...
Click to collapse
I realized the problem with the mismatched aboot after the fact... ironically it all worked out because after all of this I am now back to the original kitkat and can just root and flash as you said lol.
Complete Fix Guide
http://forum.xda-developers.com/spr...y-download-t3053985/post60106965#post60106965
Can you please post where you got your laf file? I have the same problem :crying:
MWGiants said:
I was trying to install TWRP on my phone (LS990, ZV8) using flashify app. This didn't work and after I did so, every time I would try to "reboot into recovery" the phone would get stuck and I would need to pull the battery out. I then read somewhere that the fix was to delete the aboot.img and install the kitkat aboot.img . I tried to do that, and afterwards my phone won't boot at all. It gets stuck and screen turns black and the LED flashes. It sometimes gives me an error message about the bootloader I think. If I try to boot into Download mode, it (sometimes) takes me straight into fastboot instead. When I try to run fastboot and type "devices" I either get back nothing or now I get back a "?". Maybe I don't have the proper driver. Please Please help!!!
Upsdate: Ok so I played with the drivers and although I still can't get a response to "fastboot devices" I tried to flash a recovery and I can get response on the phone to some degree. It says "fastboot: getwarartition-type:recovery" but the cmd prompt on the computer says "cannot load recovery.img".
Maybe I just need to try and flash a bootloader or a download mode. Anyone know where I can get an laf for download mode. Or Have any directions?
Please help me!!!
UPDATE: FIXED IT!!!! What I did was use fastboot to load up an laf.img that I was able to download from someone on here (took a lot of searching to find an laf.img). Even though I was unable to flash the laf (tried a bunch of times and it always gave me that "failure to write" error right at the end), I was able to use fastboot to boot up the laf.img that was on my computer and that got the phone into download mode. Bear in mind that I still wouldn't get the serial number back from "fastboot devices" so if you're having this problem and it doesn't give you the serial number back it's ok. Just try to run some fastboot commands and see if you get a response on the phone, that way you'll know if fastboot is working. Anyway, I was then able to restore it via LGFlashtool. So yup, its fixable!
Click to expand...
Click to collapse
can you please help. adb shows my device and fastboot wont. when i type in fastboot devices it doesnt show anything. tried to run commands but it always gets stuck on waiting for device..
MWGiants said:
(Although from what other people are saying if you have a D855 it will have a locked bootloader and this won't work,
Click to expand...
Click to collapse
What to do with D855 than, my friend have D855 and it's stcked in fastboot mode, doesn't allow to flash anything?
lg g3 f410 stuck at fastboot
i tried the solution it didnot work. phone accepts the cmds but remain stuck at fastboot any other method?

Help...Stuck on [780] fastboot mode started [fixed]

I just want to root my D838HK and may be i use a wrong img? not sure ( i use the LG G3 V20x_Root with TWRP recovery)
Now my phone stuck on [780] fastboot mode started.......brababa and cannot turn on
Also, cannot go into download mode for KDZ update
and cannot go to 3rd party recovery by pressing vol- + power *2...after pressing hard rest , it still show [780] fastboot mode started.
Then I try fastboot method, but it only show wait for the device and not going on, I go to device manager to see driver problem or not, it has only CMCC Composite ADB Interface driver installed.
WHats should I do now?
FInally problem fixed, I found the fastboot can use suddently and I fastboot aboot / boot / recovery & laf.img extracted from D858HK20d.kdz
and it reboot as normal now...
jc917 said:
FInally problem fixed, I found the fastboot can use suddently and I fastboot aboot / boot / recovery & laf.img extracted from D858HK20d.kdz
and it reboot as normal now...
Click to expand...
Click to collapse
Can you please explain step by step how you did it? I am a complete newbie and i have the same problem you had
thank you very much in advance

Lg g4 h815 suck in fastboot mode

Hello,
My H815 phone is stuck in fastboot mode.
Whenever i press the power key the phone goes directly into fastboot mode.
I wanted to reset the phone using the phone's menu but straight after that the phone booted directly in fastboot mode and it's now stucked.
I believe that the bottery should be dead as well.
The host has it's bootloader uncloked, however i cannot install TWRP as i receive a message command: unknow in ADB when i try to install the recoevery.
I tried different USB cables and different ports of the same |laptop, currently runnin windows 7 with all the drivers.
Looking for are feedback on how to install the recovery and get rid of the command:unknown error
gogobaba said:
Hello,
My H815 phone is stuck in fastboot mode.
Whenever i press the power key the phone goes directly into fastboot mode.
I wanted to reset the phone using the phone's menu but straight after that the phone booted directly in fastboot mode and it's now stucked.
I believe that the bottery should be dead as well.
The host has it's bootloader uncloked, however i cannot install TWRP as i receive a message command: unknow in ADB when i try to install the recoevery.
I tried different USB cables and different ports of the same |laptop, currently runnin windows 7 with all the drivers.
Looking for are feedback on how to install the recovery and get rid of the command:unknown error
Click to expand...
Click to collapse
Search for FWUL from Steadfasterx.
download-> flash->connect-> open Comannd-> type "fastboot flash recovery recovery.img" or "fastboot reboot system"
Which command are you using for installing TWRP in ADB?

Can't get Lg G7 into Download Mode

Here is some background.
I ordered an LG G7 ULM off of ebay a few days ago. When I got it, I noticed that it was an LG G7 Sprint that was converted to ULM. (Which is typical of eBay). I decided to flash the latest ULM firmware to the device by downloading the latest kdz and flashing with LGup. What I didn't realize until later is that I flashed the "Brightpoint" ULM version. Knowing this, I wanted to flash the non Brightpoint version, but when I try getting into download mode, it doesn't work. It only shows the G7 logo, then shows the battery charging symbol.
Additionally, I am in USB debugging mode and have OEM unlock on in developer options.
Things I have tried:
Holding volume up and then plugging USB
Holding volume down and plugging in USB
Holding volume up and power button
Holding volume down and power button
Reboot fastboot via adb
Also, when i try using LGup without download mode it gives and error "spc code does not match"
Does anyone know how to fix this?
https://forum.xda-developers.com/lg-g7-thinq/how-to/cross-flash-oreo-pie-firmwares-lg-g7-g7-t3915303
If you try ti flash when phone is not in download mode you get "spc code does not match" error.
First method is correct
"Holding volume up and then plugging USB" If that doesn't work try adb reboot download (I don't think there is download option with fastboot command or not supported by LG G7)
If you have ADB installed,connect phone with USB cable
1)Check your phone is listed in with command
Adb devices
2) then run this command
adb reboot download
sampal said:
If you try ti flash when phone is not in download mode you get "spc code does not match" error.
First method is correct
"Holding volume up and then plugging USB" If that doesn't work try adb reboot download (I don't think there is download option with fastboot command or not supported by LG G7)
If you have ADB installed,connect phone with USB cable
1)Check your phone is listed in with command
Adb devices
2) then run this command
adb reboot download
Click to expand...
Click to collapse
1. Adb devices shows my device.
2. I tried the adb reboot download. It just reboots normally. Shows lg logo then my phone is booted up.
None of the fastboot commands word because I can't get into download mode.
onenite said:
1. Adb devices shows my device.
2. I tried the adb reboot download. It just reboots normally. Shows lg logo then my phone is booted up.
None of the fastboot commands word because I can't get into download mode.
Click to expand...
Click to collapse
If you have one of the models with OEM unlock inside the developer menu, you're wasting your time because it does nothing. I don't even know why it's there because the LG G7 ThinQ does not have fastboot mode baked in.
Try running a fastboot command and you will see. You have to get past the bootloader to access anyting to do a root and this is not possible on most of the phones here . Also you do not run these commands from download mode I don't believe, they would usually be done when in fastboot or recovery mode.
The only mode you're probably going to get into is download mode. It would be for manually upgrading firmware. You can go into that mode by holding power and Volume +. I tried for three days straight until I stumbled upon another Canadian who was able to root his phone but he had to use a special box and connectors.
There is no fastboot or recovery. All you can find is download mode and safe boot. I wish you the best of luck but if you have the same variant that I do and most of Canada does if it was purchased here then you will not be able to access fastboot because it does not exist. Don't take my word for it though, do your research and you will see I am speaking the truth. Or you can kill yourself and rip out your hair trying to get fastboot to to load but you will not succeed in doing anything but ending up bald. Luckily I shave my head or else I would have done that. Good luck on your research and if you should get fastboot to do anyting please post it in here for everyone to see so we can praise you and root our own phones also. Cheers my friend.
I didn't read back deeply but it sounds like you're attempting what I did, and use modded boot.img files to further gain access to what we need to root the phone. This is true as for what we need to do, but most who have flashed these images have either ruin their devices totally or had to reflash stock firmware. There were a few that got lucky and let's talk firmware fixed the issue but most phones that broke are probably in a landfill now. Please do share if you succeed in anyting we haven't already tried. I tried flashing to a firmware that does have fast boot capability but it did not work because fastboot is built into the phones and the firmware for any particular country has no effect on whether you can root your phone or not. Just before this I mentioned the boot.img method and I'm guessing the command you are running is something like fastboot flashroot_a boot.img and then typing the same command a second time but only with a letter b instead of an a. This method will not work either so please share if you discover a third method that no one else has discovered yet. I would donate money to you because you would basically be the developer of the root method that actually works.
TWiiTCH said:
If you have one of the models with OEM unlock inside the developer menu, you're wasting your time because it does nothing. I don't even know why it's there because the LG G7 ThinQ does not have fastboot mode baked in.
Try running a fastboot command and you will see. You have to get past the bootloader to access anyting to do a root and this is not possible on most of the phones here . Also you do not run these commands from download mode I don't believe, they would usually be done when in fastboot or recovery mode.
The only mode you're probably going to get into is download mode. It would be for manually upgrading firmware. You can go into that mode by holding power and Volume +. I tried for three days straight until I stumbled upon another Canadian who was able to root his phone but he had to use a special box and connectors.
There is no fastboot or recovery. All you can find is download mode and safe boot. I wish you the best of luck but if you have the same variant that I do and most of Canada does if it was purchased here then you will not be able to access fastboot because it does not exist. Don't take my word for it though, do your research and you will see I am speaking the truth. Or you can kill yourself and rip out your hair trying to get fastboot to to load but you will not succeed in doing anything but ending up bald. Luckily I shave my head or else I would have done that. Good luck on your research and if you should get fastboot to do anyting please post it in here for everyone to see so we can praise you and root our own phones also. Cheers my friend.
I didn't read back deeply but it sounds like you're attempting what I did, and use modded boot.img files to further gain access to what we need to root the phone. This is true as for what we need to do, but most who have flashed these images have either ruin their devices totally or had to reflash stock firmware. There were a few that got lucky and let's talk firmware fixed the issue but most phones that broke are probably in a landfill now. Please do share if you succeed in anyting we haven't already tried. I tried flashing to a firmware that does have fast boot capability but it did not work because fastboot is built into the phones and the firmware for any particular country has no effect on whether you can root your phone or not. Just before this I mentioned the boot.img method and I'm guessing the command you are running is something like fastboot flashroot_a boot.img and then typing the same command a second time but only with a letter b instead of an a. This method will not work either so please share if you discover a third method that no one else has discovered yet. I would donate money to you because you would basically be the developer of the root method that actually works.
Click to expand...
Click to collapse
Thanks for the reply.
I was reading into flashing the laf.img file which would fix the download mode not working, but I'm unable to gain root, so that isn't really an option.
I guess for now, I'm stuck with this firmware version. But, at least I'm on the latest pie version... Hopefully there will be a fix for it, or maybe someone will know how to fix this.
I have heard that you can buy for a service to fix this for around $30. But I don't think I would trust someone doing changes to my phone without a guarantee.
Help me
I have the same problem too, my phone is Verizon variant and I can't get to download mode
babykut said:
I have the same problem too, my phone is Verizon variant and I can't get to download mode
Click to expand...
Click to collapse
OK, I have solved it by myselft, you can use ADB (adb reboot recovery) to restart your phone and then holding volume up key to boot into download mode, hope it work for you
babykut said:
OK, I have solved it by myselft, you can use ADB (adb reboot recovery) to restart your phone and then holding volume up key to boot into download mode, hope it work for you
Click to expand...
Click to collapse
Oh my God, you are a genius. I can't thank you enough.... It worked!!!
onenite said:
Oh my God, you are a genius. I can't thank you enough.... It worked!!!
Click to expand...
Click to collapse
You are welcome
babykut said:
OK, I have solved it by myselft, you can use ADB (adb reboot recovery) to restart your phone and then holding volume up key to boot into download mode, hope it work for you
Click to expand...
Click to collapse
Thank you bro
babykut said:
OK, I have solved it by myselft, you can use ADB (adb reboot recovery) to restart your phone and then holding volume up key to boot into download mode, hope it work for you
Click to expand...
Click to collapse
When exactly do you hit the volume up button?
it doesnt seem to work for me
landonloco said:
When exactly do you hit the volume up button?
it doesnt seem to work for me
Click to expand...
Click to collapse
1) Give "adb reboot recovery" command
2) Press Enter
3) The display's phone shutting down
4) Hold the up volume down until you see the little label "download mode"
It works!
Jengirl said:
1) Give "adb reboot recovery" command
2) Press Enter
3) The display's phone shutting down
4) Hold the up volume down until you see the little label "download mode"
It works!
Click to expand...
Click to collapse
Wuh. It could work, but my question is, HOW THE HELL DID YOU GET YOUR LAPTOP/PC TO DETECT THE CELL PHONE!!!!!!
PD: I Have the same problem, plis help me
Jengirl said:
1) Give "adb reboot recovery" command
2) Press Enter
3) The display's phone shutting down
4) Hold the up volume down until you see the little label "download mode"
It works!
Click to expand...
Click to collapse
it shows no command screen

Fastboot mode Not taking any commands

Hi everyone, I am in a real pickle. I can boot into fastboot mode but when I do so I am not able to flash any recovery img or infact any operations on it only " fastboot devices " gives a positive response, else everything just stucks in command line. So my next step was to use the realme Flash tool. in that too when I click on available devices it shows my phone but after that it just quits the fastboot mode and the phone asks me to press any key to reboot.
Guys please help me if there is any way around it as i have tried everything. Can we reset the bootloader itself using some tool if yes then please let me know
Thanks in advance
katti205 said:
Hi everyone, I am in a real pickle. I can boot into fastboot mode but when I do so I am not able to flash any recovery img or infact any operations on it only " fastboot devices " gives a positive response, else everything just stucks in command line. So my next step was to use the realme Flash tool. in that too when I click on available devices it shows my phone but after that it just quits the fastboot mode and the phone asks me to press any key to reboot.
Guys please help me if there is any way around it as i have tried everything. Can we reset the bootloader itself using some tool if yes then please let me know
Thanks in advance
Click to expand...
Click to collapse
This happened twice with me.
Once, my device driver wasn't properly installed.
Second time I didn't gave cmd permission to access my phone.
Was there a pop up on your phone where it asks you something like "do you want this pc to control your phone"?
use diffrent port

Categories

Resources