First off, MODS please let me know if this is the wrong section but as it was about rooting/unlocking the nexus 9 I figured this was the correct forum.
I went with chain fires unlocking method, after unlocking and rebooting i forgot to go back and set the device up and enable USB debugging priot to rooting. Now where my problem lies is since that mistake my device attempts to reboot but sticks at rebooting with the spinning red, green, blue, and yellow dot spinning in somewhat of a circle like its attempting to boot but it never goes anywhere. This appears to be a boot loop minus a restart in between time. anyone have an idea of how to start this and start from scratch? Any help will be much appreciated.
Did you try to factory reset? Boot into boot loader and factory reset
di11igaf said:
Did you try to factory reset? Boot into boot loader and factory reset
Click to expand...
Click to collapse
Yes, i was able to resolve it. I downloaded the nexus tool kit, relocked and loaded stock firmware back on it, this fixed the issue, then using the nexus tool kit reunlocked and rooted with no problem. unsure why it got stuck on the boot image but all is resolved now running fire and ice kernal with dirty unicorns ROM.
thanks for the suggestion though.
Related
I rooted my GS4 and tried to install PureG but ended up in a boot loop at the Samsung Galaxy S4 screen. I fixed it by flashing the stock image through ODIN following. I then went to root it again using the guide by open1your1eyes0. I am now stuck in a boot loop yet again, however this time it says "Samsung" then underneath that is an open padlock, and under that it says "custom". I have tried everything I could think of with no luck. I have tried looking around for people with similar problems but again no luck.
Can you boot into recovery?
Flash-oholic on my SCH-I545
I got it. It was just being glacially slow booting up. I thought it was stuck so I kept resetting it. It was a dumb mistake. Thanks for the reply though.
No problem, if it hangs up in the future you may have to fix the permissions from recovery mode. FLASH ON!
Flash-oholic on my SCH-I545
Interesting thing happened today which has basically put my phone in a death spiral state. The battery died and after charging it a while I went to power it back on and found it in a boot loop state. I can get into the bootloader, but from there if I select recovery it reboots and the white bar on the right side of the screen fails to fill up, then the phone reboots. I've tried flashing two different versions of TWRP from the bootloader and it still exhibits the same issue.
HBOOT 1.12.1111
RADIO 1.12.11.1210
S-OFF
I was running CM10.1 without much issue until the power issue.
Any thoughts?
Thanks to Zanzibar for helping me work through this on IRC. Eventually the steps outlined here: http://forum.xda-developers.com/showthread.php?t=2338391&highlight=boot+loop did the trick.
fastboot erase cache
fastboot reboot
The device started booting but hung on the CM logo for far too long. I hard rebooted and installed an updated version of TWRP and then wiped and flashed the ROM over again. More updates to follow.
Well the device worked for the night but when I rebooted it this morning it immediately began the boot loop situation again. I RUU'd once and it got stuck in another boot loop. I got it to boot after hard powering down and it loaded the factory ROM. I rebooted back to the bootloader and flashed TWRP 2.5.0.0 and tried to reboot. Another boot loop. Hard power cycling didn't solve it either, so I pushed the RUU for a second time. Now the device refuses to boot into anything other than the boot loader -- the initial issue from this post -- and no amount of hard power cycling makes a difference.
The phone is currently showing as LOCKED in the boot loader so I dropped it off at the Sprint store to see if they could find anything physically wrong etc. More updates as they are discovered in the hopes that if someone else ever experiences this, they have something to reference.
Thanks for posting. Did you solve the problem? I think I'm having something similar.
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
Alright, so after having my Fire HD 6 rooted for a few months I started experiencing some random restart issues. I decided to reset to Factory Defaults as I believe that it doesn't touch root (Please verify that one.)
Whenever I clicked on Facotory Reset, however; it immediately restarted and DID NOT RESET.
Then I tried to boot into TWRP and just reflash 4.5.3 (Downgrade) but when I tried to boot into recovery nothing happened, it just booted as normal. Thinking that it was just an error on my part, liking the wrong buttons, etc, I tried running 'adb reboot recovery'
This yielded the same result, just a normal reboot.
I have since unrooted my Kindle to try to update to 5.0.1 (To downgrade again)
Upon trying to update, I restart with no change just like in Factory Reset.
This leaves me with no Root, and no Recovery.
Next I tried using Fastboot to reset it, which now leaves me in a reboot loop that's stuck on the "Fire" logo.
TL;DR:
I have no root, I cannot get into recovery, I cannot access bootloader since ADB doesn't have permission without me giving it (Again, bootloop)
Overall, I'm kind of screwed, any help appreciated.
KeybladePaladin said:
Alright, so after having my Fire HD 6 rooted for a few months I started experiencing some random restart issues. I decided to reset to Factory Defaults as I believe that it doesn't touch root (Please verify that one.)
Whenever I clicked on Facotory Reset, however; it immediately restarted and DID NOT RESET.
Then I tried to boot into TWRP and just reflash 4.5.3 (Downgrade) but when I tried to boot into recovery nothing happened, it just booted as normal. Thinking that it was just an error on my part, liking the wrong buttons, etc, I tried running 'adb reboot recovery'
This yielded the same result, just a normal reboot.
I have since unrooted my Kindle to try to update to 5.0.1 (To downgrade again)
Upon trying to update, I restart with no change just like in Factory Reset.
This leaves me with no Root, and no Recovery.
Next I tried using Fastboot to reset it, which now leaves me in a reboot loop that's stuck on the "Fire" logo.
TL;DR:
I have no root, I cannot get into recovery, I cannot access bootloader since ADB doesn't have permission without me giving it (Again, bootloop)
Overall, I'm kind of screwed, any help appreciated.
Click to expand...
Click to collapse
Please help.... I see you random viewer >.>
I think if someone had an answer they would have posted. Unfortunately, fastboot doesn't work on the 2014 HDs, and it sounds like that's what put you into the bootloop. At this point I think your only option is to contact Amazon for replacement if you're still under warranty.
DoLooper said:
I think if someone had an answer they would have posted. Unfortunately, fastboot doesn't work on the 2014 HDs, and it sounds like that's what put you into the bootloop. At this point I think your only option is to contact Amazon for replacement if you're still under warranty.
Click to expand...
Click to collapse
You're sure fastboot doesn't work? I believe I have used it prior to this with no issues. (By the way, warranty is out >.<)
KeybladePaladin said:
You're sure fastboot doesn't work? I believe I have used it prior to this with no issues. (By the way, warranty is out >.<)
Click to expand...
Click to collapse
Bootloader screen doesn't indicate fastboot mode. Getvar doesn't return anything. If flash commands worked, I'm sure someone would have reported it.
If you haven't tried all button combinations, you should. (You know, hold down power; try power and vol down; try all three.) Without recovery that's all I can suggest. Sorry this happened.
I got the same problem too.
I tried to root and install gapps follow this tutorial. Everything work perfectly.
One day, my Fire's battery was empty and it turned off. I charged it and when it started, it falt in bootloop. The screen show amazon about 8sec and reboot.
I booted into twrp and flashed only 2 files update-kindle-full_ariel-20.5.2.2_user_522053520 and supersu, try to make it work but it didn't
Now, when i hold power button , "Amazon" and then "Fire" appear and it stuck there.
I tried to get into recovery by power and volume+ but didn't work, the screen show "Amazon" and reboot and stuck on "Fire" again.
What should I do now?
Sorry about my English.
So I recently got a Nexus 9. I think it was affected by the battery issues with android nougat. I rooted and used greenify and got much better battery life but decided I wanted to unroot and see if over a couple days the battery life would have gotten better. So I connected to my computer and stupidly sent the "fastboot flashing lock" command and now my Nexus is stuck in a boot loop because of TWRP. I knew that locking the bootloader would initiate a factory reset but didn't take into account that TWRP may affect that so now I can not use my Nexus. The device says it is a developer edition and not intended for personal use and I don't I know what to try. Just letting everyone know I only tried to sideloading and flash. I appreciate everyone who takes the time to read this and try to help.
Have you tried following instructions from google to flash a factory image ?
https://developers.google.com/android/images
I have but I can't flash due to the bootloader being locked and I can't sideloading because every time I tried it just errors or does nothing
AUSTIZ1997 said:
I have but I can't flash due to the bootloader being locked and I can't sideloading because every time I tried it just errors or does nothing
Click to expand...
Click to collapse
Did you try booting your nexus to fast boot and execute fastboot oem unlock?
I have, it just send me an error message
Update, I was able to finally get into the custom recovery and tried to flash the stock recovery and now it just boots into fastboot mode but I got rid of the custom recovery (as far as I know) and the boot screen that said the tablet was a developer device
Same problem here in May 2017, the OTA update prompted by Google sent the device into a bootloop. As the Bootloader was locked and there was no way to change to USB debugging mode it wasn't possible to use Recovery mode or to flash an OTA. Wiped data cache, tried all options in HBoot menu, tried flashing OTAs and full block OTA didn't work either. Just stuck in bootloop.
Repair shop encountered same problems so they then suspected the logic board. They heated it up to reflow the solder and success! Logic board may fail again through dry joint but I believe this risk can't be avoided by switching manufacturer as they all use the same component-to-board soldering practice.