So here is the deal. I was running CM 12 with TWRP on my Nexus 5 for the past few weeks. After the 12.1 OTAs rolled out, with their issues in Google Play Services compatibility, I decided to go back to stock. For that I used the Nexus Root Toolkit option flash stock/ unroot. The process finished said that the bootloader needed to be unlocked, silly me for forgetting that step. I unlocked the bootloader, again using the Nexus Root Toolkit and the stock recovery. After it finished erasing data, it started this weird bootloop where it goes to the google logo, with the unlocked bootloader symbol, then immediately goes to the TWRP splashscreen, where it will stay for approximately 20 seconds before the screen goes black and the splashcreen comes back again.
I've tried shutting it off and on again, even tried accesing it via ADB, all with no luck. Any suggestions?
Toolkit f'd you up pretty bad. Why would you need to unlock your bootloader if you were already rooted and running a custom rom?
Try downloading the factory images and flashing them..
Sent from my Nexus 5 using Tapatalk
Go ask the toolkit dev. All you can tell us is which button you pushed. Without knowing what script was run and what it did, we can't tell you what happened.
And I second the above; why would the bootloader need to be unlocked when you already successfully flashed? Because the toolkit told you that you needed to?
axstcz said:
So here is the deal. I was running CM 12 with TWRP on my Nexus 5 for the past few weeks. After the 12.1 OTAs rolled out, with their issues in Google Play Services compatibility, I decided to go back to stock. For that I used the Nexus Root Toolkit option flash stock/ unroot. The process finished said that the bootloader needed to be unlocked, silly me for forgetting that step. I unlocked the bootloader, again using the Nexus Root Toolkit and the stock recovery. After it finished erasing data, it started this weird bootloop where it goes to the google logo, with the unlocked bootloader symbol, then immediately goes to the TWRP splashscreen, where it will stay for approximately 20 seconds before the screen goes black and the splashcreen comes back again.
I've tried shutting it off and on again, even tried accesing it via ADB, all with no luck. Any suggestions?
Click to expand...
Click to collapse
You should put it in fastboot mode and flash a stock android image. will wipe your device but your sanity and phone will be back to normal. if you need help finding fastboot commands and such let me know.
Related
Shortly after getting the phone I rooted and installed CM / Synergy ROM. I'm not entirely sure what happened but a few days after I started receiving a message about insufficient storage when attempting to update apps on the Market. So I figured just redoing everything would be a good way to resolve the issue.. that went well.
I followed the how to root your vzw guide. I wiped and reset back to factory, flashed the Synergy ROM again with Odin, and then applied the latest Imoseyon LeanKernel. I then spent hours getting everything set back up thinking the phone was fine. After the phones first reboot I had a message stating the phone was running an unauthorized version of software and I should contact Verizon. So I panicked and went back to the guide following the section titled 'How to get back to stock from any rom' I applied both of the VRAL files as it says and then the stock ROM.
Not sure if I'm just compeltely confused on part of the process here or what, but I do not understand why I still have a 'custom' boot screen showing, and now am stuck in a boot loop. Although, I'm no longer seeing the scary contact Verizon message.
I had also run into something after hours of digging called root66. So I tried that as well and I'm still stuck in the same position. The custom counter has gone up each time I've flashed.
Vol up + home + power enter the screen saying it's loading custom boot and then the phone vibrates / restarts / hangs in boot.
Help is greatly appreciated!
jacksheadache said:
Shortly after getting the phone I rooted and installed CM / Synergy ROM. I'm not entirely sure what happened but a few days after I started receiving a message about insufficient storage when attempting to update apps on the Market. So I figured just redoing everything would be a good way to resolve the issue.. that went well.
I followed the how to root your vzw guide. I wiped and reset back to factory, flashed the Synergy ROM again with Odin, and then applied the latest Imoseyon LeanKernel. I then spent hours getting everything set back up thinking the phone was fine. After the phones first reboot I had a message stating the phone was running an unauthorized version of software and I should contact Verizon. So I panicked and went back to the guide following the section titled 'How to get back to stock from any rom' I applied both of the VRAL files as it says and then the stock ROM.
Not sure if I'm just compeltely confused on part of the process here or what, but I do not understand why I still have a 'custom' boot screen showing, and now am stuck in a boot loop. Although, I'm no longer seeing the scary contact Verizon message.
I had also run into something after hours of digging called root66. So I tried that as well and I'm still stuck in the same position. The custom counter has gone up each time I've flashed.
Vol up + home + power enter the screen saying it's loading custom boot and then the phone vibrates / restarts / hangs in boot.
Help is greatly appreciated!
Click to expand...
Click to collapse
Maybe odin again,if you can get into adb?
in adb type in
Code:
adb reboot download
this should get you into odin mode
If that doesn't work try
Code:
adb reboot recovery
here's an example of how output should look
Code:
Erics-MacBook-Pro:applications eric$ adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
if you do this you this properly you should be in recovery clockwork mod, wipe everything or restore to a previous rom, i hope that helps.
http://goo.im/devs/invisiblek/i535/stock.kernel.tar here's the stock kernel
Odin back to stock rom, odin stock kernel, boot into recovery, wipe data factory reset. Next time read the guide more thoroughly and unlock your bootloader before flashing.
ericerk; adb is not detecting the device. I'm receiving the following message when trying to list devices or using the reboot commands you have recommended; "List of devices attached" and nothing after. Also "error: device not found" Odin is detecting the device.
droidstyle; Those are the steps I followed. The problem is I can not enter into the recovery menu now. When I hold Vol up + Home + Power while the device is booting it attempts to load, vibrates the device, and then hangs in a boot loop. I had also downloaded EZ and unlocked the bootloader before hand. Maybe the mistake I made was to lock it after everything was done? Maybe I misunderstood something I had read about doing so to avoid a push and causing the exact issue I have?
Thanks again!
Why did you relock the bootloader? That was a big mistake!! Now you need to follow section 2...flsh a stock rom and kernel, boot into stock recovery, wipe data, reboot. This time Unlock the bootloader and leave it unlocked!
Just for verification/clarification, the stock rom and kernel I have downloaded are;
Samsung-Updates.com-GT-I8530_XEF_1_20120614154832_nv1pfwdaeb / I8530XXLF3_I8530OXXLF1_HOME.tar.md5
Samsung-Updates.com-SCH-I535-VZW-I535VRALF2_Kernel / kernel.tar
I may have misread something. I read to avoid getting a push from Verizon and possibly locking out the device that the boot loader needed to be locked.
Doing as you've recommended now. Flashing the stock ROM; stock.vzw_root66.tar, kernel, attempting to boot into recovery.
Thank you. Still waiting on this download to Odin the stock image.
If your on a custom rom you will never get a push or OTA from verizon. Also if your stock rooted, you can uninstall all vzw services to block OTA's
When does the custom boot screen come into play? Is this after locking/unlocking the bootloader? Or is this from flashing a custom ROM?
Also the lock icon is in the unlocked position. I'm not sure if this has relation to actually being unlocked or is just a default image showing it's 'custom'
Back up and running! Thank you.
So I've unlocked the boot (will remain unlocked this time) and flashed the following ROM and kernel just as I did last time.
Eschelon's Synergy / Synergy_d2vzw-19Aug12-0509-r39-s
Imoseyon LeanKernel / lk_tw_beta-v0.2.2
Rebooted the device to test and have not received the unauthorized Verizon message yet. The custom boot screen image is gone as well.
thanks for info!
jacksheadache said:
When does the custom boot screen come into play? Is this after locking/unlocking the bootloader? Or is this from flashing a custom ROM?
Also the lock icon is in the unlocked position. I'm not sure if this has relation to actually being unlocked or is just a default image showing it's 'custom'
Click to expand...
Click to collapse
when your bootloader is unlocked the custom unlock screen will go away...reason being there is no longer a secure aboot checking for VZW approved software.
droidstyle said:
when your bootloader is unlocked the custom unlock screen will go away...reason being there is no longer a secure aboot checking for VZW approved software.
Click to expand...
Click to collapse
Thanks again!
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
I have a nexus 5.
16GB model.
5.1.1
Rooted.
TWRP 2.8.6.1
I was about to flash CM 12.1 .
I pressed wipe but it froze, I left it that way for about an hour and decided to research about what is happening. A lot of comments on some thread I read said that turning it off and then on worked for them and I did the same. Now all I get is a flashing Teamwin logo. The only accessible feature of the phone is the Power off/Start/Bootloader/Restart Bootloader thing-y. Whichever of them I press I get the flashing Teamwin logo.
Just wait it takes awhile
@bigglongruler
bigglongruler said:
I have a nexus 5.
16GB model.
5.1.1
Rooted.
TWRP 2.8.6.1
I was about to flash CM 12.1 .
I pressed wipe but it froze, I left it that way for about an hour and decided to research about what is happening. A lot of comments on some thread I read said that turning it off and then on worked for them and I did the same. Now all I get is a flashing Teamwin logo. The only accessible feature of the phone is the Power off/Start/Bootloader/Restart Bootloader thing-y. Whichever of them I press I get the flashing Teamwin logo.
Click to expand...
Click to collapse
Well you still have access to the bootloader luckily. Best part about a Nexus is that they're difficult to actually brick. Boot your phone into the bootloader and either fastboot flash recovery to reinstall twrp or use fastboot to reflash the stock system images.
davehasninjas said:
Well you still have access to the bootloader luckily. Best part about a Nexus is that they're difficult to actually brick. Boot your phone into the bootloader and either fastboot flash recovery to reinstall twrp or use fastboot to reflash the stock system images.
Click to expand...
Click to collapse
Thanks man, that's exactly what I needed. I tried to re-flash TWRP but had the same problem but when I flashed the stock system images everything went back to normal.
bigglongruler said:
Thanks man, that's exactly what I needed. I tried to re-flash TWRP but had the same problem but when I flashed the stock system images everything went back to normal.
Click to expand...
Click to collapse
Glad I could help, and that your phone is up and running again.
Take care.
Hi,
I tried yesterday to return my Nexus 5 to a stock image so that I could do OTA updates. I realised after that I also had to return it to stock recovery because TWRP was not letting it work.
using this tutorial, I booted into the latest TWRP image, which only caused my phone to go into a boot loop, only making it as far as the Teamwin screen. The phone will not load the bootloader to do anything with fastboot.
what are my options?
t.holley.os said:
Hi,
I tried yesterday to return my Nexus 5 to a stock image so that I could do OTA updates. I realised after that I also had to return it to stock recovery because TWRP was not letting it work.
using this tutorial, I booted into the latest TWRP image, which only caused my phone to go into a boot loop, only making it as far as the Teamwin screen. The phone will not load the bootloader to do anything with fastboot.
what are my options?
Click to expand...
Click to collapse
What do you want to do exactly? Restore stock recovery so that you can take the OTA? If you followed either one of the methods on that thread, you should already be stock, i don't get why you booted TWRP again.
Hi,
As I mentioned, following that tutorial, I just booted into the TWRP image. It wasn't that tutorial I used to flash the stock image. All that I did was get back to the stock android.
I originally did try using their method, but wasn't able to get the .sh script to run so I used another tutorial to flash the android image, but didn't have a boot or recovery that I flashed. I was able to download the update now and tried installing, but it would take me to the TWRP recovery and say that the update failed.
I was following the optional steps at the bottom, thinking that was what I needed to lock everything back up, clearly that wasn't right.
t.holley.os said:
Hi,
As I mentioned, following that tutorial, I just booted into the TWRP image. It wasn't that tutorial I used to flash the stock image. All that I did was get back to the stock android.
I originally did try using their method, but wasn't able to get the .sh script to run so I used another tutorial to flash the android image, but didn't have a boot or recovery that I flashed. I was able to download the update now and tried installing, but it would take me to the TWRP recovery and say that the update failed.
I was following the optional steps at the bottom, thinking that was what I needed to lock everything back up, clearly that wasn't right.
Click to expand...
Click to collapse
Just flash the stock recovery image with fastboot
Sent from my Nexus 9 using XDA Free mobile app
That's what I am asking...I can't load into anything on the Nexus to use fastboot, it is stuck loading into this TWRP image.
t.holley.os said:
That's what I am asking...I can't load into anything on the Nexus to use fastboot, it is stuck loading into this TWRP image.
Click to expand...
Click to collapse
Press and hold power for 30 second, the device will try to boot but just keep holding the power. Then press and hold vol down and power. It doesn't boot into the bootloader?
Sent from my Nexus 9 using XDA Free mobile app
Hi,
I tried this again today and was able to get into it. Yesterday it didn't want to boot into it for some reason. Followed the tutorial I posted from the start to re-flash everything, and so far seems to be working. Hasn't loaded into android yet, just stuck on the loading screen, hoping it's just the initial start up that sometimes takes a while.
t.holley.os said:
Hi,
I tried this again today and was able to get into it. Yesterday it didn't want to boot into it for some reason. Followed the tutorial I posted from the start to re-flash everything, and so far seems to be working. Hasn't loaded into android yet, just stuck on the loading screen, hoping it's just the initial start up that sometimes takes a while.
Click to expand...
Click to collapse
FYI the TWRP boot loops are due to MTP bug that was never fully fixed from 2860. It's better than it used to be, but still an issue occasionally, especially if connected to power while you try to get in to TWRP.
I have been running with Nolimit ROM since early on. On Sunday I decided to try Franken. All seemed to go well with the flash but the phone would boot into the red screen. I shut it off and it refused to turn back on. I let it charge overnight and tried to turn it on the next morning. Nada. I did notice that it was showing a device under ports. After doing some searching, I found the tool that OnePlus uses to recover from the hard brick. Installed using the tool and it completed successfully. Upon reboot it would just hang at the initial splash screen. Doing more research I found the Hydrogen OS recovery and tried that. Again, I see the H2OS splash screen but it never boots. I can get into Fastboot and Recovery and have tried clearing everything. Before I go back to the Oxygen OS, is there anything else I can do or is it RMA time?
BTW, the bootloader is now locked, a side effect from using the OnePlus recovery tool.
I almost forgot... because the OS won't boot, It won't allow OEM unlock. Trying to unlock the bootloader gives a failed for remote access.
Thanks in advance.
You can't boot locked with a non-stock recovery. The bootloader won't allow it.
Maybe try running the unbrick tool again. Sorry, if you can get to recovery, you don't need the unbrick tool. You should be able to adb push the full OS to your phone and flash it in recovery.
The stock recovery does not provide a way to flash. At least I don't see anything
Thread closed as OP request.