Hey everyone,
A2 lite phone is in bootloop - allegedly (not my phone) "out of nowhere". The user does not do any fancy things like flashing, and this has not been done either.
Phone is on continuous boot loop, and sometimes (really seems randomly), the device starts up in the "no command" mode and stays there for a while. I read that we could go into fastboot mode by pressing "power button and tapping volume up key", but this doesn't do anything.
I've tried this thread: https://www.the***********.com/boot-xiaomi-mi-a2-fastboot-mode-recovery-mode/
But I'm not even getting into fastboot.
I'm almost thinking that the volume buttons are just broken, though from the feedback of the buttons this doesn't seem realistic.
EDIT: ok, now I'm somehow able to get it into fastboot.... sometimes. Now I'm here:
I switched the partition from a to b, but it still goes into bootloop. Then I switched it back to a, still bootloop. Then back to b. Still bootloop! But at least now sometimes I'm able to get into fastboot. No matter what kind of commands I'm typing in the cmd console, after about 10 seconds on the fastboot screen, the phone just reboots.
idk, it looks almost as if both partitions have the bad android 10...
Do you guys have any idea? Please let me know if more info is helpful.
You go into fastboot mode by holding Vol Down + Power button. So try holding Vol Down and Power button at the same time to go into fastboot mode. (Don't tap it)
Go here and grab the image you prefer (latest should do the trick) : https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
Then go ahead and follow this guide here to flash the stock ROM : https://c.mi.com/oc/miuidownload/detail?guide=2
This will wipe the data on the device, but it seems like you have no other option at this point. Cheers.
Thanks! I've tried that now. It starts flashing the device until... after about 10 seconds, the phone reboots from Fastboot mode .
As per this page: https://twrp.me/xiaomi/xiaomimia2lite.html
I've tried to do a recovery via TWRP. If I execute `fastboot boot path/to/twrp.img` then I go from fastboot to TWRP (the teamwin logo), but right after that the phone already reboots.
https://www.xda-developers.com/how-to-install-twrp/ - I don't know if it means anything, but when I execute `adb reboot bootloader`, the console returns `error: no devices/emulators found. If I execute `adb devices`, it does not list my device. However, if I execute `fastboot devices`, my device is listed.
I installed ADB usb drivers, so when I get my phone connected in fastboot, it shows up as Android Bootloader Interfacee in device manager. So not sure what's going on here, but it's all weird.
What I'm facing is very, very similar to https://www.reddit.com/r/Xiaomi/comments/4ltzt9/xiaomi_mi_note_boot_loop_even_in_fastboot/ <-- but that thread is a bit of a dead end (and 3 y/o)...
daize said:
after about 10 seconds, the phone reboots from Fastboot mode .
Click to expand...
Click to collapse
Hmm, it should never do that, maybe it's a hardware issue that we can not fix via Fastboot ?
daize said:
As per this page: https://twrp.me/xiaomi/xiaomimia2lite.html
when I execute `adb reboot bootloader`, the console returns `error: no devices/emulators found. If I execute `adb devices`, it does not list my device. However, if I execute `fastboot devices`, my device is listed.
Click to expand...
Click to collapse
When the device is in Fastboot mode, it will only be recognized as Fastboot. Only when it's properly booted, the device can be recognized in ADB, so no issues there.
I assume your bootloader is already unlocked as you have successfully booted into TWRP. You might try EDL (Emergency Download Mode) flash as a last resort :
Download MiFlash (20160401) from here : https://www.xiaomiflash.com/download/
You're downloading that particular version because it is able to EDL flash on your phone. Install the MiFlash you've downloaded and open it, then put the phone into fastboot mode. Connect it to your PC and use this code to take the phone into EDL mode:
Code:
fastboot oem edl
After you hit enter, you will see the screen turn off and notification LED blinking, this is normal. This means the phone is in EDL mode. Open the MiFlash you've installed (likely in C:\Program Files\Xiaomi\MiPhone) and browse to the ROM location and connect the phone. Choose "Flash All" and start flashing.
After the EDL flash is complete the phone will not reboot. It will stay in EDL mode. You need to disconnect the phone from PC and hold power button (about 10-15 seconds) to boot the phone. If the phone boots properly, you can go into fastboot and connect it to PC, then use:
Code:
fastboot oem lock
to relock your bootloader. Try it and let me know. :fingers-crossed:
Thanks for the continued help!
I've followed your steps - When I run fastboot oem edl, the console returns "... okay [ 0.0202s] finished. total time: 0.022s" and the phone turns to a black screen (no notification led blinking). Then... after a couple of seconds, goes back into the boot loop .
Something maybe to note: every time that my phone starts up, it (1) shows a screen saying "Your device software can'tbe checked for corruption.Please lock the bootloader.", and then slides down to the typical "androidone" white screen before it reboots again.
daize said:
every time that my phone starts up, it (1) shows a screen saying "Your device software can'tbe checked for corruption.Please lock the bootloader.", and then slides down to the typical "androidone" white screen before it reboots again.
Click to expand...
Click to collapse
The screen with the ugly text is normal, since you have an unlocked bootloader, it's there to warn you that the device's software might've been tampered with. On the main subject though, I'm out of ideas. You might try booting the phone by holding Power + Vol Up, which should normally boot into stock recovery or wipe the data on the device. But I'm slowly beginning to think that this might be a hardware issue rather than a software issue that I can help you to fix.
Under normal circumstances, EDL flash is the way to fix any problems you might encounter with the software, that's why it's called the Emergency Download mode. But since we're past that stage, I believe I will not be able to assist you further. Hope you can fix your device my dude/dudette!
If the phone gets out of fastboot mode your phone does not get recognized from your computer. Try to delete fastboot and minimal adb and download the latest version. [https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445]
Open MiFlash, click Driver left on the top and install them.
Set path to the downloaded firmware. Now boot into fastboot, once that is done connect your USB cable to both, computer and phone. If this doesn't work try different USB-Ports and USB-cables. Some work, some don't. This might be the reason for leaving the fastboot mode.
Click refresh and see if your device appears
@marstonpear thanks for your help so far <3 @Cappucinto, thanks for chiming in! What do you mean with this: "Open MiFlash, click Driver left on the top and install them." <-- in MiFlash, I do not see an option to select driver...
@marstonpear thanks for your help so far <3
@Cappucinto, thanks for chiming in! What do you mean with this: "Open MiFlash, click Driver left on the top and install them." <-- in MiFlash, I do not see an option to select driver...
What did change now after installing these drivers: https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445]
I did try some other USB cables. The one I've been trying triggers the windows sound for "new device successfully connected" when I boot the phone up in fastboot, and then of course gives the "device disconnected" sound when the phone then reboots. With another USB cable in this case, windows just states: "USB device not recognized". So it seems like the cable I haven't been using is defect .
I'm unable to use MiFlash at the moment so I can't explain the whole procedure with installing the drivers in MiFlash. But there has to be something like "Install > Drivers" or something. Maybe someone else can help out.
Try to use the working cable again, open a command prompt and type: fastboot devices
Then wait for an answer, post it here and see if the phone reboots again or if it stays in fastboot
daize said:
Hey everyone,
A2 lite phone is in bootloop - allegedly (not my phone) "out of nowhere". The user does not do any fancy things like flashing, and this has not been done either.
Click to expand...
Click to collapse
The response by marstonpear below makes sense.
marstonpear said:
You go into fastboot mode by holding Vol Down + Power button. So try holding Vol Down and Power button at the same time to go into fastboot mode. (Don't tap it)
Click to expand...
Click to collapse
Although u shd consider this link, i tried to arrange it step by step:
https://forum.xda-developers.com/sho...php?p=79365091
Follow the instructions, as dat was how i revived mine. Hopefully it may help u.
Note; wen using twrp, preferably use " twrp - offain "
Miflash tool:
Link 1: https://www.xiaomiflash.com/download/
Preferably use Link 1 & choose either 2016, 2017 or 2018 versions. They come preloaded with the drivers u need
Link2: https://xiaomibuzz.com/downloads/download-xiaomi-mi-firmware-flash-tool-latest-version-2018.html
Lets know how it goes
Cappucinto said:
I'm unable to use MiFlash at the moment so I can't explain the whole procedure with installing the drivers in MiFlash. But there has to be something like "Install > Drivers" or something. Maybe someone else can help out.
Try to use the working cable again, open a command prompt and type: fastboot devices
Then wait for an answer, post it here and see if the phone reboots again or if it stays in fastboot
Click to expand...
Click to collapse
Hey there When I get into fastboot and run `fastboot devices`, a code returns <tab> fastboot.
... and then the phone restarts I'm trying but I guess I'm beyond the stage of being upset, haha.
@agbadino https://forum.xda-developers.com/sho...php?p=79365091 <-- that first link seems to be broken, could you check again? I'd love to try your steps!
daize said:
@agbadino https://forum.xda-developers.com/sho...php?p=79365091 <-- that first link seems to be broken, could you check again? I'd love to try your steps!
Click to expand...
Click to collapse
Sorry bout d previous link. I believe this shd take u directly to the tutorial:
https://forum.xda-developers.com/mi...tboot-mode-t3920925/post79365091#post79365091
remember to use "twrp offain for daisy". It works better than the regular twrp for daisy
It my take and procedure that worked for me at the time. Good luck tho
Thanks! Sadly, when I get to the `fastboot oem edl` step, it fails. I get into fastboot, I quickly enter `fastboot oem edl`. CMD says finished, the screen turns off. I immediately refresh in MiFlash (COM3 is the device), I start flashing. After 4 seconds, the device turns off (windows sound "device disconnected"). The flashing runs for a total of 7-9s says "the operation completed successfully.(0x000000000: cmd <?xml version="1.0" ?><data .. etc etc
So I don't really know what to do if I can't get into EDL mode .
daize said:
Thanks! Sadly, when I get to the `fastboot oem edl` step, it fails. I get into fastboot, I quickly enter `fastboot oem edl`. CMD says finished, the screen turns off. I immediately refresh in MiFlash (COM3 is the device), I start flashing. After 4 seconds, the device turns off (windows sound "device disconnected"). The flashing runs for a total of 7-9s says "the operation completed successfully.(0x000000000: cmd <?xml version="1.0" ?><data .. etc etc
So I don't really know what to do if I can't get into EDL mode .
Click to expand...
Click to collapse
Try getting another chord and try again.
Tried some other cables. Every time I run fastboot oem edl, it keeps saying "finished", and then reboots the phone in about 5 seconds. One time, it said "Catastrophic failure" as "status" for the flashing.
Otherwise, it most often says "The operation completed successfully.(0x00000000: cmd <?xml version="1.0"?><data><patch SECTOR_SIZE_IN_BYTES="512" byte_offset="16" filename="DISK" physical_partition_number="0" size_in_bytes="4" start_sector="NUM_DISC_SECTORS-1." value="CRC32(NM_DISK_SECTORS-1.,92)" what="Update"/></data>)
But then still continues in the bootloop...
Related
Quick background on situation.
I was running CM13 and I still have TWRP 3.0.2-0. I wanted to try out CM14 or some other variant. I went into TWRP Recovery Mode and Advanced WIPED everything except the Internal Storage and MicroSD (this is probably where I messed up?)
Then went to install and navigate to the new rom and gapps on my microsd card. Well TWRP does not see either. It lists both of them but with 0MB and unselectable. I tried two other card, no go (all FAT32). Tried OTG with 3 different thumb drives, same results. The OS is gone and all I get of course is the white ASUS boot screen loop. ADB doesn't see any devices as well (windows device manager see no new devices when I attached the cable or when I list devices).
The only thing I can boot into is TWRP and I have tried everything to access the SD/OTG without success.
So can I assume I have bricked this thing and must go onto the IntelSOC XFStik procedure? and if so, does having a working TWRP on there force me to deviate from the normal unbrick procedure I have see here and on youtube?
Or is it something really easy that I am missing? I am fairly novice (as noted by my current situation), so maybe it's an easy fix?
Any help is appreciated. Thanks.
@Endosmok
You have LP version twrp recovery? , not the mmbl twrp recovery installed ? which ends in 3.0.2.M1 ??
If you do have 3.0.2.0 for LP bootloader which early versions of CM13 used , then you can fastboot flash stock recovery for 4 20 40 196 in bootloader from here....
https://mega.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw
Thanks go to Shakalaca
To get into bootloader -- from Twrp , select reboot , select power off !
Count to ten after switching off.
Press power and vol + , release power when it vibes , release vol+ at asus screen.
Fastboot flash stock recovery for above LP .196 in bootloader , when flashed --- scroll via vol buttons to recovery and hit power. At the dead android , press power and vol+ together for 4 secs , release vol+
You should be in stock recovery now.
Scroll to `update over adb` and select .
adb sideload LP official firmware from asus for LP .196 or .198
If you need help to get thru this step , just ask:good:
Thanks for the response. I am not sure if I have the LP version. It was done back I think in April of last year... I looked around TWRP and I don't see anything except 3.0.2-0 listed.
So still a little confused. This is how i have been navigating so far....
Power button, volume up... I get to the dead robot. There I can see FASTBOOT MODE is in Red, product name, variant, IFWI, Serial #. The rest is either ? or unknown (bootloader version is unknown).
Then at the bottom i can see 'continue the fastboot process' in blue. With the volume rocker i can select, NORMAL BOOT, POWER OFF, RECOVERY MODE and RESTART BOOTLOADER. I have been select Recovery Mode to get into TWRP. Restart Bootloader gets me back to the dead robot. I would assume this is the bootloader. Normal Boot just gives me the white asus splash where it hangs. In TWRP i can see ADVANCED -> ADB Sideload, I can start and it shows starting adb sideload feature with the blue color scrolling. But still when I connect to the computer I get no connection and nothing is listed when i run adb devices.
My TWRP doesn't let me select either the OTG or MicroSD, they show 0MB but are listed. So no way for me to flash via TWRP. I figured if i can get the computer adb to recognize the phone I can try to sideload via there. But so far my device manager doesn't see a thing, not even an unknown device waiting for their proper drivers.
Where am i going wrong?
Endosmok said:
Thanks for the response. I am not sure if I have the LP version. It was done back I think in April of last year... I looked around TWRP and I don't see anything except 3.0.2-0 listed.
So still a little confused. This is how i have been navigating so far....
Power button, volume up... I get to the dead robot. There I can see FASTBOOT MODE is in Red, product name, variant, IFWI, Serial #. The rest is either ? or unknown (bootloader version is unknown).
Then at the bottom i can see 'continue the fastboot process' in blue. With the volume rocker i can select, NORMAL BOOT, POWER OFF, RECOVERY MODE and RESTART BOOTLOADER. I have been select Recovery Mode to get into TWRP. Restart Bootloader gets me back to the dead robot. I would assume this is the bootloader. Normal Boot just gives me the white asus splash where it hangs. In TWRP i can see ADVANCED -> ADB Sideload, I can start and it shows starting adb sideload feature with the blue color scrolling. But still when I connect to the computer I get no connection and nothing is listed when i run adb devices.
My TWRP doesn't let me select either the OTG or MicroSD, they show 0MB but are listed. So no way for me to flash via TWRP. I figured if i can get the computer adb to recognize the phone I can try to sideload via there. But so far my device manager doesn't see a thing, not even an unknown device waiting for their proper drivers.
Where am i going wrong?
Click to expand...
Click to collapse
You have LP bootloader .
Type in bootloader >
fastboot devices
If recognised, fastboot flash , follow my first reply above , adb wont be recognised until stock recovery is flashed and selected.
Please try to follow what as been already advised
It is V important to follow this from above , dont miss this step ;-
To get into bootloader -- from Twrp , select reboot , select power off !
timbernot said:
You have LP bootloader .
Type in bootloader >
fastboot devices
If recognised, fastboot flash , follow my first reply above , adb wont be recognised until stock recovery is flashed and selected.
Please try to follow what as been already advised
It is V important to follow this from above , dont miss this step ;-
To get into bootloader -- from Twrp , select reboot , select power off !
Click to expand...
Click to collapse
Ok... let me get this straight.... before I sound too dumb...
You want me to go into the bootloader from TWRP (using Reboot > Power Off), even though I get to TWRP via the bootloader (recovery mode) from a power on?
Also, how do I know if fastboot is enabled? Is it when I see FASTBOOT MODE in the color red on the bootloader screen with 'continue the fastboot process' at the bottom?
I've done step by step what you wrote and I get to the bootloader but fastboot devices shows nothing (I've tried different computers/cables as well). I have the computer connect to the phone w/ bootloader screen on with what i wrote about FASTBOOT MODE in red and contine the fastboot process. If that is not correct, let me know. I did hold down the Volume Up for a bit longer
I'm almost thinking I have a hardware issue with my phone. I did replace the mic with a new module prior. I never checked if the usb storage was functioning after. Though it charges via the usb (even connected to a computer it charges but not recognized as a device). I'll have to double check that as well.... not sure why the sd card is not recognized though either... never touched that area. Could be the reason why TWRP can't access either the micro sd or otg?
I do appreciate the help... and i have been reading other threads... just seem to be at a stand still for now... suggestions are always welcome.
update: tried adjust the cable on the mic module ... no dice... replaced with older mic module, no dice... don't think it's a hardware issue.
To get into fastboot mode, power off the phone. Press and hold the volume up button and press the volume button. Once the phone vibrates, let go of the power button, then the volume button. You should not be in fastboot mode. You can choose recovery, power off, etc. with the volume button when in fastboot mode.
Connect the phone to the computer. Do you see any Android devices in device manager? Do you see any unknow devices?
Did you open a command prompt window on your computer, connect the phone in fastboot mode, and type "fastboot devices" (without quotation marks) and press enter to see if the phone is recognized?
audit13 said:
To get into fastboot mode, power off the phone. Press and hold the volume up button and press the volume button. Once the phone vibrates, let go of the power button, then the volume button. You should not be in fastboot mode. You can choose recovery, power off, etc. with the volume button when in fastboot mode.
Connect the phone to the computer. Do you see any Android devices in device manager? Do you see any unknow devices?
Did you open a command prompt window on your computer, connect the phone in fastboot mode, and type "fastboot devices" (without quotation marks) and press enter to see if the phone is recognized?
Click to expand...
Click to collapse
So made some progress here. I think it was a hardware issue now... I put back the new mic module and reconnected the cable and now I can see my SD card and the computer sees it as well in adb and fastboot. That's the good news....
But ran into a new issue when trying to install any ROM from my micro sd card. I get ERROR 7 no matter what ROM I try to install. I have verified that they are the proper roms for my Z00A ZE551ML but still a no go.
What steps should I take next if I can now communicate but get error 7?
Thanks
Which recovery are you using to flash and which file are you trying to flash?
I am using TWRP 3.0.2.-0. Using the install from zip. I select any rom (Nougat Based so far I have tried). RR, Lineage, Octopus, all with the same error.
The phone is running a MM bootloader? What about MM or LP based ROMs?
I believe Timbernot said it was an LP based. I believe I installed about April last year and it was 3.0.2-0
Looks exactly like this
https://forum.xda-developers.com/zenfone-2-laser/development/recovery-twrp-3-0-0-0-recovery-t3319704
You probably need an MM bootloader for custom Nougat ROMs. Did you try any LP-based ROMs?
I have not tried any LP based yet. I will try in a bit and forward the results.
Thanks
Post removed. Let's keep things respectful here folks. :good:
And remember, to each their own.
Cheers,
Darth
Senior Moderator
Hello Everyone,
I Have A Strange Problem When I Press Power+Down Button Then Device Goes To Bootloader/Fastboot And Mi Bunny Appears, But After 3-5 Seconds Mobile Device Automatically Switch Off Without Connecting The Cable Or Doing Anything.
Note That, I Have A Latest Build V11.0.9.0.QDLMIXM Installed Without Rooting And Device Working Properly. Since I Just Want To Root The Device And Bootloader Is Unlocked. The Problem Is That Device Doesn't Stay On Bootloader/Fastboot Mode.
Thanks In Advance !!!
Thanks,
MUHAMMAD Asif Qasim
Can you get fastboot to see it in this brief window? I'm wondering if it will stay if it sees fastboot but maybe reboots because it doesn't? (Or because some other app on your PC is confusing it?)
a1291762 said:
Can you get fastboot to see it in this brief window? I'm wondering if it will stay if it sees fastboot but maybe reboots because it doesn't? (Or because some other app on your PC is confusing it?)
Click to expand...
Click to collapse
Thankyou For Prompt Response.
I Couldn't Get Your Point. The Problem Is That Device Doesn't Stay On Bootloader/Fastboot Mode Even I Connect The Cable Or Not. Its Automatically Switch Off With In 3-5 Seconds.
In Addition To That, I Can Use ADB Commands & Shows My Mobile Connectivity When I Use.
Thanks,
MUHAMMAD Asif Qasim
aasiaasi said:
I Couldn't Get Your Point. The Problem Is That Device Doesn't Stay On Bootloader/Fastboot Mode Even I Connect The Cable Or Not. Its Automatically Switch Off With In 3-5 Seconds.
Click to expand...
Click to collapse
I run this on my PC and it waits for a device.
$ fastboot getvar current-slot
< waiting for any device >
3-5 seconds should be enough time to connect your device and see if fastboot can talk to it (and if that stops it from rebooting).
If it happens when there is no cable plugged in... that's a bit more concerning. Does it also happen if you get to fastboot by typing adb reboot bootloader (from a normally-booted system)?
a1291762 said:
I run this on my PC and it waits for a device.
$ fastboot getvar current-slot
< waiting for any device >
3-5 seconds should be enough time to connect your device and see if fastboot can talk to it (and if that stops it from rebooting).
If it happens when there is no cable plugged in... that's a bit more concerning. Does it also happen if you get to fastboot by typing adb reboot bootloader (from a normally-booted system)?
Click to expand...
Click to collapse
Thank You Dear. Yes I Can Use The Command On ADB When Mobile Is Switched On Here Is The Example Snapshot.
The Problem Is That When I Boot To Bootloader It Doesn't Stay On Bootloader And Shutdowns Automatically With In 3-5 Seconds. As You Suggested Me To Check The Command When Mobile Is On Bootloader Mode The Shell Shows "waiting for any device". Ahd Restarts Automatically.
aasiaasi said:
As You Suggested Me To Check The Command When Mobile Is On Bootloader Mode The Shell Shows "waiting for any device". Ahd Restarts Automatically.
Click to expand...
Click to collapse
I don't know exactly what the bootloader does while in fastboot mode, but I'm going to guess it draws the rabbit and then gets ready to talk to the PC. And something fails and it dies.
If it's working normally, that's something... But it's going to stop you from unlocking the bootloader.
I have no idea how to fix. Maybe EDL with the test points? There are 2 aboot partitions (apparently hold fastboot).
# ls -l aboot*
lrwxrwxrwx 1 root root 21 1971-09-16 02:23 aboot_a -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 1971-09-16 02:23 aboot_b -> /dev/block/mmcblk0p32
I think the fastboot mode will exit automatically if it doesn't receive any command from PC. It happened to me before and about the <waiting for any device> when you did a command probably related to it. Check if the driver are properly installed because it happened to me on Windows 10 but not on Windows 8.1.
Mewwo2 said:
I think the fastboot mode will exit automatically if it doesn't receive any command from PC. It happened to me before and about the <waiting for any device> when you did a command probably related to it. Check if the driver are properly installed because it happened to me on Windows 10 but not on Windows 8.1.
Click to expand...
Click to collapse
Thankyou Mewwo2,
Could You Please Check Your Device ? Without Connecting The Cable , That Your Device Automatically Switched Off In Few Seconds Or Not. Please Let Me Know So I Can Figure Out Or Take A Clue For Fixation.
Secondly I Have Windows 8 And Drivers Are Properly Installed. If The Drivers Have Issue The Adb Command Doesn't Work And Doesn't Shows My Mobile (Note That I am Taking About When Mobile Isn't on Bootloader Mode)
Thanks In Advance...
Can you type another adb command like 'fastboot oem device-info' and see the output.
it's not a problem.
Mi a2 lite turns off automatically from fastboot when it doesnt detect any fastboot signal.
You can go to device manager and then see if mi a2 lite gets recognized as a device, now go to cmd and type fastboot devices and boot to fastboot again, now it shouldn't power off again.
minicm94123 said:
it's not a problem.
Mi a2 lite turns off automatically from fastboot when it doesnt detect any fastboot signal.
You can go to device manager and then see if mi a2 lite gets recognized as a device, now go to cmd and type fastboot devices and boot to fastboot again, now it shouldn't power off again.
Click to expand...
Click to collapse
Thankyou For Your Support. I Will Check & Respond Accordingly.
Hey everyone!
So, I've got a HD1903, 8GB RAM 128GB ROM. I updated to OxygenOS 11.0.02, but it was still buggy as hell, so I decided to downgrade. I also had rooted the phone, and decided to get rid of that too. I went to the stock fastboot roms page, downloaded the 10.0.13 ROM and used 'flash-all.bat' file to clear everything. But halfway, it reboots, goes into recovery, then goes to Qualcomm Crashdump mode. That's it. No code or anything, just Qualcomm Crashdump mode, in Blue and Red letters. I tried to hold vol-up, vol-down and power to get into fastboot, but it just loads the fastboot splash screen, then goes back to the same qualcomm crashdump mode screen. Even if i try to hard reset it, by holding vol-up and power, it still goes to the same screen.
Anyone know what to do? I have no idea how to use the 'MSM tool' that everyone talks about, so any guiding advice would be great!
Thanks!
DM me here - https://www.facebook.com/prantor.khan.16 I'll help
HueyT said:
Click to expand...
Click to collapse
I didn't install TWRP, this was all on stock recovery. I also cannot get into fastboot mode.
Msmtool does not need twrp or fastboot--just the software, rom image, drivers, and button combo pushes and holding
OK, so I got it working again, thanks to the advice of reddit users, discord users and the latest msm tool and some googling. I held the vol-up and vol-down buttons for 30 seconds, then connected it to the laptop, with msm running, to a usb 2.0 port, and pressed start. hey presto, it worked. Thanks guys!!
scoped_ar07 said:
Hello
Using the MSM tool is very simple, you just have to download it from this link.
https://drive.google.com/file/d/12y3lO0wIgb2_LSDeVw9x_2C_HjbgZlb_/view?usp=sharing
NOTE: only works on Windows PC
1. Unzip the contents of the RAR into a folder.
2. Run the MSM application
3. Click Start.
4. Connect the cell phone in EDL mode (volume up + down button)
5. Wait for the process to finish (it takes a long time, please be patient)
6. The phone will restart automatically and a message will appear informing you that the equipment is damaged (don't be careful).
Note: The phone should automatically boot into fastboot mode and display a menu, but if it doesn't and instead boots to the T-mobile screen, you need to force shutdown with the power button for several seconds and then manually start it in fastboot mode. (volume up + volume down + power button)
7. Now you need to unlock the bootloader with the command from a Windows CMD window, but you need to download this ADB tool first.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
-Unzip the tool into a folder
-Open a Windows command window, in administrator mode and direct it to the path where you unzipped the ADB tool.
8- Execute this command while the cell phone is connected in Fastboot mode.
fastboot flashing unlock_critical
9- A question will appear on the phone in which you must allow the unlocking.
-With the volume keys select the option to allow it and press the power button.
-At this time your bootloader will be unlocked.
10. Copy the ADB tool files into the folder where ROM 10.0.13 is and replace everything.
11. With the phone connected to the PC, on the command line, run the flash-all.bat file
12. When the phone restarts and the yellow and white letters appear informing that the phone is not safe because the bootloader is unlocked, repeatedly press the (volume down) button until a menu in Chinese appears.
-PC will detect the phone again in fastboot mode and continue to flash
-Leave the phone and PC still until the process is finished.
-In the command line it will indicate that it cannot find files or partitions (ignore it)
13. Finally, the computer will restart automatically and you will be able to use it normally.
Notes:
1. If the phone after the flashing process with MSM starts up and shows the T-mobile logo, don't worry, just turn it off with the power button and connect it in fastboot mode.
2. Do not try to use it with the firmware that I install with MSM, as it will not work properly.
3. Before locking the bootloader again (if you plan to do so) first update via OTA, to the most recent version of Oxygen, otherwise the system will crash again and you will have to repeat the whole process.
Click to expand...
Click to collapse
Stronger1101 said:
Hi
Using the MSM tool is very simple, you just have to download it from this link.
hotdogt_11_O.01_190920 op7t tmo usa patched unlock bootloader.7z
drive.google.com
NOTE: It only works on Windows pc
1. Unzip the contents of the RAR into a
2. Run the MSM application
3. Click Start
4. Connect the cell phone in EDL mode (volume up + volume down button)
5. Wait for the process to finish (it is delayed)
6. A message appears informing that the equipment is damaged, do not be careful.
7- Now you must unlock the bootloader with a command from a windows CMD window, but first you must download this ADB tool.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
-Unzip the tool into a folder
-Open a windows command window, in administrator mode and direct it to the path where you unzipped the ADB tool.
8. Now run this command while the cell phone is connected in Fastboot mode.
fastboo ...
Hi
Using the MSM tool is very simple, you just have to download it from this link.
https://drive.google.com/file/d/12y3lO0wIgb2_LSDeVw9x_2C_HjbgZlb_/view?usp=sharing
NOTE: Only works on Windows PC
1. Unzip the contents of the RAR into a folder
2. Run the MSM application
3. Click Start
4. Connect the cell phone in EDL mode (volume up + volume down button)
5. Wait for the process to finish (it's time consuming, be patient)
6. The phone will restart automatically and a message will appear informing you that the equipment is damaged (don't be careful).
Note: The phone should automatically start in fastboot mode and show a menu, but if it doesn't and instead starts on the T-mobile screen, you must force shutdown with the power button for several seconds and then manually start it in fastboot mode. (volume up + volume down + power button)
7. Now you must unlock the bootloader with command from a windows CMD window, but first you must download this ADB tool.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
-Unzip the tool into a folder
-Open a windows command window, in administrator mode and direct it to the path where you unzipped the ADB tool.
8- Execute this command while the cell phone is connected in Fastboot mode.
fastboot flashing unlock_critical
9- A question will appear on the phone in which you must allow the unlocking.
-With the volume keys select the option to allow it and press the power button.
-At this moment your bootloader will be unlocked.
10. Copy the ADB tool files into the folder where ROM 10.0.13 is and replace everything.
11. With the phone connected to the PC, in the command line, run the file flash-all.bat
12. When the phone restarts and the yellow and white letters appear informing that the phone is unsafe due to having the bootloader unlocked, repeatedly press the (volume down) button until a menu in Chinese appears.
-The PC will detect the phone again in fastboot mode, and continue flashing
-Leave the phone and the pc still until the process is finished.
-In the command line it will indicate that it cannot find files or partitions (don't pay attention)
13. Finally the equipment will restart automatically and you will be able to use it normally.
Notes:
1. If the phone after the flashing process with MSM starts up and shows the T-mobile logo, don't worry, just force it off with the power button and connect it in fastboot mode.
2. Do not try to use it with the firmware that I install with MSM, as it will not work properly.
3. Before blocking the bootloader again (if you plan to do it) first update via OTA, to the most recent version of Oxygen, otherwise it will crash the system again and you will have to repeat the whole process.
Click to expand...
Click to collapse
Oh wow that was a long and well defined post. Thank you for taking the time to type it out.
As it happens, I fixed my issue already (IDK if there's a solved flair for XDA or something?). I downloaded the latest (10.0.15) MSM Tool from the XDA page, held the vol-up and vol-down for 30 seconds this time (as per advice from discord users) got the phone into edl mode, connected to a usb 2.0 port and let msm tool do it's thing. Everything is working perfectly now.
I've got the same problem but even with holding vol up+down buttons for 30 seconds I can't get into edl mode. It boots into qualcomm crashdump mode. I don't have fastboot working, I only see fastboot splash screen for a sec and then qualcomm crashdump mode appears. Could someone help?! As soon as usb cable is connected phone boots into qualcomm crashdump mode. no matter what I do.
Also do service centers undertake servicing for such phones which bricked because of badly flashed roms.
Āryan-9909 said:
Also do service centers undertake servicing for such phones which bricked because of badly flashed roms.
Click to expand...
Click to collapse
Yes, theyll just change out the motherboard
HueyT said:
Yes, theyll just change out the motherboard
Click to expand...
Click to collapse
If they're going to just change the motherboard, I wonder what the EDL mode is meant for. Anyways, I won't go for motherboard change one can buy a new and better phone at that kinda price.
Anyways, I Fixed it through EDL method, you have to hold vol up and down simultaneously and immediately connect to windows (while still holding both buttons) via original USB cable. Check with Device manager if your device shows up, it's easy enough but you might have to keep trying to you get it right. Thereafter, disable driver verification in windows and if Sahara communications failed message appears in msm tool, turn off phone and repeat the procedure again.
The repair peeps only fix hardware and not software. It's more cost effective for them to swap out hardware faster than messing with msmtool like us
Āryan-9909 said:
I've got the same problem but even with holding vol up+down buttons for 30 seconds I can't get into edl mode. It boots into qualcomm crashdump mode. I don't have fastboot working, I only see fastboot splash screen for a sec and then qualcomm crashdump mode appears. Could someone help?! As soon as usb cable is connected phone boots into qualcomm crashdump mode. no matter what I do.
Click to expand...
Click to collapse
OK, so you won't get any confirmation that you're in EDL modem you just have to wing it. What I did, I first opened the MSM tool on my laptop, connected the USB side to the laptop at a USB 2.0 port, and kept the USB-C side within easy reach. I held the buttons down with one thumb for 30-35 seconds, and while still holding them down with one hand, i connected the cable to the phone and clicked enum in MSM, it showed connected so I let the buttons go, and it didn't restart. I clicked start, and it worked for me.
scoped_ar07 said:
OK, so you won't get any confirmation that you're in EDL modem you just have to wing it. What I did, I first opened the MSM tool on my laptop, connected the USB side to the laptop at a USB 2.0 port, and kept the USB-C side within easy reach. I held the buttons down with one thumb for 30-35 seconds, and while still holding them down with one hand, i connected the cable to the phone and clicked enum in MSM, it showed connected so I let the buttons go, and it didn't restart. I clicked start, and it worked for me.
Click to expand...
Click to collapse
You don't have to hold buttons for that long, you can immediately connect it to PC. There is usually a sound to indicate that a new device has been connected to windows, you can also keep device manager open for confirmation. This video really helped.
After receiving a " qualcomm crash dump" , I was able to boot into recovery. Then I had done a factory reset.
Phone turns on fine, charges as well.
Although, On my Laptop / Desktop it does not see the phone within MSM, ASs well as ADB, Fastbootd or device manager.
I have the correct drivers downloaded.
Ideas ?
hightech316 said:
After receiving a " qualcomm crash dump" , I was able to boot into recovery. Then I had done a factory reset.
Phone turns on fine, charges as well.
Although, On my Laptop / Desktop it does not see the phone within MSM, ASs well as ADB, Fastbootd or device manager.
I have the correct drivers downloaded.
Ideas ?
Click to expand...
Click to collapse
Qualcomm 9008 drivers too?
HueyT said:
Qualcomm 9008 drivers too?
Click to expand...
Click to collapse
Yes.
I went ahead and ran another factory reset via recovery, no luck.
New cable, another PC?
HueyT said:
New cable, another PC?
Click to expand...
Click to collapse
Tried both, my desktop would always connect, adb, fastboot, etc.
I had just just freshly installed oneplus drivers including qualcomm on my laptop. Device was not recognized before driver installation or after.
Figure id try on my Mac, and linux laptop. no dice.
ADB is enabled.
Here are the drivers that are installed on my PC ( I enabled hidden devices, in order to see them ) These were recognizing prior to " qualcomm crash dump" . Not phone will not even be seen
So, I flashed Derpfest A12 ROM, It boots fine but gets stuck on "getting your Android 12 Ready" screen with the animation. I can access wifi and visiblity options but not settings. I flashed TWRP from the official website to install the recovery. But now when I reboot and press Volume Down, TWRP is stuck on boot animation. So I thought just reset using fastboot and start again and pressed volume up and power button but it does NOT work. I tried the volume buttons again in the rom [i can change volume in the starting screen] and they are working. I can press volume down and power button to reboot into recovery and it works fine but gets stuck. So, I just want to have access to adb or fastboot to reset this phone but neither seems possible. I Cant enable advanced reboot in the starting screen. Fastboot doesnt work. ADB not recognizing as it is a new rom and havent enabled it [i enabled in the previous rom]. Thanks for you Help in Advance!
P.S. I have tinkered POCO F1 fairly so I am not totally new to this scene!
EDIT: Thanks for all the replies! But I solved the problem, Idk how but i got access to fastboot mode after some tries and reflashed everything and now it works, also I use linux and the adb drivers and fastboot were in repos so it was easy.
hello,
I am a novice and use a translation tool to write to you (sorry if there are errors...).
Ok I already installed roms (but a long time ago on a OnePlus One...
I have an OP5T, I want to install lineage Os 19.1 on it.
I followed the tutorial on the lineage wiki.
I installed ADB and fastboot well, as well as universal adb driver.
I'm on windows 11, it works.
I enabled debug mode
The adb reboot bootloader command works, so the tel is well seen by the pc and the tel restarts in fastboot mode.
Then nothing, no command (oem unlock) works, the computer does not seem to see such after restarting in fastboot mode.
I read some topic on the net that say that the phone must be in "battery charging" mode and not "file transfer". Me to be visible by adb I have to put it in file transfer mode, otherwise it is not seen.
If I put in recharge mode, same thing to do.
Do you have a tip or should I give up?
ezivoco_163 said:
The adb reboot bootloader command works, so the tel is well seen by the pc and the tel restarts in fastboot mode.
Then nothing, no command (oem unlock) works, the computer does not seem to see such after restarting in fastboot mode.
I read some topic on the net that say that the phone must be in "battery charging" mode and not "file transfer". Me to be visible by adb I have to put it in file transfer mode, otherwise it is not seen.
If I put in recharge mode, same thing to do.
Do you have a tip or should I give up?
Click to expand...
Click to collapse
You need to install not just the adb drivers, but the fastboot ones as well, see this guide for example. This driver is the one needed for fastboot.
My devices have always been in file transfer mode btw, I've never heard of it needing to be in charging mode only.
No, you don't have to be in "charging only" vs "data transfer".
Still, those of us who distain to be plebian keep our devices in "charging only" (with ADB on) as MTP is beneath our contempt.
(Actually, the problem is that the USB VID/PID sometimes changes with each mode and that you may not have a driver loaded for ADB only.)
Nimueh said:
You need to install not just the adb drivers, but the fastboot ones as well, see this guide for example. This driver is the one needed for fastboot.
My devices have always been in file transfer mode btw, I've never heard of it needing to be in charging mode only.
Click to expand...
Click to collapse
Renate said:
No, you don't have to be in "charging only" vs "data transfer".
Still, those of us who distain to be plebian keep our devices in "charging only" (with ADB on) as MTP is beneath our contempt.
(Actually, the problem is that the USB VID/PID sometimes changes with each mode and that you may not have a driver loaded for ADB only.)
Click to expand...
Click to collapse
ok thanks, i a going to try this
Hello @All,
I bought myself a new toy: a bricked Nexus 5x. The only thing I can do is enter the bootloader mode. Otherwise the phone is showing the Google logo.
In bootloader mode the last two lines are "Secure Boot - Enabled" and "Device State - Locked". The "fastboot devices" states that the device is present.
I can neither access any recovery nor install one (because bootloader locked). The device isn't rooted. Parallel to posting this I am searching the depths of the web. Of course without a solution.
Can I do anything else?
hmm, did you try going into the recovery and resseting it, if that didnt work go on your computer, go to bootloader mode, and on your computer try typing: fastboot flashing unlock or fastboot oem unlock, if none of those work, then try reflashing the firmware trough recovery or fastboot, here is the rom for adb sideload trough recovery...
here is a direct download cuz it wouldnt post the zip https://dl.google.com/dl/android/aosp//bullhead-ota-mhc19q-8fe67a2b.zip
I can't access the recovery, but I'll try fastboot again. "fastboot flashing unlock" and "fastboot oem unlock" don't work. I get a " FAILED (remote: 'oem unlock is not allowed')" message.
ok, try this, go in fastboot, and run this command, fastboot flash boot N2G47Z_4Cores.img with the img that i send you, if it works, then see if iit boots up!
it doesnt wanna send it, heres a link to download it https://www.dropbox.com/s/tm7qt98r6d7q2a6/N2G47Z_4Cores.img?dl=0
I tried
Code:
$ fastboot flash boot N2G47Z_4Cores.img
and the answer was
Code:
Sending 'boot' (12045 KB) OKAY [ 0.464s]
Writing 'boot' FAILED (remote: 'device is locked. Cannot flash images')
fastboot: error: Command failed
...
But thanks for your effort to help me
Heinz- said:
I tried
Code:
$ fastboot flash boot N2G47Z_4Cores.img
and the answer was
Code:
Sending 'boot' (12045 KB) OKAY [ 0.464s]
Writing 'boot' FAILED (remote: 'device is locked. Cannot flash images')
fastboot: error: Command failed
...
But thanks for your effort to help me
Click to expand...
Click to collapse
hey is there a way you can send me a video of what happens when it boots up and when you try to enter recovery, maybe i can still help.
if you cant here send it to my mail [email protected] , this is my mail since 2016 and zombie was mostly for minecraft . but then i was young, so yeah.
I can only describe it for you...
When I try to boot into recovery it happens the same as booting the system. The Google sign appears with a short buzz of the vibration motor, then disappears after 16 seconds, and a second later the same again. A classical boot loop. I can only access the bootloader mode. When I try to boot from there, the same happens. The "system state" is locked, and Secure Boot is enabled.
I can power off the device from the bootloader, then it stays off.
Is there any hope to bring it to life again, or is it a brick forever?
Heinz- said:
I can only describe it for you...
When I try to boot into recovery it happens the same as booting the system. The Google sign appears with a short buzz of the vibration motor, then disappears after 16 seconds, and a second later the same again. A classical boot loop. I can only access the bootloader mode. When I try to boot from there, the same happens. The "system state" is locked, and Secure Boot is enabled.
I can power off the device from the bootloader, then it stays off.
Is there any hope to bring it to life again, or is it a brick forever?
Click to expand...
Click to collapse
well it looks like a problem with either the ram, vibrator, or the partitions, sadly this happened with old nexus devices, so its a brick forever sadly. but if you want you can sell it online for parts.
Ok then, I hope I can sell the brick. Thank you again for your help, @NikolaTechGuy !
But there's one last hope: This thread, shown to me directly under this answer ("Similar threads") that I'm currently writing. One last try...
Heinz- said:
Ok then, I hope I can sell the brick. Thank you again for your help, @NikolaTechGuy !
But there's one last hope: This thread, shown to me directly under this answer ("Similar threads") that I'm currently writing. One last try...
Click to expand...
Click to collapse
Sorry if this is too late but are you sure you can't do anything with the phone?
To enter Bootloader Mode press and hold Vol Down + Power. You will automatically enter Fastboot Mode. You will see the settings of 'Secure boot' and 'Device State'
Use Vol up and Vol Down to scroll through menu and the Power button to select an option:
Start
Restart bootloader
Recovery Mode
Power Off
If you select Recovery Mode, wait until you see the 'Robot lying down' image and "No command" text appear on screen. Now hold Power button and briefly press the Vol up button. The 'Android Recovery' screen should now appear.
To enter LG 'Download Mode':
Power Off your phone.
Now press the Vol. Up button and hold it
Now Plug your phone into your computer using a USB cable
After a few seconds 'download mode' should appear on your phone screen, followed by a 'Firmware Update' screen.
If it doesn't enter LG Downoad Mode then check in your Windows Device Manager under COM/PORTS. See if you have connected in Qualcomm 9008 EDL (Emergency Download ) Mode. The connection will appear as Qualcomm HS-USB QDLoader 9008. You might have to download the Qualcomm driver for this to work.
If you can get into Recovery Mode or EDL mode you still have options! It depends how much time and effort you want to spend on a 7 year old phone with no sd card option.
You can become 'obsessed' like me, and buy a hot air gun solder rework station to try and reflow the solder under the MSM8992 chip to fix the 'bootloop of death'! NOTE: I have tried it on 3 bricked Nexus 5X and only got a temporary success on one phone - the other two I did a very good job of frying the chip! Mind you I now have alot of spare parts!
I took the Nexus to a repairman who calls himself "Handy-Doc". He told me it was the hardware. He couldn't install anything as well as me. But replacing the motherboard could help. So I ordered a motherboard on AliExpress. This is my last try!
Heinz- said:
I took the Nexus to a repairman who calls himself "Handy-Doc". He told me it was the hardware. He couldn't install anything as well as me. But replacing the motherboard could help. So I ordered a motherboard on AliExpress. This is my last try!
Click to expand...
Click to collapse
You will have to keep us updated. I looked at those motherboards but wasn't sure about them. What version of Android is installed? Do they come with a new IMEI or are they blank? etc. Taking a 5X apart is very straightforward with a couple of simple phone tools. There are plenty of Youtube videos that show you how to do it - it might save you having to pay "handy-Doc"!
No, it doesn't work. I can plugin the phone when it's in "Download Mode" but nothing more happens. After a few seconds the phone tries to boot again. The "Handy Doc" man gave me back the phone without asking for payment.
The motherboard is on its way from China to Germany. This can take several weeks.
Hi
I am sorry if I am posting this at the wrong place.
I bricked my Nexus 5x device flashing DivestOS on it.
I flashed two different LineagOS on this device successfully in the past and the genuine Android when I was rolling it back. It always worked, but not this time.
Trying to roll it back to genuine Android, there were errors that several ".img" was missing in the archive.
I tried to chat with Android developers on Matrix chat and also reported this problem here, on DivestOS forum, but they blame hardware and/or user mistake.
I took it farther to sort the device problem and made it unresponsive, the screen is black and it does not react to anything at all now.
All I needed to know if there is ANY way to bring this device back to life.
I found some "LGFlashTool_2.0.1.6" on one of the old forumes of (2016), but I did not try it, I believe it will not work, and wanted to know from Android developer's oppinion before I try anything else.
Thank you
---Update:
I opened it, unplugged and re-plugged the battery.
Was able to boot it into the fastboot menu.
1. secure boot - enabled
2. device state - unlocked
-Tried to flash the genuine Android (I did it several times and I know it works)
No success!
Please see the terminal screenshot attached for errors.
If you can get into fastboot have you tried flashing TWRP and getting into it again? Then try flashing a lineageOS that you know works.
bjlabuk said:
If you can get into fastboot have you tried flashing TWRP and getting into it again? Then try flashing a lineageOS that you know works.
Click to expand...
Click to collapse
Thanks for reply =).
This is a goot point.
I'll try and post the result here.
Now, not always I can boot it into fastboot menu, sometimes it's totally un-resposive, does not show any sights of life, it can be the battery charge problem (battery was not bad though).
balakarpo said:
Thanks for reply =).
This is a goot point.
I'll try and post the result here.
Now, not always I can boot it into fastboot menu, sometimes it's totally un-resposive, does not show any sights of life, it can be the battery charge problem (battery was not bad though).
Click to expand...
Click to collapse
Yea, looking at the log everything appears to be okay until that last line. Did you use flash-all.bat from the factory image bullhead-opm7.181205.001-factory-5f189d84.zip?