Related
Hi guys, my HTC is stuck in a bootloop after trying to update Cyanogenmod 13. I fixed the error before (by wiping the data via ADB) but I stupidly decided to re-attempt to install the latest update and guess what? I did it again - only this time, the developer options weren't enabled.
So now I currently have a bootlooped HTC with no authorisation to do anything through the ADB shell, so is there any way to authorise my phone since I can't physically use it?
Cheers
(Also how do I get it back to HTC Sense?)
musta_001 said:
Hi guys, my HTC is stuck in a bootloop after trying to update Cyanogenmod 13. I fixed the error before (by wiping the data via ADB) but I stupidly decided to re-attempt to install the latest update and guess what? I did it again - only this time, the developer options weren't enabled.
So now I currently have a bootlooped HTC with no authorisation to do anything through the ADB shell, so is there any way to authorise my phone since I can't physically use it?
Click to expand...
Click to collapse
Just boot into bootloader by holding vol down as it bootloops. Then boot into recovery (TWRP?) and wipe data there.
Or re-flash CM or restore TWRP backup, if needed.
musta_001 said:
(Also how do I get it back to HTC Sense?)
Click to expand...
Click to collapse
Just flash a Sense ROM. Or restore your TWRP backup from before you flashed CM, or from the stock nandroid collection.
redpoint73 said:
Just boot into bootloader by holding vol down as it bootloops.
Click to expand...
Click to collapse
Yeah the problem is that when I try doing that, the phone resets and goes into some black flashing screen now in 4-5 second intervals. I also tried booting it into bootloader using my computer but as I said before, it won't let me due to USB debugging not being enabled beforehand
musta_001 said:
Yeah the problem is that when I try doing that, the phone resets and goes into some black flashing screen now in 4-5 second intervals. I also tried booting it into bootloader using my computer but as I said before, it won't let me due to USB debugging not being enabled beforehand
Click to expand...
Click to collapse
Doesn't matter whether USB debugging is on or not, since adb commands only work in OS or recovery (neither of which are available). Fastboot commands only work in bootloader-fastboot mode (debugging not needed). So if you can't get into bootloader, you're pretty much screwed on both counts (adb and fastboot).
I've seen a couple reports like this on the forum, where trying to get into bootloader results in black screen, then a reboot. Don't think there was ever a solution found, sorry to say.
redpoint73 said:
Doesn't matter whether USB debugging is on or not, since adb commands only work in OS or recovery (neither of which are available). Fastboot commands only work in bootloader-fastboot mode (debugging not needed). So if you can't get into bootloader, you're pretty much screwed on both counts (adb and fastboot).
I've seen a couple reports like this on the forum, where trying to get into bootloader results in black screen, then a reboot. Don't think there was ever a solution found, sorry to say.
Click to expand...
Click to collapse
Well looks like I found the fix XD
I held down the power button and BOTH of the volume buttons at the same so that the phone resets. I kept hold of it until the phone booted to the lockscreen. From there I enabled USB debugging and went to flash the stock ROM.
musta_001 said:
Well looks like I found the fix XD
I held down the power button and BOTH of the volume buttons at the same so that the phone resets. I kept hold of it until the phone booted to the lockscreen. From there I enabled USB debugging and went to flash the stock ROM.
Click to expand...
Click to collapse
Very interesting. That combo is known as the "battery reset" or something to that effect. I'm not sure why/how that would have helped your problem, but I'm glad to see something did!
I suppose the moral of the story, try all button combos before giving up!
Hello guys, I just got a Pixel 3XL from somebody and I thought I could make it to work, but now I'm stucked. The phone is stucked in fastboot and the bootloader is LOCKED. I tried to unlock it using GUIDE for Google Pixel 3 XL unlock bootloader, but I cannot do this task 100% because I cannot enable OEM unlock and USB debugging since the phone is stucked in fastbood mode. Also, if I try to get into recovery mode, when I press the power button to get into recovery, the phone turns off. I ust want to make it stock.
Any idea how to solve this? Thank you
try sideloading the full OTA.
https://developers.google.com/android/ota
robertoancini51 said:
Hello guys, I just got a Pixel 3XL from somebody and I thought I could make it to work, but now I'm stucked. The phone is stucked in fastboot and the bootloader is LOCKED. I tried to unlock it using GUIDE for Google Pixel 3 XL unlock bootloader, but I cannot do this task 100% because I cannot enable OEM unlock and USB debugging since the phone is stucked in fastbood mode. Also, if I try to get into recovery mode, when I press the power button to get into recovery, the phone turns off. I ust want to make it stock.
Any idea how to solve this? Thank you
Click to expand...
Click to collapse
The answer is the same as in your other thread. If you cannot get into recovery mode and your bootloader is locked there is nothing you can do. The mystery is how you lost recovery with a locked bootloader... it may have been unlocked at one time and someone re-locked it?
v12xke said:
The answer is the same as in your other thread. If you cannot get into recovery mode and your bootloader is locked there is nothing you can do. The mystery is how you lost recovery with a locked bootloader... it may have been unlocked at one time and someone re-locked it?
Click to expand...
Click to collapse
that's the mistery. so I cannot do nothing with the phone? Is no any solution to put the recovery mode back into the phone to work?
robertoancini51 said:
that's the mistery. so I cannot do nothing with the phone? Is no any solution to put the recovery mode back into the phone to work?
Click to expand...
Click to collapse
Not if you can't fastboot the boot.img there isn't. Like the others said, if you can't get into stock recovery to side load the OTA, your kinda hosed.
robertoancini51 said:
that's the mistery. so I cannot do nothing with the phone? Is no any solution to put the recovery mode back into the phone to work?
Click to expand...
Click to collapse
No, nothing you can do because you cannot fastboot flash any partition when the bootloader is locked, and without a working recovery you cannot use adb to sideload an OTA. My guess is your friend at one time had the bootloader unlocked but he later locked it back before giving it to you. Once the bootloader is unlocked it should never be locked again... unless you know exactly what you are doing and have good reason to do so. If you have tried multiple times to unlock the bootloader using fastboot -and- exhausted all means of booting to recovery (you are positive you know how to get there and cannot) then there is no way to recover. Until one of these two things changes you cannot get back in. Sorry man!
Badger50 said:
Not if you can't fastboot the boot.img there isn't. Like the others said, if you can't get into stock recovery to side load the OTA, your kinda hosed.
Click to expand...
Click to collapse
ok, thank you
v12xke said:
No, nothing you can do because you cannot fastboot flash any partition when the bootloader is locked, and without a working recovery you cannot use adb to sideload an OTA. My guess is your friend at one time had the bootloader unlocked but he later locked it back before giving it to you. Once the bootloader is unlocked it should never be locked again... unless you know exactly what you are doing and have good reason to do so. If you have tried multiple times to unlock the bootloader using fastboot -and- exhausted all means of booting to recovery (you are positive you know how to get there and cannot) then there is no way to recover. Until one of these two things changes you cannot get back in. Sorry man!
Click to expand...
Click to collapse
I just cannot believe that the phone is unusable
robertoancini51 said:
I just cannot believe that the phone is unusable
Click to expand...
Click to collapse
Just to be sure I am reading this right, instead of seeing the "no command" screen when you toggle the smart menu option to recovery and hitting the power button, the device shuts down?
sliding_billy said:
Just to be sure I am reading this right, instead of seeing the "no command" screen when you toggle the smart menu option to recovery and hitting the power button, the device shuts down?
Click to expand...
Click to collapse
Yes
robertoancini51 said:
Yes
Click to expand...
Click to collapse
You mention not being able to toggle OEM unlock or USB debugging, but are you sure they are not already toggle? Have you tried locking or unlocking the bootloader from fastboot (hopefully you can see the device on your computer when plugged in)? Your issue reminded me of another thread https://forum.xda-developers.com/showpost.php?p=78277194&postcount=260 where it looked like an unlock only partially worked. I assume you are not the registered owner and cannot contact Google about the issue.
sliding_billy said:
You mention not being able to toggle OEM unlock or USB debugging, but are you sure they are not already toggle? Have you tried locking or unlocking the bootloader from fastboot (hopefully you can see the device on your computer when plugged in)? Your issue reminded me of another thread https://forum.xda-developers.com/showpost.php?p=78277194&postcount=260 where it looked like an unlock only partially worked. I assume you are not the registered owner and cannot contact Google about the issue.
Click to expand...
Click to collapse
I'm not sure if they are already toggle. Yes, I've tried to lock/unlock bootloader from fastboot, but nothing. The PC sees it from device manager. No,I'm not registered.
robertoancini51 said:
I'm not sure if they are already toggle. Yes, I've tried to lock/unlock bootloader from fastboot, but nothing. The PC sees it from device manager. No,I'm not registered.
Click to expand...
Click to collapse
Might be worth posting something on the Google forum. If an agent isn't checking registration, you might get some ideas. The only thing else I can think is that there may be some key combination (vol down or up and hold) when pressing the power button to get to recovery to keep it from shutting down. Good luck.
sliding_billy said:
Might be worth posting something on the Google forum. If an agent isn't checking registration, you might get some ideas. The only thing else I can think is that there may be some key combination (vol down or up and hold) when pressing the power button to get to recovery to keep it from shutting down. Good luck.
Click to expand...
Click to collapse
I Have written to ghem, I wait an answer from them. I will try some combination and come back with an answer
i have the same problem
robertoancini51 said:
I Have written to ghem, I wait an answer from them. I will try some combination and come back with an answer
Click to expand...
Click to collapse
who did you write to? can you share please? also if you manage to solve the problem, please share the solution.
many thanks,
Cant you take the back of and use EDL Mode? its qualcomm so its available.? wheres all the master techys in the pixel thread?You can push the entire factory image whether its locked or unlocked with EDL.
---------- Post added at 04:56 PM ---------- Previous post was at 04:50 PM ----------
https://www.leakite.com/revised-how-to-unbrick-qualcomm-android/
Remember to change any images to googles.
Hi,
I followed this guide on how to root the pixel 2: "androidcentral.com/how-root-google-pixel-2" and finished all the steps. But when running step 11 it got stuck in a boot loop due to some software issues with the patched image I assume.
I've tried opening the phone in fastboot mode and then connecting with ADB, but it seems I cannot find my device since USB-debugging is not turned on.
Any ideas of how this can be solved? Or am I screwed?
Try rebooting into recovery. When you see the Android laying down and I believe it says no command, press the up button. This should bring you to another menu where ADB sideload is an option. you could then download the appropriate OTA from Google and sideload it to the phone.
Larzzzz82 said:
Try rebooting into recovery. When you see the Android laying down and I believe it says no command, press the up button. This should bring you to another menu where ADB sideload is an option. you could then download the appropriate OTA from Google and sideload it to the phone.
Click to expand...
Click to collapse
Thanks for your reply. I pressed "On/off" button + volume down and got into menu with recovery mode. But selecting recovery mode with "on/off" button and then clicking volume up just brings me to a view with the google logo showing and then the phone turns off. I can't seem to access menu with ADB sideload unfortunately...
helpless_user said:
Thanks for your reply. I pressed "On/off" button + volume down and got into menu with recovery mode. But selecting recovery mode with "on/off" button and then clicking volume up just brings me to a view with the google logo showing and then the phone turns off. I can't seem to access menu with ADB sideload unfortunately...
Click to expand...
Click to collapse
when in Bootloader mode (where it shows your "baseband version" and such), you actually use the volume button to change around the different options to boot, and then the "on/off" button to select.
But it looks like you get it to show the red "recovery mode" and, I imagine, you intuitively pressed the "on/off button" to select it, but in the unlikelihood that that is the case, make sure you are not holding or pressing or "....clicking volume up" button while it's booting; that's probably where you're going wrong....
only once you're in the stock recovery mode -- with the android lying down, dead, and a red exclamation point coming out of it -- is where you press the "volume up" and power button together to see the options...
good luck and hope this helps....
simplepinoi177 said:
when in Bootloader mode (where it shows your "baseband version" and such), you actually use the volume button to change around the different options to boot, and then the "on/off" button to select.
But it looks like you get it to show the red "recovery mode" and, I imagine, you intuitively pressed the "on/off button" to select it, but in the unlikelihood that that is the case, make sure you are not holding or pressing or "....clicking volume up" button while it's booting; that's probably where you're going wrong....
only once you're in the stock recovery mode -- with the android lying down, dead, and a red exclamation point coming out of it -- is where you press the "volume up" and power button together to see the options...
good luck and hope this helps....
Click to expand...
Click to collapse
I tried this and I never get to the dead android screen. I just get to a screen that says that my bootloader is unlocked and then the Google logo is showing.
helpless_user said:
I tried this and I never get to the dead android screen. I just get to a screen that says that my bootloader is unlocked and then the Google logo is showing.
Click to expand...
Click to collapse
Hmmmm...it sounds like something's wrong with your boot partition, then -- that's where the recovery resides. I suggest re-downloading the latest Full Factory image (from Google's developers site), editing flash-all to remove the "-w" and "exit" at the end, then running the flash-all once again on your device.
....after reading your OP, one key thing to keep in mind is that, in Bootloader Mode, you use "fastboot" commands while you use "adb" commands when within the OS or recovery....
And, for future reference, it would be better (most likely) if you wish to root the taimen for you to follow THIS GUIDE: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418 .
helpless_user said:
Thanks for your reply. I pressed "On/off" button + volume down and got into menu with recovery mode. But selecting recovery mode with "on/off" button and then clicking volume up just brings me to a view with the google logo showing and then the phone turns off. I can't seem to access menu with ADB sideload unfortunately...
Click to expand...
Click to collapse
In fastboot you can boot to a recovery.img; fastboot boot twrp.img
Download TWRP .img here.
(that recovery menu allows adb mode also).
Here you can(re)flash zip/image etc.
Format /data to ensure it is not encrypted.
For example, flash the extracted images of the OTA images from Google.
simplepinoi177 said:
Hmmmm...it sounds like something's wrong with your boot partition, then -- that's where the recovery resides. I suggest re-downloading the latest Full Factory image (from Google's developers site), editing flash-all to remove the "-w" and "exit" at the end, then running the flash-all once again on your device.
....after reading your OP, one key thing to keep in mind is that, in Bootloader Mode, you use "fastboot" commands while you use "adb" commands when within the OS or recovery....
And, for future reference, it would be better (most likely) if you wish to root the taimen for you to follow THIS GUIDE: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418 .
Click to expand...
Click to collapse
Thank you very much!! Running fastboot helped me do a factory reset and now my phone is working again! Thought my phone was bricked so this is a relief.
helpless_user said:
Thank you very much!! Running fastboot helped me do a factory reset and now my phone is working again! Thought my phone was bricked so this is a relief.
Click to expand...
Click to collapse
I'm real happy you got it back up and running!
Yeah, I'm not agreeing with all of what Google's doing now (in concerns with the Pixel 4 [i.e. removing unlimited original quality storage]), but they really did well with the whole "Bootloader Mode" where you can feel a bit more secure and confident that, as long as you have access to Bootloader Mode and can successfully connect your device, you're not too far gone and definitely bricked beyond hope! It's not so hopeless as with devices before and what the term "bricking" truly applies to....
Happy to have helped!
Not able to figure out the exact fix
helpless_user said:
Thank you very much!! Running fastboot helped me do a factory reset and now my phone is working again! Thought my phone was bricked so this is a relief.
Click to expand...
Click to collapse
@OP, I am still stuck with the exact same issue. How did you exactly fix it? After running the solution given, I'm back at the infinite logo screen again.
Edit: It worked, thank you so much! This is a life saver.
simplepinoi177 said:
I'm real happy you got it back up and running!
Yeah, I'm not agreeing with all of what Google's doing now (in concerns with the Pixel 4 [i.e. removing unlimited original quality storage]), but they really did well with the whole "Bootloader Mode" where you can feel a bit more secure and confident that, as long as you have access to Bootloader Mode and can successfully connect your device, you're not too far gone and definitely bricked beyond hope! It's not so hopeless as with devices before and what the term "bricking" truly applies to....
Happy to have helped!
Click to expand...
Click to collapse
Hi i have the same issue with different device lenovo tab m10 tbx605L and i cant boot the recovery.img it throws me this error.Can u give me any ideas?
helpless_user said:
Hi,
I followed this guide on how to root the pixel 2: "androidcentral.com/how-root-google-pixel-2" and finished all the steps. But when running step 11 it got stuck in a boot loop due to some software issues with the patched image I assume.
I've tried opening the phone in fastboot mode and then connecting with ADB, but it seems I cannot find my device since USB-debugging is not turned on.
Any ideas of how this can be solved? Or am I screwed?
Click to expand...
Click to collapse
Did you install TWRP before rooting? If you did, that is the source of the bootloop. Our root guides here are much simpler than the one you provided the address to. The article in question is also out of date. Current versions of TWRP and Magisk don't play nice together. You need to BOOT TWRP using fastboot instead of installing it.
Copying the latest Magisk package to your internal storage, then renaming it to uninstall.zip and flashing it through TWRP should remove Magisk and resolve the bootloop. If that doesn't work, flashing the last stock package should.
EDIT: Quoted the wrong poster. My reply is an answer to the quoted poster instead of the poster who revived a dead thread with a question for a totally different device.
Strephon Alkhalikoi said:
Did you install TWRP before rooting? If you did, that is the source of the bootloop. Our root guides here are much simpler than the one you provided the address to. The article in question is also out of date. Current versions of TWRP and Magisk don't play nice together. You need to BOOT TWRP using fastboot instead of installing it.
Copying the latest Magisk package to your internal storage, then renaming it to uninstall.zip and flashing it through TWRP should remove Magisk and resolve the bootloop. If that doesn't work, flashing the last stock package should.
Click to expand...
Click to collapse
unfortunately there is not an exact version of twrp recovery available for my device lenovo (tbx605L) even when i try to boot the stock recovery.img , it says FAILED (remote : unknown command) do you know what is causing this error??
safaan0313 said:
unfortunately there is not an exact version of twrp recovery available for my device lenovo (tbx605L) even when i try to boot the stock recovery.img , it says FAILED (remote : unknown command) do you know what is causing this error??
Click to expand...
Click to collapse
I didn't realize you had replied to a thread that was two years old AND for the wrong device. Ask in the Lenovo section. This is the Pixel 2 XL section and advice given here is not applicable to you.
Strephon Alkhalikoi said:
I didn't realize you had replied to a thread that was two years old AND for the wrong device. Ask in the Lenovo section. This is the Pixel 2 XL section and advice given here is not applicable to you.
Click to expand...
Click to collapse
Hmm well thanks for your indirect F**k off
safaan0313 said:
Hmm well thanks for your indirect F**k off
Click to expand...
Click to collapse
I'm not sure you're aware of this, but not all devices are the same. Case in point: Samsung. How do you use fastboot commands on a Samsung device? Answer: You can't as Samsung doesn't support fastboot.
But thank you for making your expectations clear. Apparently, according to you, I should be able to figure out your problem despite not owning your device. It doesn't work that way. The only reason I know the answer to the question I posted in the previous paragraph is because I own a Samsung device.
Seriously, you getting bent out of shape at me because of your own screw-up is laughable.
Strephon Alkhalikoi said:
I'm not sure you're aware of this, but not all devices are the same. Case in point: Samsung. How do you use fastboot commands on a Samsung device? Answer: You can't as Samsung doesn't support fastboot.
But thank you for making your expectations clear. Apparently, according to you, I should be able to figure out your problem despite not owning your device. It doesn't work that way. The only reason I know the answer to the question I posted in the previous paragraph is because I own a Samsung device.
Seriously, you getting bent out of shape at me because of your own screw-up is laughable.
Click to expand...
Click to collapse
Right I knew that.I am sorry.I was so damn angry at my own mistake.I AM S O R R Y.But off the record I just repaired my tab
LE2125 Installed but when TWRP loads none of the Dialog works, its locked up.
weeems said:
LE2125 Installed but when TWRP loads none of the Dialog works, its locked up.
Click to expand...
Click to collapse
How did you install twrp and is it 3.6.0
MrSteelX said:
How did you install twrp and is it 3.6.0
Click to expand...
Click to collapse
I used fastboot flash and it is 3.6.0 yes
weeems said:
I used fastboot flash and it is 3.6.0 yes
Click to expand...
Click to collapse
Wrong installation method
weeems said:
I used fastboot flash and it is 3.6.0 yes
Click to expand...
Click to collapse
You have to use fastboot boot twrp. Now you must install stock kernel and start over.
This seems similar to something that has happened to me. I purchased this phone with the intent of flashing Lineage-MircoG on it. TWRP-3.6.0_11-0-lemonadep.img has been installed, and was working on the phone. I was in the process of doing factory wipes so that I could flash LOS and for some reason, the touch screen stopped working. I can interact with the power button but can't swipe to unlock. I can't seem to find any button combination that will reboot the device either. I'm not sure what I did wrong, but I could really use a break down of how to fix it. Thank you in advance.
EDIT: Was able to get to fastboot by holding down power, volume up, and volume down at same time. Still unable to interact with touch, however. Computer seems to recognize a device is plugged in but Internal Storage is completely empty, and thus far my attempts to drag the LineageOS image to the device have been unsuccessful.
HellsBells7 said:
This seems similar to something that has happened to me. I purchased this phone with the intent of flashing Lineage-MircoG on it. TWRP-3.6.0_11-0-lemonadep.img has been installed, and was working on the phone. I was in the process of doing factory wipes so that I could flash LOS and for some reason, the touch screen stopped working. I can interact with the power button but can't swipe to unlock. I can't seem to find any button combination that will reboot the device either. I'm not sure what I did wrong, but I could really use a break down of how to fix it. Thank you in advance.
EDIT: Was able to get to fastboot by holding down power, volume up, and volume down at same time. Still unable to interact with touch, however. Computer seems to recognize a device is plugged in but Internal Storage is completely empty, and thus far my attempts to drag the LineageOS image to the device have been unsuccessful.
Click to expand...
Click to collapse
Install stock rom and boot it. Touch will be back then temp boot twrp and install LOS. After installing then you do format data.
MrSteelX said:
Install stock rom and boot it. Touch will be back then temp boot twrp and install LOS. After installing then you do format data.
Click to expand...
Click to collapse
Can you point me to a guide to doing so? I'm afraid I don't know, first time I've ever screwed up this bad. Not even sure where to get files or anything of that nature, Or how to get them onto the phone via fastboot (seems to be the only way to interact)
EDIT: Will this help me?
HellsBells7 said:
This seems similar to something that has happened to me. I purchased this phone with the intent of flashing Lineage-MircoG on it. TWRP-3.6.0_11-0-lemonadep.img has been installed, and was working on the phone. I was in the process of doing factory wipes so that I could flash LOS and for some reason, the touch screen stopped working. I can interact with the power button but can't swipe to unlock. I can't seem to find any button combination that will reboot the device either. I'm not sure what I did wrong, but I could really use a break down of how to fix it. Thank you in advance.
EDIT: Was able to get to fastboot by holding down power, volume up, and volume down at same time. Still unable to interact with touch, however. Computer seems to recognize a device is plugged in but Internal Storage is completely empty, and thus far my attempts to drag the LineageOS image to the device have been unsuccessful.
Click to expand...
Click to collapse
Install stock rom and boot it. Touch will be back then temp boot twrp and install LOS. After installing then you do format data.
HellsBells7 said:
Can you point me to a guide to doing so? I'm afraid I don't know, first time I've ever screwed up this bad. Not even sure where to get files or anything of that nature, Or how to get them onto the phone via fastboot (seems to be the only way to interact)
EDIT: Will this help me?
Click to expand...
Click to collapse
Yes
OK, thanks for being patient with me. I have the program downloaded to my computer but I don't seem to be able to get my phone into the prescribed EDL mode. Fastboot, yes, but not EDL. The fastboot command from my terminal window isn't working, and obviously I'm too far gone for adb at this point.
Is there a combination of hardware keys that will force EDL? Or perhaps an easier way that I'm missing altogether?
Again, thank you for helping me. I don't remember having this much trouble with the 6T.
From fastboot. Temp boot twrp and have it boot to edl. If no touch, can you plug in a mouse. If all fails, with phone off hold vol up and down together and plug in USB cable
I got it back on to stock! Thanks for everyone's help.
i need some help since im not good with technical stuff but my phone got into a boot looping situation after my keychain with a magnetic tag dropped on the phone.
Welcome to XDA.
Factory reset.
If that fails, open and inspect for displaced connectors.
If it still fails to boot, reflash to last known working rom.
If all that fails there's hardware damage from the impact... high G loading can damage the mobo, solder joints as well as cause internal damage to chipsets.
blackhawk said:
Welcome to XDA.
Factory reset.
If that fails, open and inspect for displaced connectors.
If it still fails to boot, reflash to last known working rom.
If all that fails there's hardware damage from the impact... high G loading can damage the mobo, solder joints as well as cause internal damage to chipsets.
Click to expand...
Click to collapse
tried the factory reset didnt work well.
but i can still access the fast boot mode.
> tried the recovery mode : none of the options there worked out.
> i want to try an reflash to last known working rom but i am no sure how to do that.
>i just hope the last possible chance isnt true but ill be hoping for the best.
How hard was it hit?
it didnt damage the screen, its almost the hight of 18mm
wargey said:
it didnt damage the screen, its almost the hight of 18mm
Click to expand...
Click to collapse
Very strange... maybe the boot loop is unrelated to the impact.
The only thing that was attached with the key chain was a magnet used for location like a smart tag when that hit the phone stopped working and tried to turn it on them went on s bootloop sequence and doesn't go after the splash logo
wargey said:
The only thing that was attached with the key chain was a magnet used for location like a smart tag when that hit the phone stopped working and tried to turn it on them went on s bootloop sequence and doesn't go after the splash logo
Click to expand...
Click to collapse
Try a factory reset and go from there.
If that failed inspect the hardware before trying to flash it... make sure the battery is good.
As best as I know a normal magnet can't do this. I don't let my phone near MRI and CAT scan (ionizing radiation) units though.
I'll try factory reset through recovery mode first... I think.
If factory reset doesn't work, try to do an ADB sideload on the recovery.
hi again.
tried the factory reset didnt work out but how to do the ADB sideload ?
batuken said:
If factory reset doesn't work, try to do an ADB sideload on the recovery.
Click to expand...
Click to collapse
hi again.
tried the factory reset didnt work out but how to do the ADB sideload ?
wargey said:
hi again.
tried the factory reset didnt work out but how to do the ADB sideload ?
Click to expand...
Click to collapse
Boot your phone to recovery. While on the language selection screen, type this on cmd:
adb sideload <rom>.zip
Make sure you have fastboot and ADB drivers installed on your PC.
batuken said:
Boot your phone to recovery. While on the language selection screen, type this on cmd:
adb sideload <rom>.zip
Make sure you have fastboot and ADB drivers installed on your PC.
Click to expand...
Click to collapse
tried the cmd but it didnt work saying that it cannot read it
tried to flashboot and i tried the adb and both is not working
i also tried to strip the payload but it didnt work at all.
so idk i guess i am out of option in trying to recover.
i hope anyone can help me in finding other ideas
Is the battery good?
blackhawk said:
Is the battery good?
Click to expand...
Click to collapse
when i start pluging in the charger it starts to boot loop also
but yes it shows that its charging so i think the battery is good
wargey said:
when i start pluging in the charger it starts to boot loop also
but yes it shows that its charging so i think the battery is good
Click to expand...
Click to collapse
Sounds like a hardware.
blackhawk said:
Sounds like a hardware.
Click to expand...
Click to collapse
that sounds not good then i guess ill have to send it back to the company
Thanks again for the help i really tried everything on software side but with no success even i managed to buy the firehose and and showed me that error process fail