I unlocked the bootloader on my phone, then flashed twrp. I rebooted to twrp and installed boot.img, TWRPWorkingInstaller.zip, TWRP-BLUE-FIX.zip, and Root.zip. Rebooting worked fine, but I saw that there was a newer twrp (twrp-3.2.1-3-wOOSkernel.img, so I tried installing it from twrp. The problem is that I installed it to the system image partition. After that, everything got wonky, unsurprisingly. Now, if I try to boot to twrp, it loads and I get to the first menu, but I cannot interact with it at all. Then the screen goes black and the led lights up blue. It doesn't respond to anything except shutting it down. I can hold the power button down to power off, but it reboots instead to a black screen with the blue LED. I can also boot into the bootloader. I can reflash twrp. When I restart to recovery then, I get the screen asking if I want to keep the system files locked or swipe to unlock it. The device seems to work fine for about 5 seconds from the time I get to the first twrp menu, then it doesn't respond. About 5-8 seconds later, the screen goes black and the blue led comes on. I also cannot power-off the device. If I try, it reboots.
Is there anything I can do to recover from this? I've got the stock recovery files (OnePlus6Oxygen_22_OTA_009_all_1805172226_f7d1518e0e704ca3.zip), but I can't copy them to the device because it won't boot to the OS.
Yippee38 said:
I unlocked the bootloader on my phone, then flashed twrp. I rebooted to twrp and installed boot.img, TWRPWorkingInstaller.zip, TWRP-BLUE-FIX.zip, and Root.zip. Rebooting worked fine, but I saw that there was a newer twrp (twrp-3.2.1-3-wOOSkernel.img, so I tried installing it from twrp. The problem is that I installed it to the system image partition. After that, everything got wonky, unsurprisingly. Now, if I try to boot to twrp, it loads and I get to the first menu, but I cannot interact with it at all. Then the screen goes black and the led lights up blue. It doesn't respond to anything except shutting it down. I can hold the power button down to power off, but it reboots instead to a black screen with the blue LED. I can also boot into the bootloader. I can reflash twrp. When I restart to recovery then, I get the screen asking if I want to keep the system files locked or swipe to unlock it. The device seems to work fine for about 5 seconds from the time I get to the first twrp menu, then it doesn't respond. About 5-8 seconds later, the screen goes black and the blue led comes on. I also cannot power-off the device. If I try, it reboots.
Is there anything I can do to recover from this? I've got the stock recovery files (OnePlus6Oxygen_22_OTA_009_all_1805172226_f7d1518e0e704ca3.zip), but I can't copy them to the device because it won't boot to the OS.
Click to expand...
Click to collapse
Do you have a TWRP backup from when your phone worked on an external drive?
Can you access fastboot? Just use the fastboot ROM files to reflash the OS. Or if that doesn't work try the unbrick tool.
Yeah. I can use fastboot. However, I wasn't able to get to ROM to flash. I'm not sure if I'm using the correct parameters in the command. I googled, but all I came up with was flashing custom ROMs. Where can I find the unbrick tool?
NM. Found the unbrick tool. I may try it. I'll let you know how it works.
Thanks for your help @NateDev!. The Unbrick Tool helped me fix it.
Yippee38 said:
Thanks for your help @NateDev!. The Unbrick Tool helped me fix it.
Click to expand...
Click to collapse
Glad you got it solved
Related
I rooted my MT4GS a few months ago but stuck with the stock ROM. I decided I wanted to try out the CyanogenMod 9.1 ICS ROM. I followed the following steps:
1) Installed ROM Manager.
2) ROM Manager indicated a newer version of ClockworkMod Recovery and I installed it (5.0.2.7).
3) Using ROM Manager, did a full backup of the current ROM. All went well.
4) Using ROM Manager, downloaded and installed CyanogenMod 9.1.0 stable-doubleshot. I specified to wipe the data and cache partitions. The installation seemed to go normally.
When the phone rebooted, it was stuck at the logo screen. Had to remove the battery to turn it off. Tried a couple times, still the same.
Since I had the backup, I decided I would use CWM to restore the old ROM.
When I boot into recovery mode, it shows CWM 5.0.2.7, but whatever option I try to choose from the recovery menu, The screen just goes blank with the CWM logo in the middle and nothing else happens. Hitting the power button returns me to the menu, but no option works, even power down or reboot. It just goes back to the CWM logo again and I have to remove the battery to shut it down.
So, I thought I would try using fastboot to flash the ROM again. When I boot the phone into the boot loader and select fastboot, then plug the phone in via USB, nothing happens. Windows does not see the phone and ADB or fastboot don't see it either. It's not a driver issue, as the computer is still setup from when the computer was rooted and I connect the phone all the time with no problems.
When the phone is off and plugged into USB or the charger, I still get the charging light, though it goes off after about 10 seconds, then comes back on and cycles like that.
Is there anything I can try at this point, or is my phone bricked? It seems like I followed all the steps correctly. Is there an update.zip I can put in the root folder and see if it picks it up?
Any help would be appreciated.
brucehvn said:
I rooted my MT4GS a few months ago but stuck with the stock ROM. I decided I wanted to try out the CyanogenMod 9.1 ICS ROM. I followed the following steps
...
Click to expand...
Click to collapse
Ok, after rebooting Windows, I was able to get the USB connection to the phone to work in fastboot. It seems I missed the step described in this thread:
http://forum.xda-developers.com/showthread.php?t=1508556
which states with S-ON you must flash the boot.img separately. I did that via fastboot and the phone boots into cyanogenmod now.
However, I still seem to have the issue with clockwordmod recovery. As long as I do the recovery functions from rom manager, everything is fine, but when I manually boot into the recovery menu, I get the same behavior of any choice from the menu just blanks the screen except for the CWM logo and nothing happens. I tried reflashing the recovery image using fastboot, but still no go.
brucehvn said:
However, I still seem to have the issue with clockwordmod recovery. As long as I do the recovery functions from rom manager, everything is fine, but when I manually boot into the recovery menu, I get the same behavior of any choice from the menu just blanks the screen except for the CWM logo and nothing happens. I tried reflashing the recovery image using fastboot, but still no go.
Click to expand...
Click to collapse
This is solved also. Seems on the MT4GS, the trackball is the selection button. The power button appears to only be a back button.
What a thread! Two nicely phrased problem definitions, two well explained solutions, and all from the same guy. Sorry we weren't able to help directly, but you obviously found the answers you needed elsewhere in the forum. And you updated the title as well to show it was solved. Thanks.
So guys, i've done it. I bring my first device.
Yesterday i tried to downgrade via fastboot with this recovery images https://developer.nvidia.com/gameworksdownload (yes is choose the right ones)
flash boot, check
flash recovery, check
flash system, failes (insufficient memory)
erase sytem, check
flash system, failed (insufficient memory)
flash twrp, check, but no usb mouse so
flash cwm, check
factory reset, check
rom.zip and gapps on sd card, check
reboot, boot into bootloader, no chance
It boots everytime normal, so i cant enter the recovery.
Connect it to charger, check
charging led lights up, check
Go sleeping, check
doenst boot into bootloader :/
Back to charger
Now I wanted to try it again and i wont even boot.
Anyone has an Idea? Or is it really bricked?
Can you still see the device listed using fast boot?
No, because I can't enter the bootloader or the recovery. But it boots again
...
The same thing just happened to me. Unfortunately, I am still trying to figure it out. I flashed a "stock" recovery that I had found in order to be able to take the OTAs. Now when I boot, I just stay stuck on the NVIDIA splash screen.....been there for hours.
rafaelvelasquez2 said:
The same thing just happened to me. Unfortunately, I am still trying to figure it out. I flashed a "stock" recovery that I had found in order to be able to take the OTAs. Now when I boot, I just stay stuck on the NVIDIA splash screen.....been there for hours.
Click to expand...
Click to collapse
Same here.....
Mine is working again. Booting in the bootloader is a little bit tricky.
Have you tried to flash all? Boot.img, recovery.img and system.img?
...
I had the same issue. But after trying to get into the bootloader using POWER + VOLUME DOWN for about 15 minutes it finally went to the bootloader and I was able to re-flash it. I have a feeling it's the cludgy power button.
You do not need to flash the stock recovery to take the ota. I have taken 2 otas now on custom recovery without any issue and without loosing root. Just an FYI.
Sent from my SHIELD Tablet using XDA Free mobile app
I just did a factory reset under lollipop, locked boot-loader rooted and it rebooted to the green android screen then dropped into CWM and asked to fix root. I said no, then it went to the nvidia boot logo and it is stuck. Any suggestions? Thanks.
Edit: nevermind, I just powered it off after about 20 minuets and it hung again. When I plugged it into my pc, it finally poped into the setup/welcome screen. Pretty weird. Heart attack averted
So, I got my new OnePlus One today and I tried to get CM12 onto it. I was following the [GUIDE] How to Install CM12 on the OnePlus One- Android Lollipop/5.0 on the OPO forums, and everything went well until I tried to get the TWRP on there. I flashed the recovery and rebooted the phone. I turned it off and then tried to boot it into recovery but it doesn't, it just hangs at the OPO logo until I hard-restart it.
I've tried factory resetting it and doing
fastboot oem unlock
but nothing happened. The factory reset pretty much just reset the phone. I think I might've messed up the kernel. How do I fix it?
EDIT 1: I've tried reflashing twrp recoveries and nothing. When I hold power+volume down, it powers on, shows the one plus logo, then reboots and just goes to the lockscreen.
UPDATE 1: I managed to manually flash all the CM12 files and use lollipop. I haven't tried the recovery yet but I'll keep you guys updated (if any of you even care).
UPDATE 2: Apparently flashing CM12 made the recovery work. Everything works as it should and the OTA to the most recent CM12 worked perfectly.
You're probably doing the button combo wrong. Hold volume down, then hold power (so you're holding them together), when you see the boot logo let go of power but keep holding volume down until you reach recovery.
Heisenberg said:
You're probably doing the button combo wrong. Hold volume down, then hold power (so you're holding them together), when you see the boot logo let go of power but keep holding volume down until you reach recovery.
Click to expand...
Click to collapse
I was curios and enabled advanced reboot to try and boot into recovery and it worked (after I had flashed CM12). Everything's working now.
SDCore said:
UPDATE 1: I managed to manually flash all the CM12 files and use lollipop. I haven't tried the recovery yet but I'll keep you guys updated (if any of you even care).
Click to expand...
Click to collapse
How did you manually flash CM12? I think I'm having the same trouble you were having. I used the oneplus toolbox from the forum to unlock the bootloader, then flash the TWRP, but no luck in getting into recovery mode. It just boot loops with the oneplus logo until I release the volume down button at which point it then boots to the lock screen.
Heisenberg said:
You're probably doing the button combo wrong. Hold volume down, then hold power (so you're holding them together), when you see the boot logo let go of power but keep holding volume down until you reach recovery.
Click to expand...
Click to collapse
@Heisenberg I'm also having trouble getting into recovery. I've tried the different button combos (power + vol down; power + vol down and release power) as well as the advance reboot options to get into recovery, but they all fail. I get the 1+ logo and after I let go of the volume down button the screen goes black and boots again to the 1+ screen and then to the lockscreen. It's almost like it doesn't recognize the recovery. I tried putting the stock recovery back on using the image in the OnePlus One toolkit folder, but that one doesn't work either. In addition to unchecking the "CM Recovery Update", are there any other settings that could be causing problems?
For background info, I initially used the toolkit interface to unlock the bootloader and then flash the recovery. The bootloader unlocked with no issue...it wiped my device and I was in sync with the "How to root" video posted by alex.inthi. I got sidetracked after the (seemingly) successful flash of TWRP onto the phone I kept getting booted into the Cyanogen recovery. I realized out that I needed to uncheck the setting to keep it from overwriting TWRP and after that was not able to boot into recovery. After finding your beginners guide (thanks, by the way, very well written) I tried using fastboot from the command line as you show, but still no luck.
Thanks in advance for any help...
bellino13 said:
I used the oneplus toolbox from the forum to unlock the bootloader, then flash the TWRP, but no luck in getting into recovery mode. It just boot loops with the oneplus logo until I release the volume down button at which point it then boots to the lock screen.
Click to expand...
Click to collapse
bellino13 said:
@Heisenberg I'm also having trouble getting into recovery. I've tried the different button combos (power + vol down; power + vol down and release power) as well as the advance reboot options to get into recovery, but they all fail. I get the 1+ logo and after I let go of the volume down button the screen goes black and boots again to the 1+ screen and then to the lockscreen. It's almost like it doesn't recognize the recovery. I tried putting the stock recovery back on using the image in the OnePlus One toolkit folder, but that one doesn't work either. In addition to unchecking the "CM Recovery Update", are there any other settings that could be causing problems?
For background info, I initially used the toolkit interface to unlock the bootloader and then flash the recovery. The bootloader unlocked with no issue...it wiped my device and I was in sync with the "How to root" video posted by alex.inthi. I got sidetracked after the (seemingly) successful flash of TWRP onto the phone I kept getting booted into the Cyanogen recovery. I realized out that I needed to uncheck the setting to keep it from overwriting TWRP and after that was not able to boot into recovery. After finding your beginners guide (thanks, by the way, very well written) I tried using fastboot from the command line as you show, but still no luck.
Click to expand...
Click to collapse
Okay, I must have been having a special kind of moment - I've got TWRP 2.8.7.0 running on my handset now. I may have been holding the volume down button too long, or it may be that I was using an older version of TWRP, but I'm going to go with the former. I've also been able to successfully flash and boot into Philz 6.59.2
Having the same problem
I am having the exact same problem and cannot seem to find a solution. Recovery screen just doesn't appear, but goes to lockscreen.
Tried erasing, flashing both twrp, philz etc., but nothing works. The phone doesn't recognize the recovery status. Advanced booting does the same.
Update CM-recovery is checked off, phone is unlocked. I've followed every step of the big guide down to every detail.
Is manually flashing the 12.1 ROM the only way and in that case: is it hard for a relative newcomer?
I tried booting into recovery today, and my R7 Plus just boots normally. It gives the vibrate indication, and then the OPPO logo flashes on for a split second... but then it gives up booting into recovery, the screen goes black again, and the phone boots normally.
If I hold down volume [-] and power, it keeps flashing the Oppo logo and then black screening every second until I let go of the buttons. It seems to me like it keeps trying to boot into recovery and then something goes wrong. After I let go of the buttons, it boots normally.
Booting to recovery through Flashify didn't work; it gave the same Oppo logo-flash before turning back and booting normally.
For some more background, after rooting my phone, I did some deleting of .com files and other Oppo-associated apps/files; I'm not a fan of ColorOS and any Oppo bloatware, so I probably deleted some pretty important stuff. Actually, I'm pretty sure I deleted something important along the way.
I would like to do a clean install to get all of the key firmware modules/files back, I can't do that without access to recovery. I tried unrooting and installing an official update, but that failed since I can't access recovery. What's more, I can't re-root because, again, recovery isn't available; Oppo Tools isn't working.
If I do a factory reset, does that restore all of the ColorOS data, including restoring deleted OS files, or does it just delete my user data and I still won't be able to boot into recovery? Is there a way to flash a stock ROM without recovery mode being available?
sendraww said:
I tried booting into recovery today, and my R7 Plus just boots normally. It gives the vibrate indication, and then the OPPO logo flashes on for a split second... but then it gives up booting into recovery, the screen goes black again, and the phone boots normally.
If I hold down volume [-] and power, it keeps flashing the Oppo logo and then black screening every second until I let go of the buttons. It seems to me like it keeps trying to boot into recovery and then something goes wrong. After I let go of the buttons, it boots normally.
Booting to recovery through Flashify didn't work; it gave the same Oppo logo-flash before turning back and booting normally.
For some more background, after rooting my phone, I did some deleting of .com files and other Oppo-associated apps/files; I'm not a fan of ColorOS and any Oppo bloatware, so I probably deleted some pretty important stuff. Actually, I'm pretty sure I deleted something important along the way.
I would like to do a clean install to get all of the key firmware modules/files back, I can't do that without access to recovery. I tried unrooting and installing an official update, but that failed since I can't access recovery. What's more, I can't re-root because, again, recovery isn't available; Oppo Tools isn't working.
If I do a factory reset, does that restore all of the ColorOS data, including restoring deleted OS files, or does it just delete my user data and I still won't be able to boot into recovery? Is there a way to flash a stock ROM without recovery mode being available?
Click to expand...
Click to collapse
Hi there, i know its been a long time. But i wanna know, have you solved your problem? If yes, could you please share how to fix it. Because im in the same situation right now.
Thank you.
Hello Guys! I need your help. My Power Button is broken. The only way to boot up my phone is to plug it to a power source, wait for the Sony Logo and the Blue LED to light up, press volume up (+) to trigger TWRP, and select reboot system. I have Multi Recovery installed. Now my problem is when I am trying to press volume up, TWRP does not trigger. I also tried the other two recoveries. The screen just goes black and nothing happens. Now I can not boot up my phone. I have tried the ADB solution but it does not work as well. Please send me some help. I really need to turn my phone on. Thank you, and regards my friends.
If your system can't boot, since it enters on chargemon mode, my suggestion is to try to pick a customized boot image, with injected recovery ramdisk in order to get them working again. This however requires Unlocked Bootloader. You can give it a try here: http://forum.xda-developers.com/xpe...recovery-6-t3047492/post63240855#post63240855
linuxct said:
If your system can't boot, since it enters on chargemon mode, my suggestion is to try to pick a customized boot image, with injected recovery ramdisk in order to get them working again. This however requires Unlocked Bootloader. You can give it a try here: http://.xda-.com/xperia-m2/developm...recovery-6-t3047492/post63240855#post63240855
Click to expand...
Click to collapse
Thank you, Sir for suggestions Sir. I have found out a way to boot my phone up this morning. I pressed the volume up button before connecting into the PC and it opened Fastboot. Then I entered the command fastboot reboot to the cmd. It has already booted. I would like to try your suggestion, I've got unlocked bootloader though. Thank you so much, by the way.