Related
Installed 4.4.1 via TWRP this morning, but it is stuck in reboot. Just keeps doing the colliding circles!
Tried rebooting a couple of times. Can get to fastboot, But device isn't seen by adb, and fastboot only shows start (no recovery option)
Any ideas at this point?
RedBullet said:
Installed 4.4.1 via TWRP this morning, but it is stuck in reboot. Just keeps doing the colliding circles!
Tried rebooting a couple of times. Can get to fastboot, But device isn't seen by adb, and fastboot only shows start (no recovery option)
Any ideas at this point?
Click to expand...
Click to collapse
I would recommend flashing the 4.4 stock factory image from here in fastboot mode. Then once your device is booting up properly again I would recommend taking a look at this guide to properly install the 4.4.1 update.
You MUST either side load or safer still, un-root(if rooted) and flash stock recovery and sideload and then re-flash custom recovery and re-root if needed.
If you are able to get to fastboot:
Fastboot flash recovery recovery.img ( use stock)
Fastboot reboot-bootloader
go into to stock recovery - wait for dead droid, one you see him, go into recovery by holding volume+ and power at same time
follow the orange instructions to sideload via adb - which should now work
reboot and validate all is well
reboot into bootloader and re-flash your custom recovery and root (if needed)
Enjoy.
planet_x69 said:
You MUST either side load or safer still, un-root(if rooted) and flash stock recovery and sideload and then re-flash custom recovery and re-root if needed.
If you are able to get to fastboot:
Fastboot flash recovery recovery.img ( use stock)
Fastboot reboot-bootloader
go into to stock recovery - wait for dead droid, one you see him, go into recovery by holding volume+ and power at same time
follow the orange instructions to sideload via adb - which should now work
reboot and validate all is well
reboot into bootloader and re-flash your custom recovery and root (if needed)
Enjoy.
Click to expand...
Click to collapse
Thanks, I eventually got it. I was really puzzled that I couldn't select recovery from the bootloader. All set now though, thanks!
I hae also updated to 4.4.2 but now my N10 is stuck at the Google start page. Please help?
jalize said:
I hae also updated to 4.4.2 but now my N10 is stuck at the Google start page. Please help?
Click to expand...
Click to collapse
If you mean stuck at boot animation, then I suspect you used TWRP to flash?
I found that TWRP was not able to clear caches, so I use CWM instead. Worked like a champ...
RedBullet said:
If you mean stuck at boot animation, then I suspect you used TWRP to flash?
I found that TWRP was not able to clear caches, so I use CWM instead. Worked like a champ...
Click to expand...
Click to collapse
No I used the adb sideload command for the OTA. That all went well but now I'm stuck at the google page even before the animations begin!
jalize said:
No I used the adb sideload command for the OTA. That all went well but now I'm stuck at the google page even before the animations begin!
Click to expand...
Click to collapse
Hold volume up and power to get it to recycle, and immediately hold all three buttons down to get to bootloader. Try clearing your caches from recovery
RedBullet said:
Hold volume up and power to get it to recycle, and immediately hold all three buttons down to get to bootloader. Try clearing your caches from recovery
Click to expand...
Click to collapse
Tried that already, still stuck at Google page before animations. Everything is stock on this tablet with root.
jalize said:
Tried that already, still stuck at Google page before animations. Everything is stock on this tablet with root.
Click to expand...
Click to collapse
Hi,
Try flashing it fresh stock again, factory reset your device from recovery, download the stock image file from here, untar it, then unzip the zip inside the tar and you'll get some files (.img). Copy those files to your fastboot folder and then open a cmd there. (Guessing that you're using Windows)
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
If you're using Linux, do the same, but instead of only fastboot use:
Code:
sudo ./fastboot
Then boot it. I had the same problem when I updated mine to 4.4.1, but I did one thing a little different... Instead of fully "stocking" it again, I flashed back 4.3, flashed 4.4 OTA and then let it boot, without wiping my data, after all it was running like this before. Worked. But as I'm unsure of your situation I think it's more secure and easier to fully stock it again.
Hope this helps,
~Lord
PS.: Remember to put your device in fastboot mode!
EDIT - UPDATED INSTRUCTIONS 12th May 2014
Due to the partition sizes being different in the GPE RUU it is not simply a case of flashing a sense rom in recovery. You will experience problems if you do this. This might involve getting the storage encrption message, bootloops, freezing etc etc.
This thread is specifically for users who have problems getting back to sense. Solution is below. If you have alternative solutions that have worked without issues please post.
I have tried to make them as simple as possible. This guide assumes you are S-Off otherwise how did you get here. (
This does not apply if you have installed a GPE ROM. You can flash as normal through recovery. (using instructions of new rom)
Thanks to @exad for his continuing support/assistance throughout the thread, as well as @graffixnyc for the GPE RUU and both he and @navalynt for finding the initial fixes.
It will be much easier if you have your new Rom on your external sdcard prior to starting this. It will also stop a number of problems if you have SuperCID (11111111) If you don't know how to - FASTBOOT Commands
1. Enter the command "fastboot oem readcid". Make and KEEP a note of your original CID.
2. Enter the command "fastboot oem writecid 11111111"
3. Enter the command "fastboot read cid" [it should confirm your CID is 11111111]
4. Press the volume down button twice on your phone and navigate to reboot bootloader, then hit power button to reboot the bootloader.
5. Bootloader will also say "CID-11111111" now to confirm (Thanks to @xl VipeR lx ) Also to @umjammerlammy for the GENTLE reminders to include this
Make sure the firmware file and twrp recovery are in your Android directory on your PC - Mine is
C:\Users\Grentuu\AppData\Local\Android\android-sdk\platform-tools\
During this process you may find that when you reboot the phone starts to boot into android. Mine did but simply had the GPE animated logo but never entered GPE. All you do is press Vol up and power for about 10 seconds to reset. As soon as it resets press vol down and power to get back to bootloader.
Flash 1.54.401.5 firmware from Here
Fastboot Method
Boot device into FASTBOOT mode either by adb reboot bootloader or Vol down & Power (device should show FASTBOOT USB)
Make sure the firmware file to be flashed is in your android folder
Open a command prompt from the folder where fastboot resides. (Hold shift key/right click in the dir to get menu - left click on Open Command Prompt here.)
Run the following commands:
fastboot oem rebootRUU (this will reboot the device into RUU mode in preparation for zip flashing)
fastboot flash zip 1.54.401.5-W_Splash.zip (the name of the zip should EXACTLY match the name of the file you're flashing)
It will fail the first time. Run the same command AGAIN until you see it has flashed successfully.
I repeat - Run the same command TWICE until you see it has flashed successfully.
Once complete, type fastboot reboot-bootloader The hyphen is required.
Some users have stated this firmware (1.54.401.5) did not work for them as they weren't GSM and reboots just threw them back to recovery. If this happens try a stock (your original e.g. T-mobile) firmware then follow the rest of the process.
Boot into stock recovery
Factory reset
Reboot into bootloader
Flash TWRP - command = fastboot flash recovery openrecovery-twrp-2.7.0.2-m8.img (The must match exactly the name of the recovery you are flashing and remember the recovery file must be in your android folder)
Boot into TWRP
Go into Wipe menu
do a full factory reset wipe
Reboot back into recovery
Install rom
Profit
These have worked for me everytime (Change count =19)
Thanks for this. I'm about to give it a shot now.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
---------- Post added at 05:08 PM ---------- Previous post was at 04:40 PM ----------
For some reason the firmware wont flash in twrp. Should I sideload the firmware?
Sent from my GT-P5210 using XDA Premium 4 mobile app
To flash a firmware you must be in bootloader/fastboot mode.
Fastboot oem rebootRUU
Fastboot flash zip firmwarefilename.zip
Then again
Fastboot flash zip firmwarefilename.zip
Fastboot reboot-bootloader
exad said:
To flash a firmware you must be in bootloader/fastboot mode.
Fastboot oem rebootRUU
Fastboot flash zip firnwarefilename.zip
Then again
Fastboot flash zip firnwarefilename.zip
Fastboot reboot-bootloader
Click to expand...
Click to collapse
Thanks. Understood, I was just reviewing my steps for the conversion. I really just want to try out that new Sense rom and then I'll probably revert back. BRB...I'll let you know how it goes.
Bear in mind you must have S-off to flash a firmware that way.
exad said:
To flash a firmware you must be in bootloader/fastboot mode.
Fastboot oem rebootRUU
Fastboot flash zip firmwarefilename.zip
Then again
Fastboot flash zip firmwarefilename.zip
Fastboot reboot-bootloader
Click to expand...
Click to collapse
Those are the instructions in post 1 the original thread.
The issue is with people wanting to go back to sense
This thread is about returning to sense. Flashing a firmware is always the same. It's the firmware itself that's different...
Here is where I am at..
I converted to GP easily and it worked well.. I wanted to convert back so I installed twrp first, then through twrp installed the 1.54.401.5 firmware.
Installing that firmware removed twrp and the rom. So I am without an OS at all, and have stock recovery.
Is there anyway I can flash a custom recovery or a rom via the stock firmware/recovery?
My computer will not recognize adb devices. But it used to obviously.
I have an SD card.
Any help and I will be sooo grateful. (maybe even donate)
Thanks!
You can't flash a firmware through recovery... You can flash a stock recovery after the steps listed above if you like. See the stock backup thread.
You can flash any recovery through fastboot... Adb only works with the rom booted or with custom recovery booted.
Thanks will try it out.
exad said:
You can't flash a firmware through recovery... You can flash a stock recovery after the steps listed above if you like. See the stock backup thread.
You can flash any recovery through fastboot... Adb only works with the rom booted or with custom recovery booted.
Click to expand...
Click to collapse
So what do I do in this situation with no rom installed only 1.54 firmware and stock recovery.
Flash twrp
exad said:
Flash twrp
Click to expand...
Click to collapse
I have no rom installed, so it wont show in adb devices.
PunchLick said:
I have no rom installed, so it wont show in adb devices.
Click to expand...
Click to collapse
You flash recovery via fastboot, no need for a rom.
Just make sure you have the proper fastboot drivers from htc.
Dmaxon said:
You flash recovery via fastboot, no need for a rom.
Just make sure you have the proper fastboot drivers from htc.
Click to expand...
Click to collapse
ADB devices shows no devices. If i had custom recovery this would be so much easier, but im using 1.54.401.5 firmware with stock recovery and no ROM.
Just dont know what to do to get a working device again. All i can do is boot into stock recovery, hboot and fastboot.. but computer shows no device.
PunchLick said:
ADB devices shows no devices. If i had custom recovery this would be so much easier, but im using 1.54.401.5 firmware with stock recovery and no ROM.
Just dont know what to do to get a working device again. All i can do is boot into stock recovery, hboot and fastboot.. but computer shows no device.
Click to expand...
Click to collapse
I would recommend the All-In-One Toolkit. This will allow you to fastboot the recovery, even though the pc doesn't recognize it. This has worked for me in the past.
Meanwhile, I get the following error message when attempting to flash the 1.54...
Any suggestions guys???
Problem solved. I had not supercid. After I did that, I was able to successfully flash 1.54...
Why post steps if your not willing to help?
The steps in the OP can still cause issues for some people.
Sent from my HTC One_M8 using Tapatalk
Ideas4ya said:
I would recommend the All-In-One Toolkit. This will allow you to fastboot the recovery, even though the pc doesn't recognize it. This has worked for me in the past.
Meanwhile, I get the following error message when attempting to flash the 1.54...
Any suggestions guys???
Problem solved. I had not supercid. After I did that, I was able to successfully flash 1.54...
Click to expand...
Click to collapse
Can you elaborate a little on which options etc, because that sounds fantastic and would help me so much!
PunchLick said:
Can you elaborate a little on which options etc, because that sounds fantastic and would help me so much!
Click to expand...
Click to collapse
When you open the all in one...the 3rd option on the top right is what you need. Follow the step, even if fastboot says device is not connected, this will still send the recovery to your device as long as you're in the bootloader.
I will never understand why people play with there phones and have no understanding of adb and fastboot commands with the bootloader. if people would learn that first there wouldn't be so many threads when they get stuck. tool kits are bad it makes people lazy. but I appreciate the devs who make them
Hi everyone,
I've run out of ideas on this one and other threads couldn't really help me/were closed already.
I tried CM, stock android by Ivan and M1cha as well as some others, but about a month ago, I was curios for MIUI 6 based on Lollipop for my Mi2s and changed from M1cha's CM12 5.0.1.
Now that I've seen that Ivan published his 5.1.1 I wanted to try it out. He also provides us with a modified custom recovery that I wanted to flash.
First, I renamed the file to update.zip and tried to flash it in Mi-Recovery 2.0.1, which didn't work due to the failing signature verification.
Also, choosing update package in the Updater app in MIUI didn't work out, it immediately tells me something went wrong.
Then I thought, why not use fastboot? That worked before.
Not this time. I tried the simple way, meaning just fastboot flash recovery recovery.img: Then, bc it didn't work, I first erased the recovery partition and then flashed the recovery.img, which was still unsuccessful.
Whenever I try to enter recovery mode, my phone just gets stuck showing the MI logo and not doing anything.
I can reenter fastboot mode or simply reboot to the system as usual, except for when no system is installed.
When I gave up on the custom recovery thing, I simply tried to flash the ROM via update.zip methods, as well as via fastboot. None of them worked, either because the signature verification fails (stock recovery) or because the zip file does not contain the android-info.txt and the other txt file.
As mentioned above, upon entering fastboot -w and then flashing the recovery.img, I can suddenly enter recovery mode. This sucks!
TL;DR: No usual method of flashing either custom rom or recovery works (to my knowledge)
Can anyone help me? I know its stupid but I start feeling kind of boxed in on MIUI.
Thanks in advance
fastboot oem unlock
fastboot flash recovery recovery.img
unfortunately, that didn't work either...
leonfromotown said:
unfortunately, that didn't work either...
Click to expand...
Click to collapse
Do fastboot devices and tell us the output
SkiFire13 said:
Do fastboot devices and tell us the output
Click to expand...
Click to collapse
5b799fb fastboot
looks just the way it did before
Hi people...
Everything was going so smoothly... bootloader unlock... root... some nice root apps... free paid games... and my p8 lite was just feeling so good... until... I flashed twrp with flashify under the name of boot.img... Am I stupid or what?! Now I can only get 2 scenarios... when i turn on the phone it goes directly to twrp. In twrp i get the option to go the bootloader screen... If I choose system it goes back to twrp... I can't get it to start. I downloaded the official tar.gz from emui site but I dont know how can I install it. PLEASE HELP... What should I do in this case?! I miss my baby...
Thanks in advance
You have to restore stock recovery in fastboot mode.
arviit said:
You have to restore stock recovery in fastboot mode.
Click to expand...
Click to collapse
How do I do that?! If I wanted to wipe my phone completely and re-install the OS would be better to do it using twrp or stock recovery?
Thank you very much
Sorry, i misunderstood. If you flashed twrp as boot.img, reflash stock boot in fastboot mode.
flash stock boot.img in fastboot mode
and then flash twrp as recovery
will be like this
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash recovery TWRP.img
fastboot reboot
use the boot.img from stock rom and twrp image you downloaded
Oh no!
Now I made some serious **** to my baby... guess now i'll have to send it to huawei to fix it. I made a full wipe like if it was format c: in computers... everything is gone (i didnt had any personal data) it doesnt have OS even. But when I still had twrp i tried to flash boot.img and recovery.img and now when i start it goes directly to bootloader screen but saying "please update system again" and where it used to say phone unlocked it now says (in red letters):
Error!
Func NO: 10 (boot image)
Error NO: 2 (load failed!)
I was able to get to eRecovery with usb connected but when i choose to download e install the new version it gives me the message "wifi starting failed".
It also does not get any instuction with fastboot. but hi suite starts when I connect it. Strange?!
What do you think? Should I send it to huawei? Or is it possible for me to make it work again?
Also tried UPDATE.APP function and all give me fail message.
I'm going crazy!!!! But I love to mess around with android... To me this is the android essence. Fortunately I have a lumia for when my baby doesnt work.loooool
Thank you all
I don't understand why you don't use fastboot. Everybody told you to use it. In our phone situation, without custom kernel or rom, twrp is for experimentation and you cannot mix things.
arviit said:
I don't understand why you don't use fastboot. Everybody told you to use it. In our phone situation, without custom kernel or rom, twrp is for experimentation and you cannot mix things.
Click to expand...
Click to collapse
Well, you warned me... but sometimes i do these kind of *****... So, in this situation you think it's better to send it or is there way to fix this.
By the way, when I enter huawei eRecovery and I get the option to download the firmware through wifi and it says wifi starting failed, is there any way to make this work? And to fastboot do we need to open cmd as administrator to make it work? Because if Hi suite detects the phone I should also be able to fastboot it right?
Thanks for your patience
Just use fastboot aand flash everything
Recovery
Boot
Systme
Cust
jabonloco said:
flash stock boot.img in fastboot mode
and then flash twrp as recovery
will be like this
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash recovery TWRP.img
fastboot reboot
use the boot.img from stock rom and twrp image you downloaded
Click to expand...
Click to collapse
hello I have p8 lite unlocked and rooted, yesterday I wanted to install the TWRP 2.8.7. but I was wrong and I installed twrp for the p8 and not p8 lite.
When I go into recovery mode my phone locks that read huawey, I tried with fastboot command to delete the wrong recovery and install the right of the p8 lite but the result does not change, my phone locks that read huawey
i think The commands that you wrote and that I have quoted are also fine for my case, it's' true?
i have version firmware b133 which boot.img from stock rom?
Try to reflash stock boot.img too.
arviit said:
Try to reflash stock boot.img too.
Click to expand...
Click to collapse
but Ido the extraction of the boot.img from the update version b133?
Hi everyone!!
First of all, thanks to everybody who helped me with this situation.
I now am using my baby again as if it was new. I wiped him completely as i stated before and it was as easy as finding the right firmware (136a) and using the vol down + vol up + power button technique. I put the UPDATE.APP file inside a folder named dload in sdcard using other phone (with my p8 was impossible). After that rebooted the device, pressed those 3 buttons and the instalation started successfully.
I just cant explain how happy i was. I stayed 3 days without it.
After that I have been messing with fastboot so thanks to everyone who made me realize that i didnt need to do all of this, but well, A full wipe is always welcome.
Is there any custom kernel on the way for overclock my baby?
Please explain to me how do I put SOLVED in this thread as my problem is already solved...
Thanks
siul_lasc said:
Hi everyone!!
First of all, thanks to everybody who helped me with this situation.
I now am using my baby again as if it was new. I wiped him completely as i stated before and it was as easy as finding the right firmware (136a) and using the vol down + vol up + power button technique. I put the UPDATE.APP file inside a folder named dload in sdcard using other phone (with my p8 was impossible). After that rebooted the device, pressed those 3 buttons and the instalation started successfully.
I just cant explain how happy i was. I stayed 3 days without it.
After that I have been messing with fastboot so thanks to everyone who made me realize that i didnt need to do all of this, but well, A full wipe is always welcome.
Is there any custom kernel on the way for overclock my baby?
Click to expand...
Click to collapse
I also have same problem. Now i am going to try this. thank you very much.
---------- Post added at 02:22 PM ---------- Previous post was at 01:53 PM ----------
siul_lasc said:
Hi everyone!!
First of all, thanks to everybody who helped me with this situation.
I now am using my baby again as if it was new. I wiped him completely as i stated before and it was as easy as finding the right firmware (136a) and using the vol down + vol up + power button technique. I put the UPDATE.APP file inside a folder named dload in sdcard using other phone (with my p8 was impossible). After that rebooted the device, pressed those 3 buttons and the instalation started successfully.
I just cant explain how happy i was. I stayed 3 days without it.
After that I have been messing with fastboot so thanks to everyone who made me realize that i didnt need to do all of this, but well, A full wipe is always welcome.
Is there any custom kernel on the way for overclock my baby?
Click to expand...
Click to collapse
Yeah finally my phone is working now thanks to you I searched many treads and forums but i cant find a solution. But finally i got an easy solution Thank you again bro.. Good Luck !!!:good::good::good::good::good::good::good:
Just download your firmware version, use huawei extractor to extract boot.img,cust.img,recovery.img and system.img
After that,download mininal adb fastboot copy you files into fastboot folder , enter fastboot mode on your phone and from fastboot folder,open cmd and type these commands:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
After this your phone will boot normally. Once you've done this, copy update.app to your sdcard or internal and install it by local update. Once you've done all this,your phone is fine.
May I know how do you wipe your internal storage? and what if after wiping, im unable to get into recovery mode? does it mean phone is not usable anymore?
SOLUTION
Hello. I'm the bigest mess on androids but i know that flashing stock recovery can remove any TWRP/CWR. If its too powerfull flash stock boot and run fastboot -w.(fastboot -w erases all PERSONAL data)
Guys Help me in this
guys help me
http://forum.xda-developers.com/honor-7/help/stock-emui-recovery-image-lost-twrp-t3442021
thank you !!
VladHD said:
Just download your firmware version, use huawei extractor to extract boot.img,cust.img,recovery.img and system.img
After that,download mininal adb fastboot copy you files into fastboot folder , enter fastboot mode on your phone and from fastboot folder,open cmd and type these commands:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
After this your phone will boot normally. Once you've done this, copy update.app to your sdcard or internal and install it by local update. Once you've done all this,your phone is fine.
Click to expand...
Click to collapse
After days of searching the internet i couldnt find any working solution. then i tried the local update without flashing al those .img's. ( didnt work )
Now after flashing al those .img's my phone works again but its a whole different phone. Only problem is when i try to update him with the update.app file it won't go any further then 5%.
If you know why this happens let me know
Further i wanna thank you one last time .. thank you
Hey XDA, Recently installed Paranoid Android coming from Chroma and it's not stuck in a boot loop. I can boot just fine every time besides the annoying corruption google warning, but no matter how many times I try to install TWRP it just won't let me boot into recovery. I'm using WugFresh's NRT kit. Can't seem to figure it out. Any suggestions?
carterl96 said:
Hey XDA, Recently installed Paranoid Android coming from Chroma and it's not stuck in a boot loop. I can boot just fine every time besides the annoying corruption google warning, but no matter how many times I try to install TWRP it just won't let me boot into recovery. I'm using WugFresh's NRT kit. Can't seem to figure it out. Any suggestions?
Click to expand...
Click to collapse
My suggestion is for you to fastboot flash the TWRP recovery image instead of using a toolkit. You cant see the inner workings of a toolkit and have no idea of what it is doing. The toolkit could be using the wrong commands to install a recovery image to your 6P. Go to www.twrp.me and search for the recovery image for your specific device and download the file. Next, rename the file to recovery.img Then, on your PC, navigate to the folder where you downloaded the TWRP image. Open a command prompt in that folder by pressing and holding the SHIFT KEY + RIGHT CLICK on your mouse and select OPEN A COMMAND WINDOW HERE. Boot to the bootloader on your device and connect it to your PC. Then type this:
fastboot flash recovery recovery.img
Then type this:
fastboot reboot bootloader
fastboot reboot recovery
Here is the link to download TWRP for your Nexus 6P
This will reboot your device to TWRP
All of this is based on the assumption that you have a working ADB installation and unlocked the bootloader and have USB Debugging turned on in DEVELOPER OPTIONS.
Sent from my Nexus 6 using XDA-Developers mobile app
Same thing, successful install and it won't open. Just shows the dead android when going to recovery.
carterl96 said:
Same thing, successful install and it won't open. Just shows the dead android when going to recovery.
Click to expand...
Click to collapse
You get the same results after fastboot flashing the TWRP image? I'd say your next step is to start fresh by fastboot flashing the factory images to return to a fully stock state. Then fastboot flash TWRP again.
Sent from my Nexus 6 using XDA-Developers mobile app
Do not boot directly into system after flashing the custom recovery.
After flashing boot into TWRP. I remember on previous devices that I owned that if you do not boot into the custom recovery after flashing it, you revert to the factory recovery.
Just a thought
tech_head said:
Do not boot directly into system after flashing the custom recovery.
After flashing boot into TWRP. I remember on previous devices that I owned that if you do not boot into the custom recovery after flashing it, you revert to the factory recovery.
Just a thought
Click to expand...
Click to collapse
I thought about that too. What is probably happening is his custom recovery is being patched by the ROM each time he boots into recovery. Thanks for picking up on that. I forgot to include that in my last post.
Sent from my Nexus 6 using XDA-Developers mobile app
tech_head said:
Do not boot directly into system after flashing the custom recovery.
After flashing boot into TWRP. I remember on previous devices that I owned that if you do not boot into the custom recovery after flashing it, you revert to the factory recovery.
Just a thought
Click to expand...
Click to collapse
That's correct. After flashing TWRP the next step is reboot into the bootloader using the volume keys and power key , then from there boot into recovery using the volume keys and power key, then the phone can be rebooted from TWRP into Android and then after that TWRP should stick.
If the boot image is not patched, the ROM will overwrite TWRP once you reboot. flashing latest SU from TWRP will prevent this.
Thanks for all the replies guys! All the advice combined got it to work. I did some more research and found that Paranoid doesn't actually come preprooted like all the other roms I've been used to. So using the tool kit I just had it root it with the latest SuperSu and also flash a custom recovery. It has booted into TWRP no problems now a few times. Hopefully it will stay like this. Will keep everyone posted and appreciate the advice. Thanks XDA!