Hello,
Recently I flashed a CWM file for 'Lava Iris X1' found on this site for my android 'Lava Iris X1 Grand'. Now my phone is stuck in a bootloop. For some reason i cant enter recovery mode even before my phone was stuck in a bootloop. I am not sure whether my phone has USB debugging enabled or not. I rooted my android with KingRoot before all this happened. I have downloaded your Minimal Adb and Fastboot but it cant find my device.
Overall problem:
1) Phone Stuck in Bootloop
2)USB debugging enabled ? Not sure
3) Can't enter recovery mode
4) ADB wont find my device
Note : When I used Minimal Adb and Fastboot, I typed 'fastboot devices' and some numbers appear:
0123456789ABCDEF devices
but when I used the command 'adb devices' my device is not shown:
List of devices attached
I have a backup at my phone through the Flashify app but since recovery mode cant show I cant recover it. I also need a some flash recovery images.
Please help me out here. I don't know what else to do.
Thank You in advance
Fixed
Nevermind guys, i was able to get my phone out of bootloop using SP Flash Tool.
Now all I have to do is restore IMEI.
Marticco said:
Nevermind guys, i was able to get my phone out of bootloop using SP Flash Tool.
Now all I have to do is restore IMEI.
Click to expand...
Click to collapse
Can you please tell me how did you do that.. i am also in the same situation.
Hi,
I tried flashing Google bootlogo from XDA Ressurection remix thread by using command:
Code:
dd if=/sdcard/logo.bin of=/dev/block/mmcblk0p11
It seemed everything went well and logo was transferred, but when I restarted the phone all I can see is black screen and phone doesn’t boot at all, can’t boot into recovery or fastboot, no matter if I press Power+VOL UP or with VOL DN, any idea how to resolve it? Hard to imagine this command would hard brick device.
I was running rooted CM13.1 from Team Superluminal without any issues, previously I flashed same Google boot logo by using ADB command, but tried to avoid using PC this time after flashing new FW blobs.
EDIT: I can see Qualcomm HS-USB QDLoader 9008 (COM3) in Unspecified devices in W10 64bit.
EDIT 2: apparently mmcblk0p11 is aboot in Mi4C and logo is in mmcblk0p26
tried to flash it through QFIL follwoing these steps
http://www.droidsavvy.com/unbrick-qualcomm-mobiles/
but flashing not successful, sahara protocol could not connect, not sure what else to do, drain battery and hope it will start blinking red and put in fastboot then?
miflash try to read hello packet when flashing fastboot rom but after 5.9s give up with "can not read from port COM3"
You lost your bootloader. Try http://forum.xda-developers.com/showpost.php?p=67725320&postcount=161 to recover your device without reset your device back to MIUI.
already flashed fastboot dev ROM through MiFlash (W10 64bit just switched to non-verified drivers and it found phone after installing qualcomm drivers again), photos for last 2.5 months lost, grr, one time i don't backup longer time end up like this...
Hey,
so, three days ago my Mi4i suddenly turned itself off during the night.
I couldn´t turn it back on, it was stuck on the Cyanogenmod-Logo and wouldn`t go any further.
I couldn´t even enter recovery mode. The only thing I could do was enter Fastboot.
And now Im stuck there.
Tried recovery via Mi PC Suite- it recognised the phone, started recovery, said "finished", but the phone is still in Fastboot.
Same for Mi Flash tool.
Doesn´t matter which ROM i try to flash, I´m still in Fastboot.
Any ideas what I can still try? Or is the phone completely bricked and I need a new one?
Try rebooting by connecting the phone with USB and in CMD running fastboot reboot.
May I know why MIUI did u try flashing on your phone?
If it was Developer ROM. I suggest you to try Global Stable ROMs, This usually fixes everything.
Good luck mate!
Regards,
Sharan
Unfortunately, I did try all that.
Do fastboot commands work? Does your device show up in
fastboot devices?
If yes, Try booting into a recovery using fastboot boot recovery.img
If commands don't work even after you've drivers properly installed(i.e. your PC's fastboot works for other phones), Then I have no idea.
I tried to google, and searched on XDA as well. But I cannot find any thread that clearly explains the difference between the bootloader mode and download mode.
What is the basic difference between them ?
adb reboot bootloader - boots into fastboot mode in my Xiaomi Redmi 3S. Is the fastboot mode same as download mode ? If it is, does that mean adb reboot bootloader and adb reboot download have the same meaning ?
Sometimes across threads, I have read that even the recovery and fastboot mode are same. Though I'm pretty sure they aren't, but could someone please explain how they differ ?
I found a question on android.stackexchange, but couldn't quite understand the answer.
satwick_dash said:
I tried to google, and searched on XDA as well. But I cannot find any thread that clearly explains the difference between the bootloader mode and download mode.
What is the basic difference between them ?
adb reboot bootloader - boots into fastboot mode in my Xiaomi Redmi 3S. Is the fastboot mode same as download mode ? If it is, does that mean adb reboot bootloader and adb reboot download have the same meaning ?
Sometimes across threads, I have read that even the recovery and fastboot mode are same. Though I'm pretty sure they aren't, but could someone please explain how they differ ?
I found a question on android.stackexchange, but couldn't quite understand the answer.
Click to expand...
Click to collapse
Bootloader is code that executed when your operating system starts. Bootloader is a set of instructions that how operating system starts to run apps smoothly.
Download mode, Bootloader mode and fastboot mode are same. Download mode is related to samsung devices. "adb reboot download" command is used for boot samsung device in download mode for flashing purpose.
"adb reboot bootloader" command used for other devices to boot in fastboot mode for flashing.
Recovery mode and fastboot are different.
fastboot mode used for flashing roms.
Recovery mode is used for factory data reset, clear cache, flash official update package(Stock) and can backup and restore whole rom and data, flash mods, custom roms (custom like CWM AND TWRP)
Ashwinrg said:
Bootloader is code that executed when your operating system starts.
Click to expand...
Click to collapse
Do you mean that when the 'device' starts ? Because I read here on xda, that bootloader is before the device boots into 'Android' or 'recovery' .
Also, you said
Ashwinrg; said:
Download mode, Bootloader mode and fastboot mode are same. Download mode is related to samsung devices. "adb reboot download" command is used for boot samsung device in download mode for flashing purpose.
"adb reboot bootloader" command used for other devices to boot in fastboot mode for flashing
Click to expand...
Click to collapse
What happens if I try to flash a Samsung device in 'bootloader' mode ? Or some other device into 'download' mode ?
satwick_dash said:
Do you mean that when the 'device' starts ? Because I read here on xda, that bootloader is before the device boots into 'Android' or 'recovery' .
Also, you said
What happens if I try to flash a Samsung device in 'bootloader' mode ? Or some other device into 'download' mode ?
Click to expand...
Click to collapse
Yes. Bootloader executed before android system starts. It have set of instructions that how system starts and runs operations.
Download mode is only term that uses for Samsung devices and fastboot mode for others. The meaning and purpose of both is same.
satwick_dash said:
I tried to google, and searched on XDA as well. But I cannot find any thread that clearly explains the difference between the bootloader mode and download mode.
What is the basic difference between them ?
adb reboot bootloader - boots into fastboot mode in my Xiaomi Redmi 3S. Is the fastboot mode same as download mode ? If it is, does that mean adb reboot bootloader and adb reboot download have the same meaning ?
Sometimes across threads, I have read that even the recovery and fastboot mode are same. Though I'm pretty sure they aren't, but could someone please explain how they differ ?
I found a question on android.stackexchange, but couldn't quite understand the answer.
Click to expand...
Click to collapse
There is bootloader mode and then there is bootloader.
Bootloader mode is the flashing mode.
Bootloader is the code executed before android system boots.
Some devices boot to a bootloader mode and then have a menu to choose which mode to switch to: fastboot, recovery, etc..
The difference between download mode and fastboot has been explained to you already.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
The bootloader is code that is executed before any Operating System starts to run. Bootloaders basically package the instructions to boot operating system kernel and most of them also have their own debugging or modification environment. Think of the bootloader as a security checkpoint for all those partitions. Because if you’re able to swap out what’s on those partitions, you’re able to break things if you don’t know what you’re doing. So basically it commands the kernel of your device to Boot the Device properly without any issues. So careful with bootloader since it can mess things very badly.
Recovery is defined in simple terms as a source of backup. Whenever your phone firmware is corrupted, the recovery does the job in helping you to restore or repair your faulty or buggy firmware into working condition. It is also used for flashing the Rom’s , kernel and many more things.
Click to expand...
Click to collapse
Download mode is used to flash or `install` update's, full frimwares and custom recoveries generally
Ashwinrg said:
Bootloader is code that executed when your operating system starts. Bootloader is a set of instructions that how operating system starts to run apps smoothly.
Download mode, Bootloader mode and fastboot mode are same. Download mode is related to samsung devices. "adb reboot download" command is used for boot samsung device in download mode for flashing purpose.
"adb reboot bootloader" command used for other devices to boot in fastboot mode for flashing.
Recovery mode and fastboot are different.
fastboot mode used for flashing roms.
Recovery mode is used for factory data reset, clear cache, flash official update package(Stock) and can backup and restore whole rom and data, flash mods, custom roms (custom like CWM AND TWRP)
Click to expand...
Click to collapse
Hi, bro then what is "Qualcomm HS-USB QDloader 9008" mode??
what is the difference between fastboot and Qualcomm HS-USB QDloader 9008"
Sharashchandra said:
Hi, bro then what is "Qualcomm HS-USB QDloader 9008" mode??
what is the difference between fastboot and Qualcomm HS-USB QDloader 9008"
Click to expand...
Click to collapse
The difference is, fastboot mode is the mode designed for flashing the device when fastboot is functioning correctly.
Qhsusb dloader 9008 is when the device has been bricked. The device has to be restored by a specific method when in this state.
Sent from my LGL84VL using Tapatalk
Droidriven said:
The difference is, fastboot mode is the mode designed for flashing the device when fastboot is functioning correctly.
Qhsusb dloader 9008 is when the device has been bricked. The device has to be restored by a specific method when in this state.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Sorry for digging this topic up, but I have a few questions here regarding the Bootloader and the Dloader 9008, so please help to answers if you still follow this thread.
+ For Qualcomm based devices, when in Qloader 9008 ( let's say EDL if I made no mistakes ) then is this true that we can do anything to our devices at this mode? Says, I'm using QPST, and I'm in EDL mode, can I flash a new bootloader to the devices? And if yes, how can I do that?
+ My situation here is a little complicated, one of my ROM testing device, is Xiaomi A1 ( or at least, I think so until few days back ). But then one day, it just bricked when I try to flash a custom ROM, and of course I tried to flash the stock A1 firmware in order to un-brick it. But then, it stays at 900E mode ( Diagnostics mode, not Qloader 9008 ).
Then I had to dig deeper and find out that my device is not actually A1, it's Mi 5X with A1 firm.
Next, I tried to flash 5X firm to bring it back from bricked, but still no luck. Again, I found out that my device is not only 5X, but it's a Tiffany device with Oxygen bootloader ( and worst thing is, it's locked by accident ).
Coming to this point, I'm kind of lost. After reading many articles, try many methods ( lets say my device always in 9008 for the last few days )))) ) but still not able to bring it back from death.
So, if it's anyway to bring it back to life, please help to instructs the process, I have all the tools with me along with about 100GB of firms ( A1, 5X, Mi Max 2, Miui EU....etc ).
Thanks in advance, guys!
hi community
i hope someone is still active in this nubia x section, because i hope for some help.
i flashed twrp to my nubia x with using Minimal ADB and Fastboot.
with twrp i flashed the new rom 3.21.
as i tried also to flash gaps i got in the "your device is corrupt. it can't be trusted and will not boot g.com/abh" error.
but because i still was able to flash files with Minimal ADB and Fastboot i flashed all the *.img files i found in the NX616J-update.zip to the phone.
so i was able to boot the recovery mode and flashed the original rom 3.21 with otg from usb stick.
then the nubia x booted normal to the original rom, but because the playstore wasn't working, i flashed again twrp with Minimal ADB and Fastboot.
in twrp i used all swipe and format functions because i thinked i want clean what i can to start from the beginning.
sorry i dont remeber exactly all the steps i did.
and now my problem is the phone only boot to the fastboot menu.
Minimal ADB and Fastboot seems to still work normal, i can unlock the device and flash twrp.
but after reboot i am still in the fastboot menu.
only boot do edload don't boot to fastboot, and if i boot edload i can connect the phone to my pc and with the qfil-tool i see connect:
"Qualcomm HS-USB QDLoader 9008 (COM4)
But to use qfil to flash i think i need a "MetaBuild Configuration (contents.xml)", and i can't find this file for nubia x.
i hope someone has an idea how i get my phone out of this fastboot-loop and share it here.
thanks and kind regards
hoitschau
i found the solution, thanks to rcsj.
https://forum.xda-developers.com/nubia-x/help/install-rom-stock-3-18-gapps-support-t4108715
flashing the file vbmetaDISABLED.img from the google drive with fastboot was my rescue.