<SOLVED>
I am still pretty new to Android and modding so be gentle..............
Should have know better. Flashed the latest Omega Kernel on my 6T while watching the kiddos practice for an upcoming belt test. I know I don't mulit task!
Flashed the Android 10 version on my Android 9 phone. Realized what I did when it would go past the bootloader unlocked warning. Eventually it went to the qualcomm dump mode then rebooted.
Now I can't get it to do anything. It is stuck on that screen. Power button does nothing. My theory is if I can get into recovery I can just flash the correct previous version of Omega that is on the phone.....but without a working power button I am stuck. Computer does not even see the phone when I plug it in.
What now?
Many thanks in advance.
Use the MSM Tool method to un brick your phone. Look for the forum in the Roms, Kernels... Section.
You're going to loose all data.
I will get over losing my data. I don't have a windows machine at the house. I will have to go to our shop to use that horrible OS. Thanks for the intel.
You can fix this issue in minutes without requiring to run MSM Tool or lose any data. I faced a similar issue myself few days ago and got it running back again by doing the follows:
Boot your device into fastboot mode, download the latest boot.img (stock or any other kernel) and TWRP and type these in command line:
1) Fastboot flash boot.img
2) Fastboot boot twrp.img
3) Your device will boot into TWRP Recovery, so flash TWRP installer zip so it sticks.
4) Reboot to recovery again and flash Magisk or Full Rom OTA.
You should be fine then.
Anwar Syed said:
You can fix this issue in minutes without requiring to run MSM Tool or lose any data. I faced a similar issue myself few days ago and got it running back again by doing the follows:
Boot your device into fastboot mode, download the latest boot.img (stock or any other kernel) and TWRP and type these in command line:
1) Fastboot flash boot.img
2) Fastboot boot twrp.img
3) Your device will boot into TWRP Recovery, so flash TWRP installer zip so it sticks.
4) Reboot to recovery again and flash Magisk or Full Rom OTA.
You should be fine then.
Click to expand...
Click to collapse
Thanks, but you missed the part where my power button is not working. The phone is stuck on the 'bootloader unlocked' warning message and the power button does nothing. No way to boot into recovery or fastboot.
PattayaGlock said:
Thanks, but you missed the part where my power button is not working. The phone is stuck on the 'bootloader unlocked' warning message and the power button does nothing. No way to boot into recovery or fastboot.
Click to expand...
Click to collapse
Is your power button broken by any chance?
If it isn't, then hold volume up + power button for a few minutes and it will reboot to Fastboot screen.
Edit: Also try volume down + power button if volume up does nothing. Make sure you hold either of the combination for a few minutes until you get a haptic feedback. Google "Boot OnePlus 6T into Fastboot mode" and follow the instructions there. Once in Fastboot, follow what I wrote in my previous reply.
Anwar Syed said:
Is your power button broken by any chance?
If it isn't, then hold volume up + power button for a few minutes and it will reboot to Fastboot screen.
Edit: Also try volume down + power button if volume up does nothing. Make sure you hold either of the combination for a few minutes until you get a haptic feedback. Google "Boot OnePlus 6T into Fastboot mode" and follow the instructions there. Once in Fastboot, follow what I wrote in my previous reply.
Click to expand...
Click to collapse
Holding the power button does nothing.
Power + down volume does nothing.
Discovered power + up button WILL turn the phone off. It also just brings it back to the "bootloader unlocked" warning page. It won't bring it to fastboot mode.
Makes sense as recovery is now part of the boot.img instead of a partition. I am assuming fastboot is also part of the boot.img. If that is the case there is no way to get into fastboot with an Android 10 kernel on my Android 9 phone. ..... I think
PattayaGlock said:
Holding the power button does nothing.
Power + down volume does nothing.
Discovered power + up button WILL turn the phone off. It also just brings it back to the "bootloader unlocked" warning page. It won't bring it to fastboot mode.
Makes sense as recovery is now part of the boot.img instead of a partition. I am assuming fastboot is also part of the boot.img. If that is the case there is no way to get into fastboot with an Android 10 kernel on my Android 9 phone. ..... I think
Click to expand...
Click to collapse
Go through my reply history. I was on 9.0.17 and had flash RadioActive kernel which was based on/for Android 10 and went into crash dump mode. Doing those steps resolved it.
Both volume buttons + power for a hard shutdown [emoji6]
Anwar Syed said:
(...) Make sure you hold either of the combination for a few minutes until you get a haptic feedback.(...)
Click to expand...
Click to collapse
Minutes? [emoji50] We don't want users dislocating their fingers [emoji51]
Wrapped with delicious Fajita [emoji896]
Timmmmaaahh said:
Both volume buttons + power for a hard shutdown [emoji6]
Minutes? [emoji50] We don't want users dislocating their fingers [emoji51]
Wrapped with delicious Fajita [emoji896]
Click to expand...
Click to collapse
Should've said seconds, my bad, but your reply is hilarious...lmao xD
Turns out holding all 3 buttons did the trick....in a weird FUBAR kind of way.
1st time it popped into fastboot. Figured what the hell, tried to reboot, nope.
2nd time just booted back to the warning screen.....okay, freaked out again.
Got back into fastboot, flashed twrp, rebooted to the warning screen. SH*T!
Got back to fastboot, flashed twrp, damn thing booted into the os as if nothing had ever happened.
Held my breath, downloaded the correct kernel, rebooted to recovery, flashed, rebooted system. Everything is good.
Guess the a/b partition maybe?
Anyway, problem solved, headache over, NO DATA LOST.
Thank you everyone!
All 3 buttons did it....in a wierd FUBAR kind of way.
1st time fastboot popped up. Figured I would try reboot, nope.
2nd time just booted back to warning screen, uh oh.
3rd time fastboot, flash twrp, booted back to warning screen.
4th time fastboot, twrp, booted into OS like nothing ever happened.
Held my breath, downloaded the correct kernel update, recovery, flashed, rebooted and I am good to go.
Thanks everyone for your help!
Sorry for the dual post, I am in BOTARD mode apparently. Didn't see the post and thought I forgot to send......missed page 1 of 2!
PattayaGlock said:
Guess the a/b partition maybe?
Click to expand...
Click to collapse
That would be my guess. It should just switch to the functional slot if the other isn't (properly) booting but I've experienced this system to behave quite erratically. I presume these are childhood diseases of a relatively new Android partitioning system.
Back in the 'old' system all you should've done was boot to recovery (which couldn't be corrupted by the OS!) and dirty flash either a working kernel or the original (stock) ROM that includes the kernel.
Anyway, glad you retained all your data! Thanks for updating the title and OP with a solved tag
PattayaGlock said:
<SOLVED>
I am still pretty new to Android and modding so be gentle..............
Should have know better. Flashed the latest Omega Kernel on my 6T while watching the kiddos practice for an upcoming belt test. I know I don't mulit task!
Flashed the Android 10 version on my Android 9 phone. Realized what I did when it would go past the bootloader unlocked warning. Eventually it went to the qualcomm dump mode then rebooted.
Now I can't get it to do anything. It is stuck on that screen. Power button does nothing. My theory is if I can get into recovery I can just flash the correct previous version of Omega that is on the phone.....but without a working power button I am stuck. Computer does not even see the phone when I plug it in.
What now?
Many thanks in advance.
Click to expand...
Click to collapse
hello
I have the same problem with my phone, I have read all your comments about how to fix it, but I didn't understand how you fixed it, only holding the 3 bottons? and waiting to get into recovery or what?
tnx
My phone is sony xperia z1. I rooted this phone. and flashed wrong kernel after that the phone was not responding. Even though I pressed the power button, nothing appeared on the screen, please help me
Related
I recently got the update for 4.4 notification, clicked it but then the installation froze on a picture of android with an exclamation in his belly.
After that I could no longer boot to bootloader or recovery.
I tried fastboot but I cant not install the drivers as I cant boot to bootloader.
So I tried NRT and managed to get my recovery back (TWRP), but still no bootloader.
I have the option to return to stock on NRT but I am afraid it will fail and brick my N7.
I have SuperSU, flashify and TWRP apps running now with TWRP recovery also bootable.
How can I get my bootloader back?
Siddy1200 said:
I recently got the update for 4.4 notification, clicked it but then the installation froze on a picture of android with an exclamation in his belly.
After that I could no longer boot to bootloader or recovery.
I tried fastboot but I cant not install the drivers as I cant boot to bootloader.
So I tried NRT and managed to get my recovery back (TWRP), but still no bootloader.
I have the option to return to stock on NRT but I am afraid it will fail and brick my N7.
I have SuperSU, flashify and TWRP apps running now with TWRP recovery also bootable.
How can I get my bootloader back?
Click to expand...
Click to collapse
Hi, Siddy1200...
If you had no bootloader... nothing would work... at all.
The bootloader underpins everything you do with your Nexus 7. Nothing happens without one... in which case , you'd be effectively HARDBRICKED.
The fact that stuff is working indicates that your bootloader is fine.
To access the bootloader manually... shut down the Nexus 7 completely.
Press and hold the VOL DOWN button...
Whilst holding, press the POWER ON button, for around 5-10 seconds...
You should now boot into the bootloader.
This key press sequence should also work if you CAN'T shut down the Nexus 7 normally... for example, if you're bootlooping. I've had a few scary moments myself in the past, and the VOL DOWN+hold, POWER ON sequence has always thrown me back into the bootloader...
Rgrds,
Ged.
GedBlake said:
Hi, Siddy1200...
If you had no bootloader... nothing would work... at all.
The bootloader underpins everything you do with your Nexus 7. Nothing happens without one... in which case , you'd be effectively HARDBRICKED.
The fact that stuff is working indicates that your bootloader is fine.
To access the bootloader manually... shut down the Nexus 7 completely.
Press and hold the VOL DOWN button...
Whilst holding, press the POWER ON button, for around 5-10 seconds...
You should now boot into the bootloader.
This key press sequence should also work if you CAN'T shut down the Nexus 7 normally... for example, if you're bootlooping. I've had a few scary moments myself in the past, and the VOL DOWN+hold, POWER ON sequence has always thrown me back into the bootloader...
Rgrds,
Ged.
Click to expand...
Click to collapse
Thanks for the reply Greg.
I can't boot to boot loader, that means when I power on with vol- pressed, then select boot loader and press power , it doesn't work. The screen flashes for a second and it is back to the previous screen to where I can choose restart, recovery, boot loader,etc.
This also happened with recovery but I fixed it, now I'm trying to fix the bootloader
Siddy1200 said:
Thanks for the reply Greg.
I can't boot to boot loader, that means when I power on with vol- pressed, then select boot loader and press power , it doesn't work. The screen flashes for a second and it is back to the previous screen to where I can choose restart, recovery, boot loader,etc.
This also happened with recovery but I fixed it, now I'm trying to fix the bootloader
Click to expand...
Click to collapse
Apologies, Siddy1200... but I'm a little confused... based upon my reading of your post... I think you're already in the bootloader!!.
"...it is back to the previous screen to where I can choose restart, recovery, boot loader,etc..."
The bootloader features a green android, lying on its back, with it's belly open - some really tiny text at the lower left hand side of the screen giving details about the current bootloader version and it's lock state. At the upper right hand side of the screen, adjacent to the power button, are selectable options via the POWER BUTTON, which can be cycled through with the VOL BUTTONS... and these options are START, RESTART BOOTLOADER, RECOVERY MODE, POWER OFF... and then START again.
Somewhat similar to your above quoted description.
Selecting RESTART BOOTLOADER will just bring you back to where you already are... ie., the BOOTLOADER.
Also, if you can't access the bootloader, how are you managing to boot into TWRP?... as this is normally done via the bootloader... ie, by selecting the RECOVERY MODE option.
Rgrds,
Ged.
GedBlake said:
Apologies, Siddy1200... but I'm a little confused... based upon my reading of your post... I think you're already in the bootloader!!.
"...it is back to the previous screen to where I can choose restart, recovery, boot loader,etc..."
The bootloader features a green android, lying on its back, with it's belly open - some really tiny text at the lower left hand side of the screen giving details about the current bootloader version and it's lock state. At the upper right hand side of the screen, adjacent to the power button, are selectable options via the POWER BUTTON, which can be cycled through with the VOL BUTTONS... and these options are START, RESTART BOOTLOADER, RECOVERY MODE, POWER OFF... and then START again.
Somewhat similar to your above quoted description.
Selecting RESTART BOOTLOADER will just bring you back to where you already are... ie., the BOOTLOADER.
Also, if you can't access the bootloader, how are you managing to boot into TWRP?... as this is normally done via the bootloader... ie, by selecting the RECOVERY MODE option.
Rgrds,
Ged.
Click to expand...
Click to collapse
Thanks for your persistence Greg, I think I was confused as what the bootloader actually is, now I can see I am already in bootloader :silly:
I will return to stock with NRT and try the 4.4 update now.
So .... I flashed the mantaray-lrx21p image from Nexus Factory Images on my Nexus 10 (16GB Wifi) and now it's stuck in a bootloop.
No problem, I thought, I can get into recovery and fix it, right? Maybe do a wipe and try again? Yeah, not so fast. I get the bootloader screen, but the only option is 'Start' which just boots into the system that bootloops.
That's OK, I'll just use fastboot to wipe it. Nope. Fastboot doesn't detect a device.
I've tried both ADB and fastboot on Mac & Linux. Same issue (neither fastboot nor adb detect a device).
Ideas?
Observations
In case you think I'm just being impatient, it has been doing the boot animation for about 25 minutes now.
It doesn't like to stay off. If I hold the power button for 10 seconds it turns off, but it turns itself back on in about 5 seconds.
If I power it on while holding the volume button closer to the power button, I can get into a half-assed bootloader ... meaning that I can only push the power button again to 'Start'. I cannot cycle through the options with the volume buttons.
During the mentioned (half-assed) bootloader screen, fastboot does not detect a device.
During the boot animation, adb does not detect a device.
copolii said:
So .... I flashed the mantaray-lrx21p image from Nexus Factory Images on my Nexus 10 (16GB Wifi) and now it's stuck in a bootloop.
No problem, I thought, I can get into recovery and fix it, right? Maybe do a wipe and try again? Yeah, not so fast. I get the bootloader screen, but the only option is 'Start' which just boots into the system that bootloops.
That's OK, I'll just use fastboot to wipe it. Nope. Fastboot doesn't detect a device.
I've tried both ADB and fastboot on Mac & Linux. Same issue (neither fastboot nor adb detect a device).
Ideas?
Observations
In case you think I'm just being impatient, it has been doing the boot animation for about 25 minutes now.
It doesn't like to stay off. If I hold the power button for 10 seconds it turns off, but it turns itself back on in about 5 seconds.
If I power it on while holding the volume button closer to the power button, I can get into a half-assed bootloader ... meaning that I can only push the power button again to 'Start'. I cannot cycle through the options with the volume buttons.
During the mentioned (half-assed) bootloader screen, fastboot does not detect a device.
During the boot animation, adb does not detect a device.
Click to expand...
Click to collapse
The reason starts the only option is because your only holding volume up when going into fastboot. Hold power and volume up AND DOWN. All at the same time. Trust me I had the same issue but googling helped me find out you gotta hold both buttons
Sent from my VS980 4G
Same problem here, I'm stuck in a bootloop
I can access the bootloader and retry, but I'm still stuck in a bootloop.
I have checked the hash of the zip so I don't know what the problem can be.
Maibe I don't have the very last version of the sdk, that's the only guess I can do, let's try this...
---------- Post added at 10:07 PM ---------- Previous post was at 10:05 PM ----------
supermamie said:
Same problem here, I'm stuck in a bootloop
I can access the bootloader and retry, but I'm still stuck in a bootloop.
I have checked the hash of the zip so I don't know what the problem can be.
Maibe I don't have the very last version of the sdk, that's the only guess I can do, let's try this...
Click to expand...
Click to collapse
I launched a 3rd flash while I downloaded the sdk and this one worked...
Absolutely no idea why.
I finally got it to boot.
boot into bootloader (hold vol-up+vol-down+power)
choose reboot bootloader
choose shutdown
turn it back on
Seems like it needed to be shut completely off not just rebooted after the flash. Perhaps a reboot maintains weird memory fragments or something? Crazy talk, I know.
Edit: you shouldn't have to wait long to see if it works. Mine jumped to the "Upgrading apps ..." screen straight away.
The very first boot on my n7 and n10 took about 20 min, after that they have normal boot time, I believe this may have something to do with encryption but never bothered to check as I just did something else while it booted
Side note, the n9 has an initial boot time of at least 5-10 min (can't recall but it took forever it felt like) and this is optimized hardware for the software so no surprise that there is a huge long boot time on the first go
Also I flashed both manually erasing all partitions first through fastboot then flashing each one individually... Just another side note
supermamie said:
Same problem here, I'm stuck in a bootloop
I can access the bootloader and retry, but I'm still stuck in a bootloop.
I have checked the hash of the zip so I don't know what the problem can be.
Maibe I don't have the very last version of the sdk, that's the only guess I can do, let's try this...
---------- Post added at 10:07 PM ---------- Previous post was at 10:05 PM ----------
I launched a 3rd flash while I downloaded the sdk and this one worked...
Absolutely no idea why.
Click to expand...
Click to collapse
Ive tried to connect to the device in adb, fastboot, I can only get it to adb sideload mode.
Sideloading gives the message Wrong footer instalation aborted.
How did you manage to flash the image? All drivers did install properly it seems.
Boot loop
thedarksavant said:
I finally got it to boot.
The same was happening to me, after unlocking it it began to loop, even after I wipe it was still looping.
I followed your steps of going into reboot recovery then power off. -- issue resolved!!
Thanks!
******
Click to expand...
Click to collapse
Hi guys,
My Yotaphone 2 is currently stuck in a boot loop (shows android logo, then black screen, repeat) after a software update. I can get to the 'Downloading...' screen via power + vol. key and so have tried adb/fastboot as suggested in other similar threads. ADB can't see the device, which I guess is probably normal since it isn't booted up, but fastboot seemingly can. I've tried flashing the TWRP recovery which seems to go through fine on the PC end but doesn't seem to do anything at all on the phone itself. Calling a fastboot reboot gets the phone back to the boot loop and power + vol. goes back to the 'Downloading...' screen.
I've also tried using the Yotaphone flashing tool to flash a full android image - this also looked like everything was operating OK on the PC end but didn't seem to change anything on the phone once the process was complete.
Is there anything I'm missing or anything else I can try? Any help/ideas much appreciated!
Cheers.
pjrj said:
Hi guys,
My Yotaphone 2 is currently stuck in a boot loop (shows android logo, then black screen, repeat) after a software update. I can get to the 'Downloading...' screen via power + vol. key and so have tried adb/fastboot as suggested in other similar threads. ADB can't see the device, which I guess is probably normal since it isn't booted up, but fastboot seemingly can. I've tried flashing the TWRP recovery which seems to go through fine on the PC end but doesn't seem to do anything at all on the phone itself. Calling a fastboot reboot gets the phone back to the boot loop and power + vol. goes back to the 'Downloading...' screen.
I've also tried using the Yotaphone flashing tool to flash a full android image - this also looked like everything was operating OK on the PC end but didn't seem to change anything on the phone once the process was complete.
Is there anything I'm missing or anything else I can try? Any help/ideas much appreciated!
Cheers.
Click to expand...
Click to collapse
Do you have any idea what caused the bootloop? (maybe installing xposed or something?)
When you keep vol-up pressed at (not after) the moment the phone vibrates during power on, you will end up in TWRP recovery. There you can at least wipe->factory reset. Don't do this if you have stuff on your phone you'd like to keep though. (you can try to rescue/backup those by trying "adb pull <path_to_file>" when the phone is booted into TWRP)
SteadyQuad said:
Do you have any idea what caused the bootloop? (maybe installing xposed or something?)
When you keep vol-up pressed at (not after) the moment the phone vibrates during power on, you will end up in TWRP recovery. There you can at least wipe->factory reset. Don't do this if you have stuff on your phone you'd like to keep though. (you can try to rescue/backup those by trying "adb pull <path_to_file>" when the phone is booted into TWRP)
Click to expand...
Click to collapse
It was caused by doing an OS update (wasn't rooted or modified), I've only since tried installing the TWRP recovery and using fastboot to flash an official image to fix the looping. Flashing TWRP appears to work according to flashboot but holding the volume up key at the vibrate on power on doesn't do anything sadly.
pjrj said:
It was caused by doing an OS update (wasn't rooted or modified), I've only since tried installing the TWRP recovery and using fastboot to flash an official image to fix the looping. Flashing TWRP appears to work according to flashboot but holding the volume up key at the vibrate on power on doesn't do anything sadly.
Click to expand...
Click to collapse
Maybe I should rephrase: the vol-up should already be pressed once the vibrate starts. For a timing-insensitive, fool-proof (no pun intended) way you can enable bootloader (like you did before: you get the Downloading... screen). Then keep vol-up and power pressed together, after 15 seconds the device reboots hard, keep both keys pressed until you see TWRP 'curtain' screen, then release.
Did you try to use the YotaFlasher Windows application to reinstall an official ROM and restore factory defaults? You can get it from here, also download a ROM for your region here.
I dont know what happened but I rebooted my phone today and it booted into fastboot.. I cannot in any way get it to boot normally. The buttons are not being held down and I have tried to pull the battery.. I dont get it, anyone else have this issue and fixed it have an idea??
Was it stock (including recovery) or modified?
I would try to fastboot the TWRP over and then boot into that (Power & Vol+). But then... I seldom run stock.
SoNic67 said:
Was it stock (including recovery) or modified?
I would try to fastboot the TWRP over and then boot into that (Power & Vol+). But then... I seldom run stock.
Click to expand...
Click to collapse
No, it wasn't stock and I dont know what happened.. I was running the latest CM13 and rebooted this morning and it freezes up with the ASUS logo and saying "Fastboot Mode!!!" at the top... I've tried flashing twrp via fastboot but not getting anything.. I need a copy of the stock firmware with the boot system and recovery image in it but I'm having a hard time finding it.
BiasedThunder said:
I dont know what happened but I rebooted my phone today and it booted into fastboot.. I cannot in any way get it to boot normally. The buttons are not being held down and I have tried to pull the battery.. I dont get it, anyone else have this issue and fixed it have an idea??
Click to expand...
Click to collapse
I too had this issue. Tried lot of key combinations. Didn't work. My solution was to connect to PC and run
fastboot continue
Then it booted normally. Everything stock.
Hope this helps.
BiasedThunder said:
I dont know what happened but I rebooted my phone today and it booted into fastboot.. I cannot in any way get it to boot normally. The buttons are not being held down and I have tried to pull the battery.. I dont get it, anyone else have this issue and fixed it have an idea??
Click to expand...
Click to collapse
Phones boots into fastboot mode in two situations
1. Pressing vol up and power button simultaneously for rebooting
2. Your phone doesn't have recovery AND any OS installed
I guess your vol up button is constantly in pressed state.
Second situation cannot occur unless you wipe your system and recovery manually. So you are in the first situation
Your phone's vol up button is constantly in pressed state or electrically shorted may be due to water entering the case
Solution: You will have to open your phone's case and clean the area near the volume button. I guess you had opened the case/body and didn't fit it properly.
sziraqui said:
Phones boots into fastboot mode in two situations
1. Pressing vol up and power button simultaneously for rebooting
2. Your phone doesn't have recovery AND any OS installed
I guess your vol up button is constantly in pressed state.
Second situation cannot occur unless you wipe your system and recovery manually. So you are in the first situation
Your phone's vol up button is constantly in pressed state or electrically shorted may be due to water entering the case
Solution: You will have to open your phone's case and clean the area near the volume button. I guess you had opened the case/body and didn't fit it properly.
Click to expand...
Click to collapse
something happened when it rebooted and it lost recovery.. I fastboot flashed the new TWRP and reflashed the rom and all seems fine now.
Thanks for the quick responses!!
even I've witnessed a similar problem.. please help me.....out
BiasedThunder said:
No, it wasn't stock and I dont know what happened.. I was running the latest CM13 and rebooted this morning and it freezes up with the ASUS logo and saying "Fastboot Mode!!!" at the top... I've tried flashing twrp via fastboot but not getting anything.. I need a copy of the stock firmware with the boot system and recovery image in it but I'm having a hard time finding it.
Click to expand...
Click to collapse
Can any one please suggest where to find the stock firmware with the boot system....Please help me out here
Hello the second situation is happening to me. What can i do? In desperate
Help Me
Hello,
I have a similar problem. My phone is turned off and on the fastboot mode screen. Normal keys with volume keys, recovery mode, open, restart, even if I try to reboot on this screen opens. I tried to connect and format the computer, but I do not install all the drivers and files, but computers do not see my phone. Can you find me a solution?
grafikermc said:
Hello,
I have a similar problem. My phone is turned off and on the fastboot mode screen. Normal keys with volume keys, recovery mode, open, restart, even if I try to reboot on this screen opens. I tried to connect and format the computer, but I do not install all the drivers and files, but computers do not see my phone. Can you find me a solution?
Click to expand...
Click to collapse
Reinstall twrp from fastboot & install rom
Completely wiped all files while manual cleanup via twrp. Next thing I remember is rebooting device which is stuck in moto boot logo. Can't even switch off, holding power button for 8/10 sec reboot device to same boot logo loop. No fastboot/adb as I can't get to recovery mode. I have Moto X Pure, XT1575. Any hope?
navnit1 said:
Completely wiped all files while manual cleanup via twrp. Next thing I remember is rebooting device which is stuck in moto boot logo. Can't even switch off, holding power button for 8/10 sec reboot device to same boot logo loop. No fastboot/adb as I can't get to recovery mode. I have Moto X Pure, XT1575. Any hope?
Click to expand...
Click to collapse
Holding volume down + power won't boot into bootloader?
navnit1 said:
Completely wiped all files while manual cleanup via twrp. Next thing I remember is rebooting device which is stuck in moto boot logo. Can't even switch off, holding power button for 8/10 sec reboot device to same boot logo loop. No fastboot/adb as I can't get to recovery mode. I have Moto X Pure, XT1575. Any hope?
Click to expand...
Click to collapse
You probably deleted your operating system (ROM), you need to get into the bootloader and either flash a new ROM or use fastboot to flash back to stock.
Press and hold Power until the screen goes out, then press Power + Vol Dn immediately and hold until the bootloader screen comes up (might have to play with the timing a little). You should then be able to access fastboot or start TWRP.
jason2678 said:
Holding volume down + power won't boot into bootloader?
Click to expand...
Click to collapse
Thank You, I was able to get to boot loader, you saved my device
acejavelin said:
You probably deleted your operating system (ROM), you need to get into the bootloader and either flash a new ROM or use fastboot to flash back to stock.
Press and hold Power until the screen goes out, then press Power + Vol Dn immediately and hold until the bootloader screen comes up (might have to play with the timing a little). You should then be able to access fastboot or start TWRP.
Click to expand...
Click to collapse
Thanks acejavelin, I was able to get to boot loader as you suggested, then fastboot flash to factory image from Motorola site. Appreciate quick reply.
Glad it worked...
Sent from my Motorola XT1575 using XDA Labs
acejavelin said:
Glad it worked... Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
I posted this (below) to another thread, but I've seen how well you apply your knowledge base to these types of situations, and I thought I'd run it by your expertise:
Got a NOS Moto X Pure Edition xt1575 and experienced some kind of rooting glitch after having unlocked the bootloader and installing TWRP. Long story short, after a frantic bout of wiping and swiping, the OS is gone, I can't select the micro SD in TWRP, and adb/fastboot only sees the phone in recovery. I found this thread, which seemed promising, but it appears to be a no-go without access to the bootloader. I've flashed so many custom ROMS to a tablet I have, that I thought this phone would be a cakewalk, but it seems to have rolled right over me. So, is it time to slather some mortar on this thing and add it to the wall (bricked), or is there a Hail Mary play, or Jiu Jitsu move out there somewhere? Anything...ANY-THING would be welcome and much appreciated. Thank you.
tswrench said:
I posted this (below) to another thread, but I've seen how well you apply your knowledge base to these types of situations, and I thought I'd run it by your expertise:
Got a NOS Moto X Pure Edition xt1575 and experienced some kind of rooting glitch after having unlocked the bootloader and installing TWRP. Long story short, after a frantic bout of wiping and swiping, the OS is gone, I can't select the micro SD in TWRP, and adb/fastboot only sees the phone in recovery. I found this thread, which seemed promising, but it appears to be a no-go without access to the bootloader. I've flashed so many custom ROMS to a tablet I have, that I thought this phone would be a cakewalk, but it seems to have rolled right over me. So, is it time to slather some mortar on this thing and add it to the wall (bricked), or is there a Hail Mary play, or Jiu Jitsu move out there somewhere? Anything...ANY-THING would be welcome and much appreciated. Thank you.
Click to expand...
Click to collapse
I don't understand... Does the phone not boot to the bootloader when you hold the volume key? Have you tried my return to stock thread?