Related
i am pretty sure I bricked my phone. I just want to make sure before it becomes my good looking paper weight. I installed the wrong spl. So naturally it doesnt start up. Nothing at all. But, my orange led is on when I charge it. Also, it flashes red when the battery is low.
The problem is when i power my phone off even while its being charged, the orange led shuts off. So, is it really dead? Also anyone know if their will be a way in the future to unbrick? Thanks.
Did you try to hold "back" or "volume down" or "home" button while power it on ?
If you can get it to fastboot screen there should still be hope for the phone!
Edit: Unbricking should be a question about having the right hardware, so yes it should be posible even now!
Yeah I have done all of the above to no avail. Sucks as I really liked the phone. I thought i was using a engineering spl but i guess it was the wrong one. I wonder how it will be to repair bricked phones. I mean if they cant be turned on and such
luna9698 said:
Yeah I have done all of the above to no avail. Sucks as I really liked the phone. I thought i was using a engineering spl but i guess it was the wrong one. I wonder how it will be to repair bricked phones. I mean if they cant be turned on and such
Click to expand...
Click to collapse
Well i'm not to sure about how exactly, but the software were not born within the hardware so you need the hardware to be able to put the SPL or whatever directly into the place it belongs. I talked with a few guys here in Thailand about if they were able to unbrick a Magic and they all say they should be able to but cant promish anything cause they never tryed yet.
But now that you say that it actually recharge the mobile, does it also recharge when you use the USB connect cable from PC ?
If it does did you try to use fastboot through command prompt with adb ?
Yeah it does charge. It has now changed to a green light. The problem is that i dont know how to use the adb command prompts. Nor do I know how to set it up to do so. I dont see it though in Windows. If I click on My Computer it isnt listed.
luna9698 said:
Yeah it does charge. It has now changed to a green light. The problem is that i dont know how to use the adb command prompts. Nor do I know how to set it up to do so. I dont see it though in Windows. If I click on My Computer it isnt listed.
Click to expand...
Click to collapse
You wont see it in windows explorer cause its not mounted but take a look in the wiki: http://wiki.xda-developers.com/index.php?pagename=HTC_Sapphire_Hacking#sec03
You will find info about how to install and use adb in command prompt
Hope this will help you and that it can find your mobile!
I figured you also tryed to remove the battery and try to power on while holding home/back/volume down
ronni.rasmussen said:
You wont see it in windows explorer cause its not mounted but take a look in the wiki: http://wiki.xda-developers.com/index.php?pagename=HTC_Sapphire_Hacking#sec03
You will find info about how to install and use adb in command prompt
Hope this will help you and that it can find your mobile!
I figured you also tryed to remove the battery and try to power on while holding home/back/volume down
Click to expand...
Click to collapse
I got the adb working but it cant find it. Thanks for your help. I just have to hope that in the near future they will be able to revive bricked phones.
My Nexus one won't turn on. I tried flashing RADIO 32.24.00.22U_4.03.00.21_2 that I downloaded from Modaco.
After it failed to install showing the error message like
"Multiple Radio images"
and a few others I try to reboot it.
when trying to reboot it there showed a picture of a android and a orangish arrow and a box.
Help...I think I bricked it.
Help?
Please?
Can you get into boot loader? Hold down the track ball, then power on, and keep holding down the track ball...
Also, try holding down the "volume down" toggle button while powering on if the track ball method doesn't work...
If both don't do anything but take you to that same screen, let it sit on that screen for a bit, say 10 minutes just in case...
If still nothing, see what happens when you plug your phone into your computer with the data cable, is it recognized? If so, can you get ADB to recognize it?
Jackasaur said:
Help?
Please?
Click to expand...
Click to collapse
can u get to the recovery image? if u can, its not bricked.
well I tried plugging it into the computer, I tried the wall charger, and nothing seems to work. The LED doesn't come on, and the button combination doesn't work. So I think it's dead for good. :C Before everything got screwed All I saw was a box and an arrow pointing at a android. Which I think meant it was unboxing. I then thought it froze so I tried to take the battery out, and after that it didn't turn on anymore. No LED, no recovery, no nothing. :C Quite sad.
Why the f are so many people intent on taking their batteries out while the phone is updating? I'm not saying that led to the bricking...but it probably didn't help.
Jackasaur said:
well I tried plugging it into the computer, I tried the wall charger, and nothing seems to work. The LED doesn't come on, and the button combination doesn't work. So I think it's dead for good. :C Before everything got screwed All I saw was a box and an arrow pointing at a android. Which I think meant it was unboxing. I then thought it froze so I tried to take the battery out, and after that it didn't turn on anymore. No LED, no recovery, no nothing. :C Quite sad.
Click to expand...
Click to collapse
This part takes a few minutes. I am not totally sure what is happening at this point but I'm assuming it's not good to remove battery during this. Mine sat on that screen for a few min and then finished.
Try to boot up with volume down button held. Then use volume arrows to choose recovery and hit power.
uansari1 said:
Why the f are so many people intent on taking their batteries out while the phone is updating? I'm not saying that led to the bricking...but it probably didn't help.
Click to expand...
Click to collapse
Everyone expects everything to be instant these days... "Uh oh! The screen isn't doing anything, it's been at least 20 seconds! I could just wait and leave it for a few minutes like all the guides say to do. Or I could take my battery out...how could that hurt, right?"
For me it took a good 3-4 minutes on the screen with the arrow and the box.
Anyways, if you can't get to the recovery then you might be buying a new N1.
ahh it took like 5 minutes for me, I have to admit I was a little worried since you dont see status bars or anything, but like said, the guides warn for this.
I cant imagine that removing the battery broke it though, he should be able to load a recovery image
I feel sad for him so bumping
Bleh. I'll just have to wait and see. I'll contact HTC.
tomsan84 said:
ahh it took like 5 minutes for me, I have to admit I was a little worried since you dont see status bars or anything, but like said, the guides warn for this.
I cant imagine that removing the battery broke it though, he should be able to load a recovery image
I feel sad for him so bumping
Click to expand...
Click to collapse
If you remove the battery during the period he did, which is when the phone is actually flashing the radio ROM, yes removing the battery can and likely did break it for him. There are 2 ways to brick an Android device, while flashing a radio ROM and while flashing an SPL...
OP, have you tried any of the button combos we have recommended? Have you tried putting your battery in the phone, then without turning it on, putting it on the charger to see if it can charge the battery at least (you said it wasn't even turning on, which is likely because you have a dead battery)... charge the battery first, then try the button combo's we recommended.
And please, when you report back, and not to sound like an ass, do so clearly and systematically (I can't tell from your posts what did or didn't happen, and whether you tried anything we suggested, nor what the current state of the phone is)... so, please use this format to make it clear to us trying to help:
Battery: Charged or Wouldn't Charge (LED will come on if it is charging)
Trackball+Power: Booted into boot loader, yay! or Went to the damn box
Volume down+Power: Booted into fast boot! or Went to the damn box
And remember, you have to hold down the button, either trackball or volume down, then press the power and keep holding down the trackball or volume down until it either goes to boot loader or it goes to the box screen... you might want to even wait for a minute on the box screen(if it goes to that) while holding down the button to make sure it can't get into boot loader...
Okay so I took the battery out, put it back in, and tried charging it. The Battery LED did not come on, so I'm guessing it's not charging.
The Trackball+Power did not work.
The Volume down+Power did not work.
I think I most likely broke it, due to the fact that I took the battery out while it was flashing the radio ROM onto the phone. I kinda did it on a impulse, which is my fault. So do you think it'd be possible if I did contact HTC they'd send me a swap, and not be able to make my phone work or turn on, and everything will go on as if I "broke" it and not unlock it or anything?
Jackasaur said:
Okay so I took the battery out, put it back in, and tried charging it. The Battery LED did not come on, so I'm guessing it's not charging.
The Trackball+Power did not work.
The Volume down+Power did not work.
I think I most likely broke it, due to the fact that I took the battery out while it was flashing the radio ROM onto the phone. I kinda did it on a impulse, which is my fault. So do you think it'd be possible if I did contact HTC they'd send me a swap, and not be able to make my phone work or turn on, and everything will go on as if I "broke" it and not unlock it or anything?
Click to expand...
Click to collapse
It sounds like you have a true brick... disruption of the radio ROM flashing causes lots of bricks, and did so for you.
It is pretty common, at least with T-Mobile with the G1, to call them up and tell them your phone asked you to update, and while updating it froze and won't turn on or charge anymore. Not sure if HTC will handle it the same as T-Mobile did, but if they do they will just send you a new unit, you send the old one back, and you are back up and running... they might ask that you send it to them first, but there is no way for them to test if it was rooted/unlock boot loader if it can't be powered on, so you should be fine.
Sweet. So I called HTC, and they said they'll repair it, but I asked for a swap instead, so I'll be getting one by either Wednesday, or Thursday. Good stuff! I'll tell you all how it goes. :] Now I am stuck with my Nokia N95. Thanks for all your help.
Did you tell them you have an unlocked bootloader?
uansari1 said:
Did you tell them you have an unlocked bootloader?
Click to expand...
Click to collapse
he doesnt have 2 tell em
lightforce said:
he doesnt have 2 tell em
Click to expand...
Click to collapse
Yeah, he doesn't have to tell them... but they don't have to cover his phone either.
If they find out it's unlocked after the fact, they can charge you to repair the phone.
How exactly will they know he unlocked the bootloader if the device cannot even properly turn on, unless htc has other methods of being able to "restore" the phone, then he should be rather ok. Am I not looking into this deeply enough? Can the phone turn on with a new battery or something? Does HTC have alternatives ways of checking?
Eclair~ said:
How exactly will they know he unlocked the bootloader if the device cannot even properly turn on, unless htc has other methods of being able to "restore" the phone, then he should be rather ok. Am I not looking into this deeply enough? Can the phone turn on with a new battery or something?
Click to expand...
Click to collapse
That's my point man.. I don't know. All they have to see is that open padlock and they can deny the claim.
http://androidforums.com/fascinate-all-things-root/179136-bricked-fascinate-beyond-repair.html
This is exactly what happened to a friend of mine as well. He accidentally flashed the captivate Odin3; nothing works now. The weird thing is, is when you plug up the phone now it will do nothing. It won't power on. It won't even give prompt from the computer, anything. The only way it will power up at all is having he battery in only. Can someone explain me how this might happen? Can a software flash just short out a board?
I don't know how to help you...but am wondering why do people try this?????? We know there is no recovery available...I am just speechless.... That's probably why moto locked bootloader cause of crap like this and money loss
tats_06 said:
I don't know how to help you...but am wondering why do people try this?????? We know there is no recovery available...I am just speechless.... That's probably why moto locked bootloader cause of crap like this and money loss
Click to expand...
Click to collapse
Ill on honestly he could of been looking for a way to clear the stock/angel rom, so that he could reflash to stock. Even if you reflash/wipe cache/ reformat some settings remain. For instance if you don't have debugging on and you turn the brightness off by mistake you're FUBAR'd!
Can he get to download mode (battery out! Usb connected. Volume down). If he does, there's still hope.
I actually had to flash the US Cellular kernel in order to get to the point where I could re-flash the stock kernel.
namebrandon said:
Can he get to download mode (battery out! Usb connected. Volume down). If he does, there's still hope.
I actually had to flash the US Cellular kernel in order to get to the point where I could re-flash the stock kernel.
Click to expand...
Click to collapse
Thanks NameBrandon! I knew I read that somewhere but I couldn't remember where.
josh6780 said:
The weird thing is, is when you plug up the phone now it will do nothing. It won't power on. It won't even give prompt from the computer, anything. The only way it will power up at all is having he battery in only.
Click to expand...
Click to collapse
Just to confirm then, because it sounds like you've already tried: are you positive you are unable to get into download mode?
josh6780 said:
http://androidforums.com/fascinate-all-things-root/179136-bricked-fascinate-beyond-repair.html
This is exactly what happened to a friend of mine as well. He accidentally flashed the captivate Odin3; nothing works now. The weird thing is, is when you plug up the phone now it will do nothing. It won't power on. It won't even give prompt from the computer, anything. The only way it will power up at all is having he battery in only. Can someone explain me how this might happen? Can a software flash just short out a board?
Click to expand...
Click to collapse
I have flashed the captivate rom and the i9000 rom before from odin, and was still able to get into download mode. At the time i hadnt made the odin restore files so i had no way of fixing it. The files i created in another thread should be able to get him back, as namebrandon can tell you
namebrandon said:
Can he get to download mode (battery out! Usb connected. Volume down). If he does, there's still hope.
I actually had to flash the US Cellular kernel in order to get to the point where I could re-flash the stock kernel.
Click to expand...
Click to collapse
That is what is so weird about all this. If he usb is plugged in at all the phone will not power on. It will only power on when it is using the battery.
And yes. He was trying to flash back to stock ROM bc he bricked it with a different ROM. He was under the impression that Odin would auto detect his phone.
josh6780 said:
That is what is so weird about all this. If he usb is plugged in at all the phone will not power on. It will only power on when it is using the battery.
And yes. He was trying to flash back to stock ROM bc he bricked it with a different ROM. He was under the impression that Odin would auto detect his phone.
Click to expand...
Click to collapse
If he cannot get into download mode (pull out battery, pull out sd card, put battery back in, hold ONLY the volume down key and plug into computer) then he completely bricked his phone. He might have clicked the update boot loader option in Odin, or just flashed something that he didn't know what would happen when he did.
If he takes it back to verizon, they will most likely replace it as long as he doesn't tell them he rooted it / tried flashing it.
fallingup said:
If he cannot get into download mode (pull out battery, pull out sd card, put battery back in, hold ONLY the volume down key and plug into computer) then he completely bricked his phone. He might have clicked the update boot loader option in Odin, or just flashed something that he didn't know what would happen when he did.
If he takes it back to verizon, they will most likely replace it as long as he doesn't tell them he rooted it / tried flashing it.
Click to expand...
Click to collapse
And it, you know, doesn't show the AT&T boot logo..
But yeah, if he can't get to download mode, it's done.
namebrandon said:
And it, you know, doesn't show the AT&T boot logo..
But yeah, if he can't get to download mode, it's done.
Click to expand...
Click to collapse
Well, that's the problem. He needs it not to show the ATT logo. Lol. Working on that.
josh6780 said:
Well, that's the problem. He needs it not to show the ATT logo. Lol. Working on that.
Click to expand...
Click to collapse
Microwave?
Take the battery out first. 4-5 seconds should do it. Too long and the plastic will melt.
namebrandon said:
Microwave?
Take the battery out first. 4-5 seconds should do it. Too long and the plastic will melt.
Click to expand...
Click to collapse
um. how about that is a horrible idea. i just kicked you on irc for even suggesting that.
If you cant get into download mode, you could always splice a micro usb cable into a surge protected outlet and burn out the board...
I AM NOT RESPONSIBLE FOR WHAT YOU DO TO YOUR PHONE. HOUSE. CAR. DOG. ANYTHING. YOU DO ANYTHING ON YOUR OWN!
fallingup said:
um. how about that is a horrible idea. i just kicked you on irc for even suggesting that.
If you cant get into download mode, you could always splice a micro usb cable into a surge protected outlet and burn out the board...
I AM NOT RESPONSIBLE FOR WHAT YOU DO TO YOUR PHONE. HOUSE. CAR. DOG. ANYTHING. YOU DO ANYTHING ON YOUR OWN!
Click to expand...
Click to collapse
We're to the point of trying to figure out how to completely destroy a phone so it won't boot. I don't think burning out the board is much more of a risk than a microwave for 4-5 seconds. What if his cable lights on fire, then his carpet, etc..
It's a stupid point to argue.
fallingup said:
um. how about that is a horrible idea. i just kicked you on irc for even suggesting that.
If you cant get into download mode, you could always splice a micro usb cable into a surge protected outlet and burn out the board...
I AM NOT RESPONSIBLE FOR WHAT YOU DO TO YOUR PHONE. HOUSE. CAR. DOG. ANYTHING. YOU DO ANYTHING ON YOUR OWN!
Click to expand...
Click to collapse
Well thanks for trying to help but I just took the phone apart, pulled the AMOLED cable and put it back together.
josh6780 said:
Well thanks for trying to help but I just took the phone apart, pulled the AMOLED cable and put it back together.
Click to expand...
Click to collapse
lol.. or you could do that. Nice work.
Love this thread.
That's not how you break a phone, THIS is how you break a phone.
No no no, you're breaking it wrong!
I should take it to AT&T and ask them to activate it. "sir, this is a Verizon phone"
"no it's not"
"yes, it is."
"look you idiot, it as your effing name comes up when you turn it on"
":/"
So first some back-story, I'll get right into it. I recently dropped my phone in some water. As soon as possible I dried off the outside, and let it sit. That was the only thing I could do at the time, I had no rice, no tools to open up the phone, anything. I ended up with a solid red light, and everything unresponsive.
The next day I got some tools to open her up. There was pretty extensive corrosion to the motherboard, so using some alcohol I cleaned it all off, rinsed it, and let it dry. I also took apart everything else and cleaned any corrosion. The inside looks brand new. However, this isn't the point of the thread.
It appeared my cleaning helped quite a bit. Upon re-assembling and plugging in, I immediately got a charging sign on the phone. However, after trying to power on, I got no response. Additionally, The charging signal went out after about 20 seconds, and the whole phone became unresponsive again. I can do this process as many times as I want, but the same thing happens every time.
So I tried a different approach. First I hold down both volume rockers plus the power button, and plug it in while holding them down. This puts the phone into "download mode" However, once in download mode the phone is, again, unresponsive. After plugging into my laptop, my computer recognizes the phone, but not as "Nexus 4," but as "Full JellyBean on Mako."
Is there anything I can do about this? I've heard about drivers being able to be installed when in download mode, but I would not know what these are, where to get them, or how to install them. I really don't mind if my phone never works 100% again, I doubt it would. I just want to be able to get into the storage so I can recover some of the files I lost.
It's also probably worth mentioning I have not gotten a solid red light after the clean. Once in a while I will get a blinking red light after plugging it in, but after less than a minute it stops and goes through the charging/stop charging phase I'm so familiar with. Any help at all would be appreciated, and thanks in advance.
The charging block and/or battery could be wrecked, for safety reasons and because it will probably become faulty soon you should change the battery anyway. If the charging block is broken flashing your phone could fail. It's also possible the board was irreparably damaged, but it's probably worth a try as the parts aren't too expensive.
DrFredPhD said:
The charging block and/or battery could be wrecked, for safety reasons and because it will probably become faulty soon you should change the battery anyway. If the charging block is broken flashing your phone could fail. It's also possible the board was irreparably damaged, but it's probably worth a try as the parts aren't too expensive.
Click to expand...
Click to collapse
After trying to figure more things out, I kept it plugged in for a while. It appears my battery actually holds at least a pretty good charge, as the indicator is full when I plug it in now. However, I don't know what you mean when you say charging block.
Also, I seemed to determine my power button isn't working either. I always thought no response to pushing it meant there was something else going on, but I am able to put it into "download mode" by just holding down the volume rockers and plugging it in. Is there a way to turn on the phone another way besides the power button? Also if not, will buying another power button fix the problem? I don't want to buy one then later figure out the reason it wasn't turning on was just a board problem, and not a problem with the button itself.
You can short the power button with a screwdriver or something should turn the phone on., By charging block I mean the secondary board that the micro usb port is a part of, it can be replaced fairly easily if necessary.
26694484 100
DrFredPhD said:
You can short the power button with a screwdriver or something should turn the phone on., By charging block I mean the secondary board that the micro usb port is a part of, it can be replaced fairly easily if necessary.
Click to expand...
Click to collapse
With a screwdriver? Enlighten me, I'd have no idea how to do that. If I had a faulty charging block, then my phone wouldn't be able to charge correct? My phone was plugged in for a while in download mode, and it gained a full charge from a relatively low charge. I also took the block apart and cleaned any corrosion, so I think that's still functional.
Some more progress, upon further attempting to turn the phone on, I was able to get it into fastboot mode. When plugging into the computer it is recognized, but as just "Android." I will type out what information is displayed here, minus serial number, as a new member cannot submit links in posts apparently.
FASTBOOT MODE
PRODUCT_NAME - mako
VARIENT - mako 8GB
HW VERSION - rev_11
BOOTLOADER VERSION - MAK0230d
BASEBAND VERSION - M9615A-CEFWMAZM-2.0.1700.98
CARRIER INFO - None
SERIAL NUMBER -
SIGNING - production
SECURE BOOT - enabled
LOCK STATE - locked
Also, fastboot at the top (as far as I know) usually says "Start" or "Recovery Mode," but mine says "Restart bootloader." When I try switching with my volume buttons, nothing happens.
Another update, just in case anyone is still listening..
Str1ngcheese said:
Also, fastboot at the top (as far as I know) usually says "Start" or "Recovery Mode," but mine says "Restart bootloader." When I try switching with my volume buttons, nothing happens.
Click to expand...
Click to collapse
This no longer applies, for some reason I am able to switch through all modes, incliding "Start, Power Off, Recovery Mode, and Restart bootloader."
Str1ngcheese said:
Another update, just in case anyone is still listening..
This no longer applies, for some reason I am able to switch through all modes, incliding "Start, Power Off, Recovery Mode, and Restart bootloader."
Click to expand...
Click to collapse
Now that you're at this point, have you attempted to flash the phone with a stock image? I'd be weary of what the other poster said though and ensure your USB connection is holding steady because you don't want it dying half way through a flash because then you'll have a brick.
Monotoko said:
Now that you're at this point, have you attempted to flash the phone with a stock image? I'd be weary of what the other poster said though and ensure your USB connection is holding steady because you don't want it dying half way through a flash because then you'll have a brick.
Click to expand...
Click to collapse
I have tried actually. I used the Nexus Root Toolkit v1.8.0 to try and flash it. At first it wouldn't find the device, but through device manager I manually installed the usb_driver onto the phone. After this, the toolkit was able to find the phone. I attempted to flash the image, but it ended up staying in fastboot mode. The program then suggested I try to enable "force flash," which I did, and this time it was never able to finish because the phone tried to restart, but went through that "charging to unresponsive" state I described in my first post.
Upon trying to flash it normally again, it looks like maybe the phone has to be unlocked to do this properly? I then tried to unlock with the same program, but in order to do that, I need the power button to confirm I actually want to unlock the phone. So yet again, I need that power button working.
Any ideas/suggestions/solutions would be amazing.
Jellybean on mako means that your phone is in lgnpst/qcpnst mode. Looks like something failed to start and made the bootloader trogger that mode
Sent from my Nexus 4 using xda app-developers app
opssemnik said:
Jellybean on mako means that your phone is in lgnpst/qcpnst mode. Looks like something failed to start and made the bootloader trogger that mode
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Soo, any suggestions?
Str1ngcheese said:
Soo, any suggestions?
Click to expand...
Click to collapse
clean all the contacts with alcohol (not the normal one, the other that i dont remember the name).clean all the corrusion that you can find,let your phone charge for some hours and try again
opssemnik said:
clean all the contacts with alcohol (not the normal one, the other that i dont remember the name).clean all the corrusion that you can find,let your phone charge for some hours and try again
Click to expand...
Click to collapse
I've already done that.
Str1ngcheese said:
The next day I got some tools to open her up. There was pretty extensive corrosion to the motherboard, so using some alcohol I cleaned it all off, rinsed it, and let it dry. I also took apart everything else and cleaned any corrosion. The inside looks brand new.
Click to expand...
Click to collapse
Problem is the power button doesn't work, and the flashing fails. It looks like the flashing fails because the phone isn't unlocked. To unlock, I need the power button. Kinda stuck.
Str1ngcheese said:
I've already done that.
Problem is the power button doesn't work, and the flashing fails. It looks like the flashing fails because the phone isn't unlocked. To unlock, I need the power button. Kinda stuck.
Click to expand...
Click to collapse
the golden contacts on the power button / mobo could be damaged, do a little short till phone turns on
opssemnik said:
the golden contacts on the power button / mobo could be damaged, do a little short till phone turns on
Click to expand...
Click to collapse
How would I go about doing a short?
Str1ngcheese said:
How would I go about doing a short?
Click to expand...
Click to collapse
touch in both pins, something that passes electric current(like a yarn,wires, copper wire, something that passes electrical current).its basicly what the power button does.
Hello i have recently tried to return my phone from cyanogenmod into the stock rom using this thread: "https://forum.xda-developers.com/moto-x-style/general/guide-return-to-stock-relock-bootloader-t3489110" and my phone got stuck in the process while making the command "fastboot flash bootloader bootloader.img". And now my device is stuck on boot loop showing the cyanogenmod loading screen.
Anyway now i found a way to get to stock but for that i need to get my device into fastboot. THE PROBLEM IS that my device can't get now into fastboot! i have tried using adb commands but the adb doesn't recognize the device. I have tried fastboot commands but again it doesn't recognize the device. I also tried button combinations, but it didn't work.
Until the incidence i have used to press the power button+ vol down keys to get into fastboot mode, but now it doesn't work. I suspect that it doesn't work since in order to get into fastboot with the button combination i need to first get the device turned off. But when i connect my device to the charger it shows the battery charging screen and the device is stuck on that screen even if it has disconnected from the charger, and it will keep on that screen until the battery has depleted. I have tried shutting it down using the power button but then my phone gets into a loop with the cyanogenmod loading screen, and even if i turn it off it restarts instead.
p.s I have used to think that my fastboot was deleted but on an other thread i have been told that as long as i see the cyanogenmod loading screen of the OS that means i have a boot-loader.
Please help!
I want to get into Fastboot on my Moto Pure.
Thanks a lot
Eden.
Power down 1st
Try volume down & power key together. That will get you into fastboot directly.
Oops just seen that, my bad, I wont respond anymore.
Sent from my Portable
PassatSport15 said:
Power down 1st
Try volume down & power key together. That will get you into fastboot directly.
Oops just seen that, my bad, I wont respond anymore.
Sent from my Portable
Click to expand...
Click to collapse
Haha, as said. can't power off.
Np thanks for responding!
Anyone got an idea?
u cant poweroff does that means your phone is continuously bootlooping or its just booting but takes a hell lotta time to boot up?
Sagar_1401 said:
u cant poweroff does that means your phone is continuously bootlooping or its just booting but takes a hell lotta time to boot up?
Click to expand...
Click to collapse
I think @edenah is saying it just gets stuck at the loading screen. If the battery discharges all the way and the device is plugged in, the battery symbol shows and after the charger is unplugged, the battery charging doesn't go away until the battery dies again or the power button is pressed (which leaves us right back to where we started)
edenah said:
Hello i have recently tried to return my phone from cyanogenmod into the stock rom using this thread: "https://forum.xda-developers.com/moto-x-style/general/guide-return-to-stock-relock-bootloader-t3489110" and my phone got stuck in the process while making the command "fastboot flash bootloader bootloader.img". And now my device is stuck on boot loop showing the cyanogenmod loading screen.
Anyway now i found a way to get to stock but for that i need to get my device into fastboot. THE PROBLEM IS that my device can't get now into fastboot! i have tried using adb commands but the adb doesn't recognize the device. I have tried fastboot commands but again it doesn't recognize the device. I also tried button combinations, but it didn't work.
Until the incidence i have used to press the power button+ vol down keys to get into fastboot mode, but now it doesn't work. I suspect that it doesn't work since in order to get into fastboot with the button combination i need to first get the device turned off. But when i connect my device to the charger it shows the battery charging screen and the device is stuck on that screen even if it has disconnected from the charger, and it will keep on that screen until the battery has depleted. I have tried shutting it down using the power button but then my phone gets into a loop with the cyanogenmod loading screen, and even if i turn it off it restarts instead.
Click to expand...
Click to collapse
Try this:
Hold power button for 10-20 sek, when screen will turn off hold only vol-(at bootloop screen).
You should flash stock without "oem" commands.
Find how to update bootloader​.
aybarrap1 said:
I think @edenah is saying it just gets stuck at the loading screen. If the battery discharges all the way and the device is plugged in, the battery symbol shows and after the charger is unplugged, the battery charging doesn't go away until the battery dies again or the power button is pressed (which leaves us right back to where we started)
Click to expand...
Click to collapse
Yes thats exactly what i mean.
dzidexx said:
Try this:
Hold power button for 10-20 sek, when screen will turn off hold only vol-(at bootloop screen).
You should flash stock without "oem" commands.
Find how to update bootloader​.
Click to expand...
Click to collapse
tried this, but the device still goes into the cyanogenmod loading screen.
its soft brick but can't be fixed (just thinking any method but no idea man)
get your phone to moto service centre and they can only fix it (or maybe not) caus this is worst case happening to you
if any pro dev read this thread he might be able to answer but badluck (nobody gives a ....)
btw when you connect your phone to pc does it shows unknown device or it just charge the phone?
Sagar_1401 said:
its soft brick but can't be fixed (just thinking any method but no idea man)
get your phone to moto service centre and they can only fix it (or maybe not) caus this is worst case happening to you
if any pro dev read this thread he might be able to answer but badluck (nobody gives a ....)
btw when you connect your phone to pc does it shows unknown device or it just charge the phone?
Click to expand...
Click to collapse
:/
It recognizes it as portable usb device.
And well. I have bought the device in the us but i live outside of the US. so its bit problematic to return it now. Some help could do the trick!
I found SP flash tool and i believe it would do the trick. But i need to get the scatter loading file of the moto pure, but i can't find it anywhere, maybe anyone got the idea how to get that?
edenah said:
:/
It recognizes it as portable usb device.
And well. I have bought the device in the us but i live outside of the US. so its bit problematic to return it now. Some help could do the trick!
I found SP flash tool and i believe it would do the trick. But i need to get the scatter loading file of the moto pure, but i can't find it anywhere, maybe anyone got the idea how to get that?
Click to expand...
Click to collapse
We haven't been able to get the QLoad files for most Moto devices, at least not for the last 2-3 years... Sorry.
Well i have found a way to get the device charged while the screen is off!
If i connect it to my computer while pressing the power button and the vol down button and keep pressing it, the device stays turned off!
Now i'm trying to play with it, to turn the bootloader. so far the classical power and vol combo doesn't work.
edenah said:
Well i have found a way to get the device charged while the screen is off!
If i connect it to my computer while pressing the power button and the vol down button and keep pressing it, the device stays turned off!
Now i'm trying to play with it, to turn the bootloader. so far the classical power and vol combo doesn't work.
Click to expand...
Click to collapse
I am stuck. No button combination works. I suspect that the device isn't really off but the display is just closed. As even to open up the device takes a reallly long press on the power button.
if it got interrupted while flashing bootloader, you're pretty much not going to be able to do anything.
motorola service center is likely the only place that can fix it.
sorry for your luck.
edenah said:
Haha, as said. can't power off.
Np thanks for responding!
Anyone got an idea?
Click to expand...
Click to collapse
ericpeacock79 said:
if it got interrupted while flashing bootloader, you're pretty much not going to be able to do anything.
motorola service center is likely the only place that can fix it.
sorry for your luck.
Click to expand...
Click to collapse
exactly that's what I'm saying but he needs to get his phone to USA as he specified..
only a specialist can help ya
Sagar_1401 said:
exactly that's what I'm saying but he needs to get his phone to USA as he specified..
only a specialist can help ya
Click to expand...
Click to collapse
i see :'(
Ok Thank your guys
I guess its a lost cause.
edenah said:
i see :'(
Ok Thank your guys
I guess its a lost cause.
Click to expand...
Click to collapse
Lost cause? No, probably not... Do you know anyone in the US you trust well enough to receive the phone from repair and ship it to you where ever you are? I believe that is all you need. The US service center cannot ship outside of North America (maybe US), but they can receive packages from anywhere. If you had a US contact that could receive the device and forward it on to you it might be worth it to get it fixed if it is still under warranty, if it isn't, then it might not be worth fixing. Lots of things to consider here.