I downgraded from LineageOS back to stock 6.0 using the files from Prazaar.de and all worked fine. i was able to configure the phone back to my gmail account and calling and everything worked.
to upgrade back to 7.0 i downloaded the blur files from prazaar. i then booted into recovery and sideloaded the first blur file with adb as i have done a few times before. only this time when it was finished, the phone rebooted and the screen stayed black. no matter how often or how long i press the powerbutton with or without volume buttons, nothing happens. when i plug it into windows with a cable though, windows sees a new device Qualcomm HS USB QDloader9008. so it's not all dead.
all guides that talk about unbricking the device at some point need to boot into recovery or at least the bootmenu to start fastboot flashing. but my screen is black and no matter at what point i do a 'fastboot devices' with powerbutton-pressing, it will never show up as a fastboot device.
is there any way to recover from this error or is this phone beyond recovery? how can a phone be this dead after a software update? any help would really really be appreciated as i do still like this phone and am not ready to throw it away yet
If you'd done a little searching you would've found this amazing thread.
https://forum.xda-developers.com/moto-x-style/help/solved-hard-brick-moto-x-style-xt1572-t3693860
Instructions are for the Moto X Style XT1572, but work for the XT1575 too as long as you flash the correct firmware. The issue is caused by updating to Nougat, then downgrading to MM and performing an OTA.
parker.stephens said:
If you'd done a little searching you would've found this amazing thread.
https://forum.xda-developers.com/moto-x-style/help/solved-hard-brick-moto-x-style-xt1572-t3693860
Instructions are for the Moto X Style XT1572, but work for the XT1575 too as long as you flash the correct firmware. The issue is caused by updating to Nougat, then downgrading to MM and performing an OTA.
Click to expand...
Click to collapse
thanks, i've seen that thread, but at the point where i put the sd card in the phone with the loader.img on it and hold the powerbutton, i'm not getting a fastboot screen.. maybe i'm close to getting it to work but so far i dont see anything. any pointers would really be appreciated!
It's really finicky to use. For me, I flashed the loader.img on Windows 7 32-bit and it take multiple (like over a dozen) tries to get it to work. I got really frustrated with it, but after a while it worked. Just make sure that when you are powering on you either need to hold down volume down or volume down and power.
Related
Hi all,
First time posting on here (but I read the forums often - for guides etc).
Bought the Nexus 4 and I unlocked the bootloader and rooted the device. Kept to the stock Android (JB 4.2) however I locked the bootloader again.
The boot loop occurred after a restart after I did the following things:
1. Used Battery Calibration to calibrate the battery. Left the battery to drain and then charge to 100%.
2. Used VM Heap to change the amount and restarted the phone. Boot loop ocurred.
I have tried many things after reading this forums and other forums but there seems to be no answer to this issue.
Things I've tried are:
1. Booted into recovery mode and wipe data/factory reset many times - still has boot loop
2. Used Nexus Root Toolkit and tried the various functions on there. Fastboot doesn't detect the device (even though its in fastboot mode) in order for me to unlock the bootloader again and flash it with the stock ROM. Windows (8) does detect it but can't load drivers for it. Been through all the instructions on the Nexus Root Toolkit - reinstall drivers, cleared the device from device manager, cleared it from usb list etc. Fastboot just won't detect it to allow me to unlock!!
3. Let the battery drained and tried factory resetting but doesn't work (not tried fully charging it and then resetting though)
4. Been trying various other things which I read on the forum(s) but nothing seems to work!:crying:
Literally spent the whole day trying so many different things. Seems like I discovered a whole new unique problem to causing boot loop on the Nexus 4. I don't want to have to send this back to Google for a replacement if they give me one - hopefully with the locked bootloader and the data cleared, they won't know I've rooted, not to mention its micro-sim and my backup feature phone doesn't take micro-sim :crying:
Has any one had this issue before and fixed it!? Would really appreciate the help/guidance!
My first time rooting a phone, didn't do it before on other phones because thought knowing my luck I'd brick it beyond repair! Luck would have it, that exactly what has happened.
Appreciate the replies and help on this!
ThuanBui said:
Hi all,
First time posting on here (but I read the forums often - for guides etc).
Bought the Nexus 4 and I unlocked the bootloader and rooted the device. Kept to the stock Android (JB 4.2) however I locked the bootloader again.
The boot loop occurred after a restart after I did the following things:
1. Used Battery Calibration to calibrate the battery. Left the battery to drain and then charge to 100%.
2. Used VM Heap to change the amount and restarted the phone. Boot loop ocurred.
I have tried many things after reading this forums and other forums but there seems to be no answer to this issue.
Things I've tried are:
1. Booted into recovery mode and wipe data/factory reset many times - still has boot loop
2. Used Nexus Root Toolkit and tried the various functions on there. Fastboot doesn't detect the device (even though its in fastboot mode) in order for me to unlock the bootloader again and flash it with the stock ROM. Windows (8) does detect it but can't load drivers for it. Been through all the instructions on the Nexus Root Toolkit - reinstall drivers, cleared the device from device manager, cleared it from usb list etc. Fastboot just won't detect it to allow me to unlock!!
3. Let the battery drained and tried factory resetting but doesn't work (not tried fully charging it and then resetting though)
4. Been trying various other things which I read on the forum(s) but nothing seems to work!:crying:
Literally spent the whole day trying so many different things. Seems like I discovered a whole new unique problem to causing boot loop on the Nexus 4. I don't want to have to send this back to Google for a replacement if they give me one - hopefully with the locked bootloader and the data cleared, they won't know I've rooted, not to mention its micro-sim and my backup feature phone doesn't take micro-sim :crying:
Has any one had this issue before and fixed it!? Would really appreciate the help/guidance!
My first time rooting a phone, didn't do it before on other phones because thought knowing my luck I'd brick it beyond repair! Luck would have it, that exactly what has happened.
Appreciate the replies and help on this!
Click to expand...
Click to collapse
I'm having the same problem!
For the toolkit to see the device, you need to put your device to fastboot mode by pressing vol (-) and then the power button (the phone should be in powered off mode to do this).
andr0idfreak said:
For the toolkit to see the device, you need to put your device to fastboot mode by pressing vol (-) and then the power button (the phone should be in powered off mode to do this).
Click to expand...
Click to collapse
I've done this many times but still no luck
ThuanBui said:
I've done this many times but still no luck
Click to expand...
Click to collapse
I had a boot loop issue. It was stuck on Google logo - the white logo.
I couldn't go into recovery either.
My fix was to flash the stock recovery.IMG
I too couldn't detect the device however I kept trying.
If you face a problem getting into fast boot mode try pressing vol up + vil down + power. Didn't work for me but worked for some.
Let me know how it goes I'm glad to help out if I can
Having USB Debugging ticked WHILE IN ANDROID has absolutely no effect on whether or not your computer can see the device WHILE IN RECOVERY OR FASTBOOT.
monkeying. around said:
I had a boot loop issue. It was stuck on Google logo - the white logo.
I couldn't go into recovery either.
My fix was to flash the stock recovery.IMG
I too couldn't detect the device however I kept trying.
If you face a problem getting into fast boot mode try pressing vol up + vil down + power. Didn't work for me but worked for some.
Let me know how it goes I'm glad to help out if I can
Click to expand...
Click to collapse
Didn't fix it in the end...no matter what I tried. I got a replacement from Google (thankfully they didn't charge me for the new one!).
BTW the batch of Nexus 4 released in end of Jan/early Feb has a much better battery life than the one I got from the batch released in early Dec. Won't be rooting the new Nexus 4 in case sh*t happens again but no doubt will get tempted again somewhere down the line!
Thank you to everyone who replied!~ :good:
sideloading 4.4.2 and stuck on boot loop
ThuanBui said:
Didn't fix it in the end...no matter what I tried. I got a replacement from Google (thankfully they didn't charge me for the new one!).
BTW the batch of Nexus 4 released in end of Jan/early Feb has a much better battery life than the one I got from the batch released in early Dec. Won't be rooting the new Nexus 4 in case sh*t happens again but no doubt will get tempted again somewhere down the line!
Thank you to everyone who replied!~ :good:
Click to expand...
Click to collapse
bro mime nexus 4 has stuck into boot loop after upgrading from 4.4 to 4.4.2 .i was sideloading the zip dont know whats the issue ......i was rooted but went to stock via nexus roottool kit to get OTA . any suggestion
joshnichols189 said:
Having USB Debugging ticked WHILE IN ANDROID has absolutely no effect on whether or not your computer can see the device WHILE IN RECOVERY OR FASTBOOT.
Click to expand...
Click to collapse
all you got to do is download the toolkit and flash the software your phone is using and put it in fastboot and begin
:good::good::good::good::good::good::good:
I apologize already if this has already been posted before, I couldn't see one that had my issues so I'm making this thread.
OK, so here is my problem and everything that I can think of that I've done to my phone.
Today I tried to restart my phone as it was getting a bit sluggish. When I did it started booting fine then the animation sound stopped while the droid eye was being put together. Now my phone will not pass the droid eye during the boot phase. I press the power and both volume buttons and after a few seconds it starts itself back up again. I do the power button and down volume buttons and it still does the same thing. I've even performed the factory reset twice and it still won't help.... And no matter what I do it keeps booting itself back up on its own.
What I've done to my phone:
I am rooted but never got the boot loader unlocked since i waited too long and the last update wouldn't allow the boot loader unlock methods anymore. I have used titanium backup app to delete some system apps for example the Verizon football one, slacker radio, and any of those useless apps that I never use. I haven't deleted anything lately and have restarted my phone many times since. I have been delaying the recent update hitting no or not now, whatever it says. I thought that I said no today on the system update as well. Even then my phone was working before I restarted it.
PLEASE I hope that there is something that I can do to fix my phone because I'm forced to use my LG Vortex again and my upgrade isn't for another year..... I don't want to buy a new one since this phone has been great and I'm almost certain that if there was a way to reinstal or flash the droid razr m OS that that would fix my issues.
Thanks in advance for your input and please know that I'm a novice with this kind of thing so you will have to explain the process to me. If i have instructions I can definitely follow them.
THANKS!
You Factory Reset a couple of times, so that tells me you know how to get into recovery. See if you can get back into recovery and try clearing cache/dalvik too. I think you can still do that from stock recovery.
If that doesn't work and your battery is good, you can fastboot to recover it. If your battery was low when you started this, charge it prior to fastbooting. Just hold down the power button until the phone shuts off and plug into a WALL charger until it's charged. If the battery is good, you can grab the firmware from here http://sbf.droid-developers.org/phone.php?device=8 (use the second one from the bottom, .3, if you flash the last one you will not be able to gain root) and flash in RSD. Another choice is to use House of Moto to recover: http://www.droidrzr.com/index.php/topic/28162-house-of-moto-20/ .
OK, so I deleted the cashe and still a no go. For the second step of getting the .3 to regain root. would it be possible to get an even earlier version so I can unlock the boot loader? Also when you say flash in RSD, what is that? I know of the AP flash from the first menu, is that something inside of Recovery menu options?
Thanks for your help!
**UPDATE**
THANKS! I was able to eventually figure it out and used the last option that you said and my phone works! Now working on getting root back. Thanks again!! But I really would like to know if I could do the same thing but with an earlier version to unlock the bootloader.
Droid Razr starting up issue
Hi guys, I am facing a weird issue with my Droid Razr and hoping pros to help me sort this out and get my phone running.
I am using Droid Razr but since last one week it is not starting up. Let me elaborate, currently it is switched off and not getting up. While starting it pass through M logo but can't go ahead for startup animation (droid eye animation). Even after leaving on that animation for entire day, it is not going ahead of that.
However, if I connect it to a wall charger (while it is off) it shows battery getting charged. It is taking a usual timing of 90 minutes for full charge.
I have important pictures and data into phone memory is there any way to recover it.
I would appreciate if you can guide me to get my phone up and running as usual.
RikRong said:
You Factory Reset a couple of times, so that tells me you know how to get into recovery. See if you can get back into recovery and try clearing cache/dalvik too. I think you can still do that from stock recovery.
If that doesn't work and your battery is good, you can fastboot to recover it. If your battery was low when you started this, charge it prior to fastbooting. Just hold down the power button until the phone shuts off and plug into a WALL charger until it's charged. If the battery is good, you can grab the firmware from here (use the second one from the bottom, .3, if you flash the last one you will not be able to gain root) and flash in RSD. Another choice is to use House of Moto to recover: .
Click to expand...
Click to collapse
Hi there, I was attempting to move from a nougat Lineage OS rom to an unofficial Oreo one and as such needed to update to an Oreo Universal Bootstack as far as I understood it. I, therefore, flashed this: A2017X_BootStack_B32_N.zip (sorry, I'm too new a user to be able to post links) file using TWRP however on reboot it appears I have completely bricked my phone. At this point I am unable to get anything to display on my phone at all, any combination of button holds yields the same result, there is a slight vibration then the led turns red for a second then switches off. Connecting it to a PC it is recognised as ZTE Handset Interface (DFU). From what I've read it appears at least with the Chinese version (that I have) that you should be able to manually get it into EDL mode though pressing the power and both volume buttons but I have had no luck with that so far. Any help is much appreciated
lukeshields said:
Hi there, I was attempting to move from a nougat Lineage OS rom to an unofficial Oreo one and as such needed to update to an Oreo Universal Bootstack as far as I understood it. I, therefore, flashed this: A2017X_BootStack_B32_N.zip (sorry, I'm too new a user to be able to post links) file using TWRP however on reboot it appears I have completely bricked my phone. At this point I am unable to get anything to display on my phone at all, any combination of button holds yields the same result, there is a slight vibration then the led turns red for a second then switches off. Connecting it to a PC it is recognised as ZTE Handset Interface (DFU). From what I've read it appears at least with the Chinese version (that I have) that you should be able to manually get it into EDL mode though pressing the power and both volume buttons but I have had no luck with that so far. Any help is much appreciated
Click to expand...
Click to collapse
Hi lukeshields. It's not much help to you but I have exactly the same problem right now. If I do find a solution I will let you know.
I have heard however that with a deepflash cable, bought or one you can make at home sometimes you can boot into EDL. I have tried and it didn't work, maybe it will be different in your case.
Cheers.
Victor13f said:
Hi lukeshields. It's not much help to you but I have exactly the same problem right now. If I do find a solution I will let you know.
I have heard however that with a deepflash cable, bought or one you can make at home sometimes you can boot into EDL. I have tried and it didn't work, maybe it will be different in your case.
Cheers.
Click to expand...
Click to collapse
Hey man, I actually literally just managed to get my phone working again. It was a pretty hands-on job but I followed the guide: https://forum.xda-developers.com/axon-7/how-to/guide-dfu-unbrick-guide-disassembly-t3731152 which got my phone back on the official stock and ROM. It involves taking your phone apart but it's not too tricky if you take your time and are extra careful. Good luck and thanks anyway!
My 6T is currently a paperweight (bricked, screen won't turn on, no fastboot, no nothing) and here's the succession of events that led to it:
I live in the US and bought the unlocked 6T.
1) A few weeks ago I rooted it with same steps described in this post --> https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/. Everything seemed to go well, I had Magisk and my phone worked just fine.
2) About a week later I got a notification that my phone had a software update ready. I idiotically obliged and installed it. After the install, I still got the bootloader unlocked screen at start up so I thought my phone might still be rooted. However, I couldn't download any mods on Magisk and my root checker said I was no longer rooted. So basically, my phone appeared rooted (apps like Google Pay wouldn't work, I got the warning about the Bootloader at start-up, etc.) but I no longer had the benefit of being able to install mods through Magisk.
3) A few weeks later (yesterday) I decided I would explore options for un-rooting, mainly so I could use Google Pay again. Remember, my phone wasn't actually rooted anymore, since the update. So I thought locking the bootloader should fix my problems. I did that with fastboot oem lock and then my phone was stuck in a fastboot loop. I tried every option in fastboot and would just end up right back there. I started looking for fixes and came across the MSMDownload Tool --> http://https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892. I downloaded the driver, it recognized my device, I downloaded the tool, then ran it. At 16 seconds, the download stopped and I got an error saying "Sahara communication failed." After looking up a fix that involved holding down the volume+ button, I decided I'd try again. This is where I f*cked up. I unplugged my phone without stopping the download, and that leads us to this very moment. My phone does not turn on at all. I have no access to fastboot or anything. My computer does recognize it when I plug it back in (I'm on Windows).
If you read this it's probably obvious that I only know enough to be dangerous and bricking my phone was inevitable. Feel free to call me an idiot, I only ask that you provide some useful information, preferably on the subject of getting my phone working again. Thank you all in advance. I hope this post isn't redundant. I didn't find anything on here that was a fix for my situation. I'm also open to contacting OnePlus if anyone thinks I should do that first. I genuinely thank anyone that takes the time to read/help! xd
Use the msm tool...doesn't use fastboot
Edit...nevermind
You need to get your phone to show up as "US8_BULK" like in the MSM thread you linked. You can do this even if your phone wont boot properly. I have done it multiple times before. When in the Qualcom flashing mode the screen will not light up at all.
Hold all the buttons until it resets. This could take up to 30 seconds of holding the buttons. The just follow the steps in the MSM thread starting with this one:
Power off the phone, then hold for 5 seconds vol up and plug the usb to computer. Now you have to see US8_BULK as new device connected and you can also see in device manager; if you can't notice it, repeat the process until you see it (power on, power off, hold...) there is a full youtube guide for op5 and it's the same process - (https://www.youtube.com/watch?v=PpLvmID1wdI)
Edit: It can take some practice to get the timing down, especially if your screen is not coming on at all. Just keep trying as you will be able to get into that Qualcom flashing mode unless there is physical hardware damage to your phone.
Jager said:
You need to get your phone to show up as "US8_BULK" like in the MSM thread you linked. You can do this even if your phone wont boot properly. I have done it multiple times before. When in the Qualcom flashing mode the screen will not light up at all.
Hold all the buttons until it resets. This could take up to 30 seconds of holding the buttons. The just follow the steps in the MSM thread starting with this one:
Power off the phone, then hold for 5 seconds vol up and plug the usb to computer. Now you have to see US8_BULK as new device connected and you can also see in device manager; if you can't notice it, repeat the process until you see it (power on, power off, hold...) there is a full youtube guide for op5 and it's the same process -
Edit: It can take some practice to get the timing down, especially if your screen is not coming on at all. Just keep trying as you will be able to get into that Qualcom flashing mode unless there is physical hardware damage to your phone.
Click to expand...
Click to collapse
Awesome, that worked! I kept seeing I needed to hold volume+ and power but holding both and power is what actually worked for me. Thanks a lot my friend
@lapitman, glad to see that you finally got it to work!
Hi guys,
this is my first x compact. I unlocked the bootloader per sony's instructions on their site + what I read here.
I flashed twrp, booted to recovery, and wiped and installed the lineage 16.0 which is stickied.
Everything worked great but various rootcheckers said still not rooted. This bothered me.
I followed the thread (https://forum.xda-developers.com/x-compact/how-to/stock-8-0-root-recovery-t3747479).
I used flashtool to flash stock oreo. After that, bootloops. And can't access recovery.
I can still enter flash mode and fastboot mode, but using the CMD in platform-tools, phone not recognized.
There must be something I can do? Thank you.
pleasuremann said:
Hi guys,
this is my first x compact. I unlocked the bootloader per sony's instructions on their site + what I read here.
I flashed twrp, booted to recovery, and wiped and installed the lineage 16.0 which is stickied.
Everything worked great but various rootcheckers said still not rooted. This bothered me.
I followed the thread (https://forum.xda-developers.com/x-compact/how-to/stock-8-0-root-recovery-t3747479).
I used flashtool to flash stock oreo. After that, bootloops. And can't access recovery.
I can still enter flash mode and fastboot mode, but using the CMD in platform-tools, phone not recognized.
There must be something I can do? Thank you.
Click to expand...
Click to collapse
Use Flashtool again, and this time, before clicking , in the box that says "wipe", check 'userdata'.
Back up anything you want to save in internal storage.
levone1 said:
Use Flashtool again, and this time, before clicking , in the box that says "wipe", check 'userdata'.
Back up anything you want to save in internal storage.
Click to expand...
Click to collapse
Thank you so much. I've seen your name a lot around here, I appreciate you taking the time to help. I'm booting now and starting the root process
pleasuremann said:
Thank you so much. I've seen your name a lot around here, I appreciate you taking the time to help. I'm booting now and starting the root process
Click to expand...
Click to collapse
No problem - I'm messing around with a Samsung at the moment, but I still check in here from time to time. I think XC is my favorite phone so far... XZ2C was really nice too, but (unofficially) official Sailfish OS puts XC on top for me...
levone1 said:
No problem - I'm messing around with a Samsung at the moment, but I still check in here from time to time. I think XC is my favorite phone so far... XZ2C was really nice too, but (unofficially) official Sailfish OS puts XC on top for me...
Click to expand...
Click to collapse
Hi friend, please maybe you can help me. I have almost the same issue. But after using LineageOS for some days, my phone stuck in boot logo. I managed to use Flash Tool to flash latest original stock ROM (Customized IBE). Strangely the flash process ended OK, but the phone still stuck in boot logo. I'm only able to force shut down with Volumen Up+Power Off (3 vibrates). Not possible to enter Recovery Mode.
I'm 98% sure that I have flashed with check in wipe USERDATE and also in CUST-RESET. But I wanted to try again, and now Im not able to enter flashmode. Phone gets green light, when volume down, but Flashstool is not recognizing the phone.
Thanks in advance
jayeffpee said:
Hi friend, please maybe you can help me. I have almost the same issue. But after using LineageOS for some days, my phone stuck in boot logo. I managed to use Flash Tool to flash latest original stock ROM (Customized IBE). Strangely the flash process ended OK, but the phone still stuck in boot logo. I'm only able to force shut down with Volumen Up+Power Off (3 vibrates). Not possible to enter Recovery Mode.
I'm 98% sure that I have flashed with check in wipe USERDATE and also in CUST-RESET. But I wanted to try again, and now Im not able to enter flashmode. Phone gets green light, when volume down, but Flashstool is not recognizing the phone.
Thanks in advance
Click to expand...
Click to collapse
Does fastboot work? Also, what do you ultimately want to do, return to stock?
levone1 said:
Does fastboot work? Also, what do you ultimately want to do, return to stock?
Click to expand...
Click to collapse
yes, after hard work to install drivers, I managed to get the phone to be recognized by Flashtool in fastboot mode. But the phone is not charging when turned off, and its not rebooting. I wanted to try again with stock ROM, since I got some battery issues with LineageOS (phone turned off while playing some games, and worked fine while doing the same with usb cable charging to laptop or AC charger.)
But I cannot do anything right now. Only fastboot mode and force restart works, but it stuck in Sony logo (after normal bootloader unlock 5 seconds warning). What can I do?