I bought a used N9 with 6.0.1 on it. Not my first Nexus, I have a 7 and 6, unlocked and rooted.
I unlocked the bootloader, that went fine. I installed TWRP 3.0.1 and can boot that no issues.
I flashed Pure nexus from TWRP and Gapps, that completed without error.
When I reboot, I get a Dialog box Pure Nexus - Starting Android screen .
Then I get my unlock pattern.
After that infinite boot animation. Yes, I left it for a long time, till the battery went out.. Over an hour.
I'm sure I missed something? Like a fastboot flash step or something? Maybe about de-encription?
Thanks
PS yes I googled and read the forums... no luck yet thus the post.
Jeff_in_LA said:
I bought a used N9 with 6.0.1 on it. Not my first Nexus, I have a 7 and 6, unlocked and rooted.
I unlocked the bootloader, that went fine. I installed TWRP 3.0.1 and can boot that no issues.
I flashed Pure nexus from TWRP and Gapps, that completed without error.
When I reboot, I get a Dialog box Pure Nexus - Starting Android screen .
Then I get my unlock pattern.
After that infinite boot animation. Yes, I left it for a long time, till the battery went out.. Over an hour.
I'm sure I missed something? Like a fastboot flash step or something? Maybe about de-encription?
Thanks
PS yes I googled and read the forums... no luck yet thus the post.
Click to expand...
Click to collapse
Try again, but format data and clean flash this time
Related
Sorry I'm a noob at all of this. Successfully rooted my phone today thanks to Honsoon2000's excellent tutorial and toolkit. Then I went to install Android Revolution, which appeared to go successfully and then after I flashed the kernel the phone wouldn't load and just hangs at the quietly brilliant screen. I followed Honsoon's tutorial to the T (or so I thought) and everything went perfectly until right at the end when I flashed the kernel. I can make it back to the bootloader screen though it says "failed to load usb master mode". I can still make it into fastboot and recovery mode...tried recovery, and the process seemed to go sucessfully, but the phone still wouldn't load after...tried reinstalling ARHD-- it's still on the sd card and the install procedure still goes off without a hitch, but the phone still won't load. I've searched around and tried everything I can, to no avail. Any help would be muchly appreciated, and I apologize in advance for being a noob wasting people's time.
Edit: For example, when I follow the steps outlined in the FAQ it asks me to enter the command 'fastboot flash boot boot.img' , but when I do it says 'error: cannot load boot.img'.
Edit 2: So I put my boot.img file from Android Revolution into the data directory of the rooting toolkit and was able to complete the above flashboot command. I was also able to install the ROM off my SD card...however the phone still hangs on the Quietly Brilliant screen...I can't even power the phone down...whenever I try it just reboots...frustrating...really hoping someone can help me...cheers.
Before you begin, make sure that the drivers for the One X+ are installed.
Place the boot image being used on the computer's hard drive.
Boot in to recovery and flash the ROM.
When that is done, boot in to bootloader and connect the phone to the PC via a USB cable.
If the phone isn't in fastboot mode already, use the volume keys to highlight the word "fastboot", then press the power button.
Now, there should be text at the bootloader screen that says "Fastboot USB".
Finally, use the toolkit or command line and flash the kernel with the fastboot command.
This should successfully flash the ROM and the kernel. Make sure you full wipe before flashing a new ROM. If you can't seem to get the new ROM booting, the final choice is to relock the bootloader and run a RUU.
Which phone version you do own? International or AT&T / TELUS?
Did you flashed the correspondant boot.img? Did you cleared the cache? ( fastboot erase cache)
I'm trying to run an RUU but it keeps saying the battery isn't charged enough to flash anything...and this after it's been plugged in all day. Oh dear I think my phone might be done...really sucks :/
Also, it won't let me power the phone down-- every time i try it shuts the phone off briefly and then opens back up to the bootloader screen.
Fixed thanks to sarcasticphoenix. Cheers.
OK so I've tried 3 times to flash a new ROM onto my phone (Android Revolution twice and Eleganzia once) using Honsoon's toolkit...I've followed every instruction to the T as far as I can tell and all 3 times the process has gone perfectly right until the end when I flash the kernel...after that when I reboot the phone it just hangs at the Quietly Brilliant screen. I know how to relock the bootloader, flash the custom rom and get my phone back...but I really want to know what I'm doing wrong so I can install a custom ROM. I know I'm using the right ROM for my phone and am wondering what gives. Being driven crazy here...any ideas what's going wrong here would be helpful. BTW on the last attempt right after I finished and the phone hung I went into the boot loader and followed the instructions in the FAQ for fixing a bootloop...still nothing.
Edit: Solved my problem-- I managed to successfully load eleganzia...the only thing i did differently the last time was flash the kernel BEFORE installing the ROM off the SD card.
jrockwell said:
OK so I've tried 3 times to flash a new ROM onto my phone (Android Revolution twice and Eleganzia once) using Honsoon's toolkit...I've followed every instruction to the T as far as I can tell and all 3 times the process has gone perfectly right until the end when I flash the kernel...after that when I reboot the phone it just hangs at the Quietly Brilliant screen. I know how to relock the bootloader, flash the custom rom and get my phone back...but I really want to know what I'm doing wrong so I can install a custom ROM. I know I'm using the right ROM for my phone and am wondering what gives. Being driven crazy here...any ideas what's going wrong here would be helpful. BTW on the last attempt right after I finished and the phone hung I went into the boot loader and followed the instructions in the FAQ for fixing a bootloop...still nothing.
Edit: Solved my problem-- I managed to successfully load eleganzia...the only thing i did differently the last time was flash the kernel BEFORE installing the ROM off the SD card.
Click to expand...
Click to collapse
That's usually what I do first, flash the kernel and then install the zip via recovery
Sent from my HTC One X+ using xda premium
Which kernel are you referring too? Actually there is one or two kernels available but only for the International version, not the AT&T/TELUS which you seem to have.
I strongly suspect that your boot looping was because you didn't flash the boot.img file correctly or not at all. And you don't seem to install the good ROM version for your phone.
Elegancia has two ROM versions one for International and one for AT&T/TELUS users.
ARHD is for International users.
Please read Q12 of the FAQ.
Lucky Thirteen said:
ARHD is for International users.
Click to expand...
Click to collapse
Lol...yeah I don`t know how I missed that. I ended up getting elegancia successfully flashed and loaded so all is well. In retrospect this was a good experience because there`s nothing like having to get yourself unforked from a bad situation to gain an understanding of what`s going on. Cheers.
I have a couple questions and since I`m not allowed to post yet in the elegancia thread I'll try in this thread first:
1) An elegancia question: Is there a way (widget) to toggle data roaming on and off in this ROM?
2) Is there a way to tweak settings (transparent pull down, selection of launcher etc.) without wiping and reflashing the ROM?
3) What are people's favorite launcher for that ROM? I tried Atom but it was just a guess because I hadn't heard of any of them. I like it so far but am curious about the others.
Hi everyone, so this is my first post here on Xda, heard a lot of good things though
Anyways, I just re-rooted my HTC One M8 at&t model for the second time, I have rooted before, but had some issues so I decided to unroot and relock it, that is until today, when android 5 came out for the developer edition I decided I would try to convert mine so I could install the official ota.
So I unlocked my bootloader and flashed
./fastboot flash recovery openrecovery-twrp-2.8.4.0-m8.IMG
Said it wrote it successfully, so I tried to boot into recovery to flash super su.
When I tried however, it just sat and hung at the "entering recovery" screen.
I held down the power and volume up to get back to my home screen and retried after booting back into the bootloader.
Same thing. Not sure what I did wrong. I installed TWRP for gsm models (like I should have, right?).
Is it possible that somehow the old version of TWRP from my previous rooting experience is creating conflict with the one I just flashed? I'm really new to all this, so thanks for putting up with my uneducated self
Any ideas?
Thanks in advance!-Z
PR4X15 said:
Same thing. Not sure what I did wrong. I installed TWRP for gsm models (like I should have, right?).
Click to expand...
Click to collapse
Right, as long as its not meant for CDMA or the dual SIM version, you are good to go.
Failure to boot into recovery from bootloader can usually be solved by fastboot erase cache, and install TWRP again. Probably just a problem with TWRP not being properly installed the first time around.
Or even try an older version. TWRP 2.8.4.0 is really new, so maybe there are issues.
So I've never had to post anything before as everything I need to find is already here but this one has got me befuddled. I rooted my Moto E (1st gen) and installed clockwork mod recovery. First I installed cm13 to see what 6.0 looks like and it seem to install just fine from cwmod and then I rebooted saw the nice cmMod bootup animation and waited and waited. I got nervous so I looked up a couple Youtube videos and it looks like it can take up to 20 minutes. OK, no big deal as its a pretty low powered phone. Two hours later, I'm in the same place with the boot animation. I eventually just turned it off and restored it back to the factory image without issue. I then attempted to flash cm12 on it and had the same result. Any help or insight is appreciated.
That happened to me the first time you install cm , also I was nervous but I happened to install a custom kernel to see if it worked and it worked !!! if you do not work for you
hetor99 said:
That happened to me the first time you install cm , also I was nervous but I happened to install a custom kernel to see if it worked and it worked !!! if you do not work for you
Click to expand...
Click to collapse
So. how did you fix it? I'm not quite sure what you're trying to say.
sasquatch606 said:
So I've never had to post anything before as everything I need to find is already here but this one has got me befuddled. I rooted my Moto E (1st gen) and installed clockwork mod recovery. First I installed cm13 to see what 6.0 looks like and it seem to install just fine from cwmod and then I rebooted saw the nice cmMod bootup animation and waited and waited. I got nervous so I looked up a couple Youtube videos and it looks like it can take up to 20 minutes. OK, no big deal as its a pretty low powered phone. Two hours later, I'm in the same place with the boot animation. I eventually just turned it off and restored it back to the factory image without issue. I then attempted to flash cm12 on it and had the same result. Any help or insight is appreciated.
Click to expand...
Click to collapse
hey, it's a common problem and don't worry it can be easily solved...
you just need to flash cm11 (you can easily find it here - by percy_g2), you don't have to flash KitKat gapps. flash cm11, let it boot for the first time, once it boots, just reboot to recovery,wipe everything (except internal storage and sdcard ofcourse ) flash cm12 (of course with lollipop gapps) or cm13 (with marshmallow gapps) and the rom will boot just fine.. it'll take some time for the first boot (because android now use ART runtime), but it'll boot,
just for the record gapps must be flashed right after the rom. use opengapps....
and last but not the least - use latest TWRP 2.8.7.0 (ofcourse - can also be found on xda) since many roms doesn't support CWM nowadays
and just for the info, once you flash cm11 and let it boot, you won't need to do that again, you can flash any rom after that anytime, ofcourse unless you WANT to use cm11
booo159159 said:
hey, it's a common problem and don't worry it can be easily solved...
you just need to flash cm11 (you can easily find it here - by percy_g2), you don't have to flash KitKat gapps. flash cm11, let it boot for the first time, once it boots, just reboot to recovery,wipe everything (except internal storage and sdcard ofcourse ) flash cm12 (of course with lollipop gapps) or cm13 (with marshmallow gapps) and the rom will boot just fine.. it'll take some time for the first boot (because android now use ART runtime), but it'll boot,
just for the record gapps must be flashed right after the rom. use opengapps....
and last but not the least - use latest TWRP 2.8.7.0 (ofcourse - can also be found on xda) since many roms doesn't support CWM nowadays
and just for the info, once you flash cm11 and let it boot, you won't need to do that again, you can flash any rom after that anytime, ofcourse unless you WANT to use cm11
Click to expand...
Click to collapse
Thanks for this. I'll give it a go.
sasquatch606 said:
Thanks for this. I'll give it a go.
Click to expand...
Click to collapse
That worked. I'll honestly probably keep it at cm11 unless I can think of a real reason to upgrade. Thanks again!
In my case, I can't see anything in my screen.
sasquatch606 said:
So I've never had to post anything before as everything I need to find is already here but this one has got me befuddled. I rooted my Moto E (1st gen) and installed clockwork mod recovery. First I installed cm13 to see what 6.0 looks like and it seem to install just fine from cwmod and then I rebooted saw the nice cmMod bootup animation and waited and waited. I got nervous so I looked up a couple Youtube videos and it looks like it can take up to 20 minutes. OK, no big deal as its a pretty low powered phone. Two hours later, I'm in the same place with the boot animation. I eventually just turned it off and restored it back to the factory image without issue. I then attempted to flash cm12 on it and had the same result. Any help or insight is appreciated.
Click to expand...
Click to collapse
In my case, I can't even access the boot-loader in my mobile. May be very rare and bad situation in my case. I am not able to understand, what to do.
I bought my Moto X Pure used, and the "bootloader unlocked" message pops up everytime I boot up. However, a new security update came out this morning. But, when the update tries to re-boot, I get the TWRP main screen. The update never takes hold and keeps trying to re-boot. Which brings up the TWRP screen over and over. I've never rooted or worked with custom ROMs, so I'm in the dark here. Any ideas how I get out of TWRP Hell? Thanks.
rsdin559 said:
I bought my Moto X Pure used, and the "bootloader unlocked" message pops up everytime I boot up. However, a new security update came out this morning. But, when the update tries to re-boot, I get the TWRP main screen. The update never takes hold and keeps trying to re-boot. Which brings up the TWRP screen over and over. I've never rooted or worked with custom ROMs, so I'm in the dark here. Any ideas how I get out of TWRP Hell? Thanks.
Click to expand...
Click to collapse
Hi,
Your device is on Twrp Recovery, so official stock OTA's won't get installed via custom recovery like TWRP.
They requires stock recovery. Due to scripts / modifications etc..
Meanwhile, ive found this for you, follow that and fix your device.
Good luck!!
I thought you guys might find this amusing, and hopefully it will help some people that get into a similar situation as myself. First, a little background - I rooted and installed Alliance Rom years ago back before the bootloader was unlocked. This worked amazing for me for a long time but I've recently had some weird issues with my phone so I decided to do a factory reset.
I went into settings, clicked factory reset, and then my phone got into a boot loop on recovery. I remember from before I had to do a regular boot then click recovery at the prompt instead of doing the factory recovery so I did that.
Instead of doing a normal wipe, I wanted to wipe everything on my phone and start from scratch so I did the full wipe (in what I think was TWRP or safestrap or whatever). When I went to reboot my phone it had a message like "are you sure? there's no OS installed" and I clicked ok. Well now I couldn't get the phone to boot into anything except download mode so at least I can use Odin.
I'm frantically searching google to try and find ways to install some sort of recovery so I could load AllianceRom again since I still had the zip file for it. Eureka, I found TWRP for my phone! I tried to flash TWRP through Odin but that doesn't work because my bootloader wasn't unlocked.... I remember this from last time ... all of the places I found online to install any sort of recovery required the phone to be booted into android.
So I'm clicking around and someone has a recovery randomly posted in a thread so I install it thinking, what the hell, what's the worst that could go wrong. So I install it through Odin and boot into normal recovery and I get this message saying my phone has been tampered with and to go to a verizon store immediately! Oops... upon further investigation (looking at the download screen), I tripped the knox flag... oh well, it's not like my phone is in warranty anymore (I got it on release day).
I search around looking for what I should do next and I found a thread that talked about being on complete stock, rooting, then unlocking the bootloader. I download all the files I need (newest firmware here - https://www.sammobile.com/firmwares/galaxy-note3/SM-N900V/ and thread here - https://forum.xda-developers.com/ve...guide-ob6-of1-root-bootloader-unlock-t3439010) to go back to stock and flash in Odin. Actually I didn't download from sammobile.com because it was downloading too slow so I just googled the file name and found it somewhere else faster, go figure.
Everything seems to be going ok then all of a sudden FAIL in Odin... Ahhh what the heck do I do now? Try again obviously! Second try works woo hoo! Phone start booting up, things are looking good!!! hooray!! But wait... it's taking forever to start and it's stuck on the Verizon logo... uh oh... taking way too long to boot up so I pull the battery and try again. Boots right in saying that android is upgrading so I think I'm finally in the home stretch here.
I try to run the ArabicToolApp for Root but I installed the latest firmware which isn't supported DAMN IT! Downloaded the correct firmware (OB6!), flashed in Odin, same problem before where it was stuck on the red verizon screen, pulled battery, rebooted, finally time to get root!
Phone finally boots into OS and I get a popup "unfortunatley com.google.process.gapps has stopped" great... and it keeps coming up over and over again after I hit ok... just my luck! Reboot again to see if that fixes the issue. Seems weird that I didn't have to go through all the initial setup stuff I did on the other version I installed... hmm... or maybe it was because I pulled the battery on the red verizon screen? Whatever. I somehow manage to get to options to do a factory reset and I let the verizon screen stay on a while this time. I'll go take my contacts out and give my wife some love while I wait
Come back and the phone is at the setup wizard, this is good news. Enabled USB debugging, installed root, done! Thank god!
Next I want to unlock the bootloader. I follow the steps here which aren't very clear (I'm guessing on purpose for novice computer users) - https://forum.xda-developers.com/ve...l/official-note-3-verizon-bootloader-t3359370
1. I installed eMMC from the play store to make sure my CID started with a 15, it does so I know I'm good to use the hack.
2. I installed both files in the unlock kit (adb and driver setup)
3. Fired up adb, navigated to where I had unlock_n3, and ran through the first part of the code once, reboot my phone, checked that the CID was the developer CID, and then ran the second part of the code three times before it worked
I verified the bootloader was installed correctly by trying to install TWRP through Odin, which worked!
I'm going to try out Jasmine Rom since it's a popular one that is on 5.0. My SD card only showed 30 megs free or something like that, so I formatted it from within android and copied the zip file over and installed the Rom through TWRP. Rom installed just fine, so I did one last factory reset which worked great and I think I'm finally good to go!
If you have any questions or run into any issues feel free to reply here and I'll try to help as much as I can.
Glad it worked out for you in the end.
From making a few mistakes I know that sinking feeling "oh no, what have I done?"
FWIW, the bootloader unlock method (in principle) works from nearly ANY ROM which is rooted - so, you would have saved yourself a bunch of time if you had started with that before you wiped the Alliance ROM. So long as you have root and a CID value that starts with 0x15, you just need root privileges - no need to return to stock and re-root.
(The "in principle" part is that there were several bugs in the "safety checks" portion of the unlocker binary that were sensitive to the OS revision, so you might have to search through the unlock thread to find a version of the unlock binary that is compatible with whatever rooted ROM is on the phone when the unlocking is attempted.)
good luck
PS The AryaMod ROM (w/ phantomOne kernel) is pretty solid - Marshmallow w/ S-Pen apps, too! As with any other dev ROM, there are a few sharp edges, but mostly everything works (except NFC).
.