Hey Everyone!
Its not new that there is quite some chaos regarding the fastboot mode on our device. Though some could access it, others could not. All that would happen when I tried to reboot into bootloader was that it would get stuck on the boot logo. Many said that the bootlogo itself was the fastboot mode. However lsusb on my linux term would not recognize anything attached. So I was quite sure there was some issue. Recently when I was having a chat with Nori, I could confirm that the same. It so happens that when he boots into fastboot mode, there appeared a tiny text at the left bottom of the screen would appear saying the device was in fastboot mode.
A little bit of research and experimentation, I figured out that there was an issue in the appsboot image on the Indian version. So, I flashed the Taiwan version of the aboot on my device and VOILA! I had fastboot mode! Here is how you can get it.
BEFORE I GO ANY FURTHER, I MUST WARN YOU THAT THIS IS HIGHLY RISKY IF DONE WRONG! THERE IS A RISK OF HARD BRICKING YOUR DEVICE! AND I AM NOT RESPONSIBLE FOR WHATSOEVER THAT HAPPENS TO YOUR DEVICE.
1) Head over to http://140.115.126.139:808/gplus_e7/E7_0301_v5832_IMG/ or here
2) Download the aboot.img and save it to the root of your sdcard.
3) Open up a terminal emulator or adb shell and type in the following code.
Code:
su
dd if=/sdcard/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
4) Thats it.. Now reboot into bootloader using any rebooter or using adb and you should see something like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(sorry for all the dust.. should have viped it I guess.. well, atleast shows how good the camera is..)
Good Luck!!
hi.
my device goes to fastboot mode but fastboot command is not working on it.. what can be pb..?
\Desktop\GenerelMobile_Elite>fastboot oem unlock
< waiting for device >
pc detects is "Android Composite ADB Interface" in the device manager..
adb reboot-bootloader is working or wol down + power on..device goes to fastboot mode..
but not working on root directory..
Code:
[email protected]_MOBILE:/ # fastboot reboot
fastboot reboot
[B]sh: fastboot: not found[/B]
127|[email protected]_MOBILE:/ #
this should be closed this does not work
gaganpattanayak said:
this should be closed this does not work
Click to expand...
Click to collapse
It works fine for me. Have you followed the instructions properly?
Yes it goes to the screen and then if you give a fastboot command something seems to happen but nothing happens
HI , my phone gionee e7 is in fastboot mode..I dont know how it got into this mode .. can you tell me how to exit from this mode and get the phone started
my fone is stuck on fastboot mode how to get over it ?
Related
I am having this problem. I enter to fastboot mode (with Volume Down+Power Button), but then when I chose recovery mode I get this screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In this case, I have to wait like a minute and it will reboot normally.
It happened to me several times, until once it entered without problems and I was able to root my device. Now I want to flash the AOKP rom, and I got to the same screen over and over.
Does anybody know what could be happening ?
What custom recovery are you using? The quick answer would be that you should just reflash CWM or TWRP.
That screen is showing you that the android is broken. It seems like maybe ROM manager or goomanager or something else didn't do a good job of flashing your custom recovery image.
just start up the N4 to bootloader/flashboot screen
drop your CWM or TWRP file in your fastboot directory (mine is c:\android-SDK\platform-tools\)
run cmd
Then type what's inside the quotes:
"fastboot devices"
[your n4 should be listed]
"fastboot flash recovery [recovery image file name]"
[for me] "fastboot flash recovery recoveryCWM.img"
you should then load up your recovery on the n4 and it should start up properly.
I'd download your recovery image again too since it might be bad.
thehumble1 said:
What custom recovery are you using? The quick answer would be that you should just reflash CWM or TWRP.
That screen is showing you that the android is broken. It seems like maybe ROM manager or goomanager or something else didn't do a good job of flashing your custom recovery image.
just start up the N4 to bootloader/flashboot screen
drop your CWM or TWRP file in your fastboot directory (mine is c:\android-SDK\platform-tools\)
run cmd
Then type what's inside the quotes:
"fastboot devices"
[your n4 should be listed]
"fastboot flash recovery [recovery image file name]"
[for me] "fastboot flash recovery recoveryCWM.img"
you should then load up your recovery on the n4 and it should start up properly.
I'd download your recovery image again too since it might be bad.
Click to expand...
Click to collapse
Thank you very much! That did the job! (I was using CWM).
Hello guys, just wondering if there is a way to reload the factory recovery partition?
I am getting a demigod error and cannot do anything in recovery once I try to restart into it, but the phone when restarted works fine with the factory image.
I tried to load a custom rom and done screwed up
I did make a recovery backup, but I am pretty sure I screwed it as I was trying to copy recovery.img to the phone during some un-bricking troubleshooting.
Thanks
Okay guys, I know I should be doing my own research but I'm stuck.
I found this youtube video:
https://www.youtube.com/watch?v=hQVTc2m6U-I
I've downloaded all of the LG G2 D801 T-Mobile files:
http://downloads.codefi.re/autoprime/LG/LG_G2/D801BK/Stock_Firmware/20a_partitions
I am able to get ADB to recognize my device and I am able to 'send' commands via fastboot BUT my phone doesn't seem to accept them.
I've tried via command line and using SRK tool:
Here is what happens when I try to run the fastboot commands in fastboot mode (UP button + USB plugin)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is what I get when I try to run SRK Tool:
So as you can see from the output, the phone is detected and it seems like the files are in the process of being 'sent' but nothing actually installs.
When I was doing it in command prompt, I let it sit for a few minutes for a few commands and they just sat there at writing.
On the phone itself, this is what it states at this moment:
[500] fastboot mode started
[500]--reset--
[500]--portchange--
[500]--reset--
[500]--portchange--
[500] fastboot: processing commands
[500]fastboot: getvar: partition-type:laf
[500]fastboot: getvar:max-download-size
[500]fastboot: download:00e00000
[500]fastboot: flash:laf
That's all I get on the phone, nothing changes. It just sits there idle.
I am unsure what to do and was wondering if anybody knows how I can fix this?
So I seem to be having some kind of issue with the phone not accepting fastboot commands and/or my computer is not recognizing fastboot.
I did install the ADB/Fastboot installer. I have Java and SDK installed.
When I try to run ADB devices, it identifies the device.
When I try to run fastboot devices, all I get is:
command prompt> fastboot devices
? fastboot
That's all.
Anyone? I am having the same exact problem and have not found a fix yet.
Look at my last reply here: http://forum.xda-developers.com/lg-g2/help/g2-fastboot-mode-t3427770 it may work
Hi All,
I have a ZUK phone with boot loop at CYANOGEN logo
- Power on > ZUK logo > CYANOGEN logo > Reboot
- I can reflash stock ROM (as below image) but it still keeps reboot
- I can come to fastboot mode but cannot see the device with fastboot devices command
Anyone have solution for this case?
Tks in advance
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Use this Chinese ROM, it can work
https://www.androidfilehost.com/?fid=24052804347826528
To change language from Chinese to English: http://www.tech-and-dev.com/2016/06...ing-to-marshmallow-zui-lenovo-zuk-z1.html?m=1
I follow guide to unlock bootloader and flash recovery
in Developer options
- OEM unlocking: ON
- Update Cyanogen recovery: OFF (not found this option on Chinese ROM)
- Android debugging: ON
# UNLOCK BOOTLOADER
Reboot in fastboot mode
- adb reboot bootloader
- fastboot –i 0x2b4c oem device-info (check if bootloader is unlocked or not- If device unlocked = true that means bootloader is unlocked)
- fastboot –i 0x2b4c oem unlock-go (unlock bootloader)
# FLASH TWRP RECOVERY
fastboot flash recovery twr.img
But I fail at this step then I find another way, using QFIL to flash recovery in this link: http://www.tech-and-dev.com/2016/06...ing-to-marshmallow-zui-lenovo-zuk-z1.html?m=1
# ROM
I tried some 7.x or CM 14 ROMs but it repeat bug that I've met at the begining (boot loop) only CM13 (6.x) works: cm-13.0-20160416-NIGHTLY-ham.zip
Flash below ROMs will have boot loop issue
cm-14.1-20161208-NIGHTLY-ham.zip
NucleaRom-V2.1.5-OFFICIAL[7.1.2]-ham-20170716-2114.zip
Anyone knows why? Pls help
ducnv said:
Flash below ROMs will have boot loop issue
cm-14.1-20161208-NIGHTLY-ham.zip
NucleaRom-V2.1.5-OFFICIAL[7.1.2]-ham-20170716-2114.zip
Anyone knows why? Pls help
Click to expand...
Click to collapse
Please tell the Steps performed for flashing the 7.x ROM?
Just download ROM and use TWRP to flash
Hi all , i have installed TWRP and then tried to install lineage 14 to P8 Lite ( ALE-L21 )
i have wipe everything withoud SDcard and boot recovery2.img i was so stupid cuz its my first time in huawei
now i cant get into bootloader using Volume- and Power button i dont know why but before that i was , when i'am trying to flash using fastboot and use that command " fastboot flash recovery *RECVOERY.IMG* fastboot command said
remote : command not allowed for every single command
i tried using dload method also but same nothing show up unless RESCUE MODE Attention please update system again please anyhelp
Bootloader unlocked already and rooted
zainhassan123 said:
Hi all , i have installed TWRP and then tried to install lineage 14 to P8 Lite ( ALE-L21 )
i have wipe everything withoud SDcard and boot recovery2.img i was so stupid cuz its my first time in huawei
now i cant get into bootloader using Volume- and Power button i dont know why but before that i was , when i'am trying to flash using fastboot and use that command " fastboot flash recovery *RECVOERY.IMG* fastboot command said
remote : command not allowed for every single command
i tried using dload method also but same nothing show up unless RESCUE MODE Attention please update system again please anyhelp
Bootloader unlocked already and rooted
Click to expand...
Click to collapse
DEVICE NOW HAS NO RECOVERY OR BOOTLOADER even i , i dont know how is that fixable :|
https://imgur.com/a/dYFWEFi
zainhassan123 said:
DEVICE NOW HAS NO RECOVERY OR BOOTLOADER even i , i dont know how is that fixable :|
Click to expand...
Click to collapse
another one guys , i have touch and more touch and finally i get into FASTBOOT & Rescue mode
and this screenshot of the deep problem in fastboot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://imgur.com/a/dYFWEFi
Hello everyone, I recently installed via twrp 3.5.0.9 the new official V12.0.5.0.QFJEUXM rom from the latest xiaomi eu stable rom (xiaomi.eu_multi_HMK20MI9T_V12.1.2.0.RFJCNXM_v12-11). I just wanted to see how it was, now, I can not install the recovery again to install the xiaomi eu. Someone know how to help me.
It is as if it does not recognize the device when I send it the adb command, although in principle it does.
Thank you first of all.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
viru78 said:
Hello everyone, I recently installed via twrp 3.5.0.9 the new official V12.0.5.0.QFJEUXM rom from the latest xiaomi eu stable rom (xiaomi.eu_multi_HMK20MI9T_V12.1.2.0.RFJCNXM_v12-11). I just wanted to see how it was, now, I can not install the recovery again to install the xiaomi eu. Someone know how to help me.
It is as if it does not recognize the device when I send it the adb command, although in principle it does.
Thank you first of all.View attachment 5294485View attachment 5294487
Click to expand...
Click to collapse
Before flashing, try: fastboot devices
In Developer options, is OEM unlocking and ADB debugging enabled?
If fastboot devices does not recognize device, try another USB cable or uninstall USB drivers and try again
Yes , OEM unlocking and ADB debugging is enabled, and i had tried with original cable and other one. Thanks for your answer i will keep trying.
"Before flashing, try: fastboot devices" it doesn´t work.
Don't type reboot bootloader if you are already in fastboot
Just flash recovery.
Your address is long, try c:\adb\twrp.img
viru78 said:
Yes , OEM unlocking and ADB debugging is enabled, and i had tried with original cable and other one. Thanks for your answer i will keep trying.
"Before flashing, try: fastboot devices" it doesn´t work.
Click to expand...
Click to collapse
Seems that something is wrong with your USB driver on the PC - adb devices works but fastboot devices does not (where Bootloader is unlocked and OEM Unlocking enabled)
Try uninstalling the USB driver(s) on the PC or try another PC
yaro666 said:
Don't type reboot bootloader if you are already in fastboot
Just flash recovery.
Your address is long, try c:\adb\twrp.img
Click to expand...
Click to collapse
Or copy the (twrp) img file right into the ADB folder on the PC, and go with CMD into the ADB folder before running adb/fastboot commands
Then no paths are needed, just like:
fastboot flash recovery twrp.img
But that will not help him as long as fastboot devices fails
I thought about address length, sometimes adb has problem with it, worth a try
fixed, thanks for your answers, the problem was the laptop and drivers, i have had used other pc and install without problems.