Hi guys,
I think I made a huge mistake Any help appreciated...
I was following the Magisk and TWRP guides to try and root my phone. I thought it was all going well, but then when trying to flash TWRP, it didn't let me flash it to recovery, it said 'no partisan'. I found on a forum post to try the command 'fastboot getvar current-slot' (this returned a) then 'fastpool flash_a twrp.img'.
I tried this but then TWRP got stuck on the loading screen. I then realised that I couldn't boot into my Android version anymore as I'd flashed TWRP directly onto the boot partition! So I went about trying to flash my stock Android version back onto the phone... I then did this:
'fastboot boot_a boot.img' I stupidly then rebooted. I now am stuck with a perpetually spinning Google loading boot image. I can't launch into recovery mode as I have none, and when holding the power button and volume up it shows an info screen saying "PRESS POWER BUTTON TO PAUSE" and then it goes to the perpetual loading screen again.
I also can't do any more fast booting because adb cannot connect anymore...
Am I completely doomed?
silkt said:
Hi guys,
I think I made a huge mistake Any help appreciated...
I was following the Magisk and TWRP guides to try and root my phone. I thought it was all going well, but then when trying to flash TWRP, it didn't let me flash it to recovery, it said 'no partisan'. I found on a forum post to try the command 'fastboot getvar current-slot' (this returned a) then 'fastpool flash_a twrp.img'.
I tried this but then TWRP got stuck on the loading screen. I then realised that I couldn't boot into my Android version anymore as I'd flashed TWRP directly onto the boot partition! So I went about trying to flash my stock Android version back onto the phone... I then did this:
'fastboot boot_a boot.img' I stupidly then rebooted. I now am stuck with a perpetually spinning Google loading boot image. I can't launch into recovery mode as I have none, and when holding the power button and volume up it shows an info screen saying "PRESS POWER BUTTON TO PAUSE" and then it goes to the perpetual loading screen again.
I also can't do any more fast booting because adb cannot connect anymore...
Am I completely doomed?
Click to expand...
Click to collapse
I ended up eventually un-bricking my phone by booting into safe mode and re-connecting the ADB. I then successfully ran 'flash-all.'
Related
Hello I believe my HTC one is bricked. I was changing my ROM, I have done it before but its been awhile so I did it wrong and bricked it. This is what I know.
When putting in the new ROM it showed an error and I realized I forgot to clear the data and cache. So I went back into my recovery to clear the cache and I did a factory reset.
Then it started to boot loop. It would boot to my boot screen, turn off, then boot up to my recovery, show the recovery's logo screen for a very short period then turn off and go back to the HTC boot screen.
I held down the power button and volume down and managed to get to my boot loader from there I did another factory reset because I thought it would go back to stock.
I attempted an RUU to no avail.
All of that got me to where I am now. I can boot to to my boot loader and recovery. I have full access of my teamwin recovery and my boot loader. My recovery says I have no OS every time I reboot. I am not in USB debugging mode and only have access to fastboot from my computer.
I really think I just need a nuclear option to set it back to. %100 stock using only fastboot. My last resort is going into the att store and play dumb.
xeas said:
Hello I believe my HTC one is bricked. I was changing my ROM, I have done it before but its been awhile so I did it wrong and bricked it. This is what I know.
When putting in the new ROM it showed an error and I realized I forgot to clear the data and cache. So I went back into my recovery to clear the cache and I did a factory reset.
Then it started to boot loop. It would boot to my boot screen, turn off, then boot up to my recovery, show the recovery's logo screen for a very short period then turn off and go back to the HTC boot screen.
I held down the power button and volume down and managed to get to my boot loader from there I did another factory reset because I thought it would go back to stock.
I attempted an RUU to no avail.
All of that got me to where I am now. I can boot to to my boot loader and recovery. I have full access of my teamwin recovery and my boot loader. My recovery says I have no OS every time I reboot. I am not in USB debugging mode and only have access to fastboot from my computer.
I really think I just need a nuclear option to set it back to. %100 stock using only fastboot. My last resort is going into the att store and play dumb.
Click to expand...
Click to collapse
you can boot to recovery
choose advanced/sideload
then from your pc put the rom you want to push to the phone in the adb/fastboot folder
then
adb devices
(verify you phone are detect)
adb sideload name_of_the_rom_file.zip
(Wait the file is transfered to phone and recovery flash)
clsA said:
you can boot to recovery
choose advanced/sideload
then from your pc put the rom you want to push to the phone in the adb/fastboot folder
then
adb devices
(verify you phone are detect)
adb sideload name_of_the_rom_file.zip
(Wait the file is transfered to phone and recovery flash)
Click to expand...
Click to collapse
Fixed. I went into the att store and a nice gentleman told me what he did. He relocked the boatloader and ran the HTC ruu
xeas said:
Fixed. I went into the att store and a nice gentleman told me what he did. He relocked the boatloader and ran the HTC ruu
Click to expand...
Click to collapse
very good
i have the same problem but my phone is not being recognized everytime i pull up a linux terminal.
i flashed the android revolution 41 rom and after instalation i accidentally skipped the last step and got stuck in the loop
i am getting the same logo and the clockworkmod 6.0.3.4 screen for a few seconds the phone restarts and gets stuck at the htc logo.
i know some have had problems with their htc one on windows 8 so i went and made my pc ubuntu, same thing.
thanks in advance for the help
qibz said:
i have the same problem but my phone is not being recognized everytime i pull up a linux terminal.
i flashed the android revolution 41 rom and after instalation i accidentally skipped the last step and got stuck in the loop
i am getting the same logo and the clockworkmod 6.0.3.4 screen for a few seconds the phone restarts and gets stuck at the htc logo.
i know some have had problems with their htc one on windows 8 so i went and made my pc ubuntu, same thing.
thanks in advance for the help
Click to expand...
Click to collapse
Welcome to XDA
posting your problem with all the needed information in a new thread would help.
when making your post be sure and include
whats on the bootloader screen
and a copy/paste of the results from fastboot getvar all
most likely your not s-off or your not on the correct version of TWRP
also in your new post add @clsA so i get the notification that you posted
I've had my Optimus G rooted for a while now, and I had recently updated to Cyanogenmod 11 M3 and after a few weeks of good use, my phone crashed for no reason. There was a green screen that said Kernel Crash, demigod fail or something and some other stuff. Told me to press up to do this, down to do this, power to do this…. Anyways the phone wouldn't boot up after that. It was stuck on the LG logo. I could only get it into fast boot and download mode but from fast boot there was no way to get to recovery or regular boot. I found the TeenyBins post and tried to fix it using both of the .bins they had but at 85% the phone tried to boot up and was stuck on the LG logo again. Then I found the stock .bins and tried to flash them over, yet I got the same result. I've tried everything I can think to do, if anyone has any suggestions, please please help.
Teenybins don't have an OS. Did you try to get into recovery after flashing them? Doing a hard reset after stock bins may get it to boot, but internal storage will be wiped. For future reference in the demigod screen the buttons are backwards.
After flashing Teenybin I can boot into fast boot, but from there when I select recovery it goes back to the logo. Same thing happens if I select the other options. It's the google logo, not the LG logo, because the Teenybin I most recently tried was the alternate file
bowshermatthew said:
After flashing Teenybin I can boot into fast boot, but from there when I select recovery it goes back to the logo. Same thing happens if I select the other options. It's the google logo, not the LG logo, because the Teenybin I most recently tried was the alternate file
Click to expand...
Click to collapse
If you are already in fastboot, download any recovery (CWM or TWRP) extract it, rename it to recovery.img from the zip and then go to the folder where you have adb and fastboot bins and type:
fastboot flash recovery recovery.img
from there you'll be able to access recovery.
Thank you for the help, I was going to try that last night after reading your post but I took it to the AT&T store and they said they would replace it for free (warranty). I appreciate the quick response time.
Hi!
I have a OnePlus X and the year after I bought it, I flashed TWRP and installed Lineage OS. Since then, I've flashed many custom roms on my phone. A few weeks back, I decided to flash Resurrection Remix. The battery life on my phone with resurrection was pathetic so I assumed it could be fixed by flashing a custom kernel (franco kernel). I downloaded franco kernel, copied it to my SD card and powered off my phone.
Instead of pressing the VOLUME DOWN and POWER button simultaneously to enter TWRP, I pressed the VOLUME UP and POWER button by accident and went into Fastboot mode. When in Fastboot mode, I pressed the VOLUME DOWN and POWER button thinking my phone would boot into recovery, but it got stuck in a bootloop.
Now my phone can boot only into fastboot mode by pressing the volume up+power button. Any other combination of buttons and it goes into a bootloop.
All this is completely my fault and I would do anything to try and fix it.
Is my phone soft bricked or hard bricked? ( I have a feeling that it is soft bricked).
I've downloaded the android SDK and Minimal adb and fastboot on my pc. I'm able to run fastboot commands, but when I type 'fastboot oem unlock', I get an error saying
"FAILED (remote: oem unlock is disabled)". I've tried 'fastboot flashing unlock' too, but the screen just says "...". Hence, I'm not able to flash TWRP. I tried flashing even the stock recovery but it wouldn't work.
Is there any other way to unlock the bootloader?
I haven't tried the Mega unbrick guide for a hard bricked OnePlus X yet, since I'm able to boot into fastboot mode. Should I give it a shot?
And lastly, can I recover my phone from this mess or is it permanently bricked?
I would appreciate any help.
Thank you!
Sounds very similar to my situation. I did end up following that guide to get mine going again. The link is broken to get the recovery tool, the 2nd one below is the "minimal" version which isn't supposed to wipe data. That is the one that worked for me. I would backup any data if you can first, no guarantee it wont wipe it. Mine wouldn't boot into the stock rom after, but at least it would get to the stock bootloader (VolDOWN + PWR). From there I was able to adb sideload the stock rom (Install from USB). This completely restored it to stock.
23santosh24 said:
Hi!
I have a OnePlus X and the year after I bought it, I flashed TWRP and installed Lineage OS. Since then, I've flashed many custom roms on my phone. A few weeks back, I decided to flash Resurrection Remix. The battery life on my phone with resurrection was pathetic so I assumed it could be fixed by flashing a custom kernel (franco kernel). I downloaded franco kernel, copied it to my SD card and powered off my phone.
Instead of pressing the VOLUME DOWN and POWER button simultaneously to enter TWRP, I pressed the VOLUME UP and POWER button by accident and went into Fastboot mode. When in Fastboot mode, I pressed the VOLUME DOWN and POWER button thinking my phone would boot into recovery, but it got stuck in a bootloop.
Now my phone can boot only into fastboot mode by pressing the volume up+power button. Any other combination of buttons and it goes into a bootloop.
All this is completely my fault and I would do anything to try and fix it.
Is my phone soft bricked or hard bricked? ( I have a feeling that it is soft bricked).
I've downloaded the android SDK and Minimal adb and fastboot on my pc. I'm able to run fastboot commands, but when I type 'fastboot oem unlock', I get an error saying
"FAILED (remote: oem unlock is disabled)". I've tried 'fastboot flashing unlock' too, but the screen just says "...". Hence, I'm not able to flash TWRP. I tried flashing even the stock recovery but it wouldn't work.
Is there any other way to unlock the bootloader?
I haven't tried the Mega unbrick guide for a hard bricked OnePlus X yet, since I'm able to boot into fastboot mode. Should I give it a shot?
And lastly, can I recover my phone from this mess or is it permanently bricked?
I would appreciate any help.
Thank you!
Click to expand...
Click to collapse
Surely your bootloader is already unlocked isn't it?
You don't actually say what happens when you try to reboot into recovery using fastboot commands. Does that fail too? What happens when you try to flash twrp again? You don't actually say.
That's what I thought too. It would just say 'recovery.img' not found or something like that. But, I followed the Mega unbrick guide and was able to install the stock ROM through the stock recovery. My OPX is alive again!
i'm stuck here. the phone does not go into recovery at all .. stuck on oneplus logo .. I don't know what to do .. any ideas?
---------- Post added at 09:20 AM ---------- Previous post was at 08:24 AM ----------
I managed to get it alive again with this guide
I've been following the tutorial found at https://forum.xda-developers.com/general/device-reviews-and-information/blu-life-one-x-2016-t3287428 but since the rules say not to post questions in general I figured I'd make a thread here instead of asking in that thread.
I've gotten to the part where I'm flashing a custom recovery. I have no problems flashing it but after rebooting and then rebooting into recovery I'm shown the stock recovery page. I'm sure it's because my phone's rewriting CWM and TWRP with the stock recovery, but I've been unable to find a way around it. The steps I've done to try and reboot into CWM/TWRP (I've tried both):
Use the adb reboot recovery command. This results in booting into stock recovery.
Use the fastboot boot cwm.img command to boot directly into the recovery mode. This results in the phone booting normally.
Shutting down the device and holding VolUp, VolDown, and Power simultaneously at boot. This results in the phone being stuck/frozen with a "Meta mode" text found at the bottom left of the screen.
Shutting down the device and holding VolUp and Power simultaneously at boot. This results in showing "Boot into recovery, bootloader, or stock" menu. Selecting recovery results in the phone booting normally.
I would find/create a custom "stock" ROM that doesn't automatically rewrite custom recovery modes with the stock recovery but I need to be able to load a custom recovery in order to install .zips. Any help in getting my phone as far away from stock as possible after reading about how the dev sells my data would be greatly appreciate.
I am having the exact same issues...why has no one in the entirety of the internet addressed this ??? We can't be the only two...
if your botloader is locked the system will keep replacing twrp with stock
Hi, so I flashed TWRP recovery and booted into it immediately. However, I forgot to flash the lazyflasher zip and rebooted straight away. Now the device is stuck at the logo and I can't seem to get to fastboot or recovery mode using the command line. I read a few other threads similar to my issue but apparently, they could access fastboot mode and I can't. Am I missing something?
ProBlast said:
Hi, so I flashed TWRP recovery and booted into it immediately. However, I forgot to flash the lazyflasher zip and rebooted straight away. Now the device is stuck at the logo and I can't seem to get to fastboot or recovery mode using the command line. I read a few other threads similar to my issue but apparently, they could access fastboot mode and I can't. Am I missing something?
Click to expand...
Click to collapse
Have you tried pressing Volume plus + power button to boot into recovery or Volume minus + power button to boot into fastboot mode?
Solution
It also happened to me but I booted into twrp and flashed an custom rom and also the lazy flasher.zip after couple of minutes it booted up. It may help you