Develop Bugs

AOSP 2.99 beta5 (five) Reboot loop! bricked

The problem I encountered must be the worst problem ever! For some reason my nexus reboot randomly and its not just a regular reboot but it reboot as a DEEP FREEZE. So basically once it rebooted, it goes back to a same specific point of time. I can't even delete stuff from the phone, for example if I deleted 1GB of music off my phone, after few second the phone will reboot automatically OR if i reboot the phone myself the 1GB of music would be back in my phone. Like WTH? I am completely lost. I have no idea how it happened, but I know it happened after I installed Paranoid Android AOSP 2.99 beta5. I was fine when flashing Paranoid Android 1,3,4. ALSO I cannot do a factory reset or install a factory rom. It just go back to 4.2.1 AOSP 2.99 beta5...
please guys, if anyone can help me that would be great. If you guys need more explaining please email or PM me. I will be glad to write a whole essay on what you guys need to know to help me out. Thank you

Go back to stock and start fresh.
Sent from my i9250

bk201doesntexist said:
Go back to stock and start fresh.
Sent from my i9250
Click to expand...
Click to collapse
That didn't work either. I tried going back to stock but it didn't do anything, I keep booting into 2.99 beta5. I was able to get into recovery mode but I think that when it load the "Google" boot up screen, that's when it start the deep freeze process. Do you get what I mean though? I can post a video to show you guys what I mean. So like if I wanted to flash another ROM I have to go into recovery, but before getting to recovery, you have to go through the "Google" loading screen correct? Then when I get into recovery to flash, the ROM is not there..

Yellowfriedrice said:
Then when I get into recovery to flash, the ROM is not there..
Click to expand...
Click to collapse
Which "ROM" is not there? Do you have any flashable zip of any ROM on your internal sdcard to flash?
I think you should go ahead and post a video so it will be much easier to understand what is going on exactly then hopefully we can help you here

ahmadallica said:
Which "ROM" is not there? Do you have any flashable zip of any ROM on your internal sdcard to flash?
I think you should go ahead and post a video so it will be much easier to understand what is going on exactly then hopefully we can help you here
Click to expand...
Click to collapse
You cant brick a nexus! Try making a jig with this link http://www.youtube.com/watch?v=jKRrTZayRxU Then get download odin and an img file of whatever rom you want and flash it through odin. Problem should be solved.

Yellowfriedrice said:
That didn't work either. I tried going back to stock but it didn't do anything, I keep booting into 2.99 beta5. I was able to get into recovery mode but I think that when it load the "Google" boot up screen, that's when it start the deep freeze process. Do you get what I mean though? I can post a video to show you guys what I mean. So like if I wanted to flash another ROM I have to go into recovery, but before getting to recovery, you have to go through the "Google" loading screen correct? Then when I get into recovery to flash, the ROM is not there..
Click to expand...
Click to collapse
man what i think is you should download nexus toolkit , i think its latest edition is 10. something and try to reflash your stock image and recovery . just try that.
---------- Post added at 08:48 PM ---------- Previous post was at 08:27 PM ----------
did something work out

khuzema9 said:
man what i think is you should download nexus toolkit , i think its latest edition is 10. something and try to reflash your stock image and recovery . just try that.
---------- Post added at 08:48 PM ---------- Previous post was at 08:27 PM ----------
did something work out
Click to expand...
Click to collapse
Based on the language used in the OP I think he used a toolkit to root/unlock his Nexus and that's why he knows nothing about his device and how to fix it.
OP- look up fastboot images nexus and follow what you read. Basicly you should download the fastboot images and flash them all in fastboot. Then start from scratch again

altimax98 said:
OP- look up fastboot images nexus and follow what you read. Basicly you should download the fastboot images and flash them all in fastboot. Then start from scratch again
Click to expand...
Click to collapse
That's right and probably the cleanest way of going out of this mess. Here is a thread that can help you accomplish that:
http://forum.xda-developers.com/showthread.php?t=1626895
Read the instructions carefully because this will delete all your data including the internal (and only) sdcard of your GNex, so consider the backup part of that thread very well.
Good Luck

still didn't work
ahmadallica said:
That's right and probably the cleanest way of going out of this mess. Here is a thread that can help you accomplish that:
http://forum.xda-developers.com/showthread.php?t=1626895
Read the instructions carefully because this will delete all your data including the internal (and only) sdcard of your GNex, so consider the backup part of that thread very well.
Good Luck
Click to expand...
Click to collapse
I couldn't use the driver from the thread you sent, it says "access denied" and I tried to disable windows signature verification but that didn't work either. So I thought maybe I'll use the driver from Nexus toolkit. I manage to complete all the steps from the instruction to the core except for the driver but it still didn't work. It would not erase the 2.99 beta5 and so I cannot go back to stock. Perhaps I should try to use the driver from the thread but I just don't know how to get pass the signature verification when installing the driver. Assist me if you can please. Thank you

Yellowfriedrice said:
I couldn't use the driver from the thread you sent, it says "access denied" and I tried to disable windows signature verification but that didn't work either. So I thought maybe I'll use the driver from Nexus toolkit. I manage to complete all the steps from the instruction to the core except for the driver but it still didn't work. It would not erase the 2.99 beta5 and so I cannot go back to stock. Perhaps I should try to use the driver from the thread but I just don't know how to get pass the signature verification when installing the driver. Assist me if you can please. Thank you
Click to expand...
Click to collapse
I really have not done anything to my GNex via Windows becuse I am using Ubuntu Linux so I have not experienced installing these drivers on Windows. I also have neither returned my phone to stock before nor used the Nexus toolkit. I am doing everything manually.
I think you are referring to the drivers in this page. If you are using Windows 8 then there are some steps mentioned on how to get pass the driver signature enforcement.
If you are on Windows 7, then look here.
Just to confirm something else because I did not read that you have done it, did you try wiping system, factory reset, cache and dalvik cache from the recovery then install any other flashable zip of a ROM on your sdcard (if you have) and still nothing is erased and you are stuck on the same ROM?

ahmadallica said:
Just to confirm something else because I did not read that you have done it, did you try wiping system, factory reset, cache and dalvik cache from the recovery then install any other flashable zip of a ROM on your sdcard (if you have) and still nothing is erased and you are stuck on the same ROM?
Click to expand...
Click to collapse
Yes, I have but that didn't seem to work either. I put a flashable ROM into the internal memory when it was rebooted, when I tried to go into recovery the file is not there anymore. Its because the phone erases everything that was placed into the internal during the Google reboot process. I even tried using the nexus toolkit to flash a stock ROM, the procedure went through successfully but it still loads 2.99 beta5.
I will try to post a video as soon as I buy a webcam.. But a webcam is cheaper than a nexus phone right now so I don't mind. lol

Yellowfriedrice said:
Yes, I have but that didn't seem to work either. I put a flashable ROM into the internal memory when it was rebooted, when I tried to go into recovery the file is not there anymore. Its because the phone erases everything that was placed into the internal during the Google reboot process. I even tried using the nexus toolkit to flash a stock ROM, the procedure went through successfully but it still loads 2.99 beta5.
I will try to post a video as soon as I buy a webcam.. But a webcam is cheaper than a nexus phone right now so I don't mind. lol
Click to expand...
Click to collapse
You may try to boot into recovery then use "adb push" to send the file to your sdcard from your computer. If the file is sent successfully, then you can find it in the recovery and install it thus escape the reboot problem.
Hope this works!

ahmadallica said:
You may try to boot into recovery then use "adb push" to send the file to your sdcard from your computer. If the file is sent successfully, then you can find it in the recovery and install it thus escape the reboot problem.
Hope this works!
Click to expand...
Click to collapse
still no good.. used the recovery sideload to push but it still didn't work.
tried odin but that didn't work either.

Yellowfriedrice said:
still no good.. used the recovery sideload to push but it still didn't work.
tried odin but that didn't work either.
Click to expand...
Click to collapse
Was there any progress of pushing the file then it did not appear in your recovery or it did not show any progress at all of being pushed?
I have experienced this and used to push the file two times (one after another while still in recovery mode) in order to successfully find the file in recovery. Give it a try and good luck

ahmadallica said:
Was there any progress of pushing the file then it did not appear in your recovery or it did not show any progress at all of being pushed?
I have experienced this and used to push the file two times (one after another while still in recovery mode) in order to successfully find the file in recovery. Give it a try and good luck
Click to expand...
Click to collapse
I pushed it before and while it was in recovery mode. Tried both ways but I didnt see any file in there.
I also just noticed that all the files within the folders are missing. The folders are there but when I go into any folders, it said no files found within the folders.

ahmadallica said:
I have experienced this and used to push the file two times (one after another while still in recovery mode) in order to successfully find the file in recovery. Give it a try and good luck
Click to expand...
Click to collapse
Thank Goodness im not the only one who has this issue... Bugs the crap outta me lol..
To the OP:
Try this, 1: make sure your an admin on your PC. From the sounds of it you may not be if it said 'access denied'. 2: Plug your nexus in while in the 'device manager' section of windows. 3: Find the new device and delete it. Delete anything that says Android ADB or Android anything or galaxy Nexus or Galaxy phone. Just delete them. Windows will warn you but do it anyways... 4: reboot the pc. 5: Plug your nexus back in, it should either install the device or fail. At that point find and download the newest samsung naked drivers and use the option on windows to install driver from disk and navigate to your unzipped folder.
That is the sure fire way to get it working again. Sorry to say if you still have driver issues then your doing something wrong. Do alot of reading and the answer will show itself.

1. Can you boot your phone into fastboot mode?
2. If so, once in fastboot mode, what happens when you connect the phone to the computer?
It is very very difficult to brick a nexus, so don't worry... .

Yellowfriedrice said:
I pushed it before and while it was in recovery mode. Tried both ways but I didnt see any file in there.
I also just noticed that all the files within the folders are missing. The folders are there but when I go into any folders, it said no files found within the folders.
Click to expand...
Click to collapse
Sorry for not being able to help you better. I'm sure that others who are familiar with Windows can help you overcome your earlier issues with drivers and so on thus be able to return to stock and start fresh
Good Luck

It is very very difficult to brick a nexus said:
challenge accepted!!
But yes I can get it into fastboot mode. Nothing special happen? What are you trying to look for to happen? It look like it functioning normally in fastboot mode.
Click to expand...
Click to collapse

OKAY i tried everything.. nothing seem to work.. selling my nexus!
Yellowfriedrice said:
challenge accepted!!
But yes I can get it into fastboot mode. Nothing special happen? What are you trying to look for to happen? It look like it functioning normally in fastboot mode.
Click to expand...
Click to collapse

[Q] Need help on how to fix soft brick on GoogleLogo

I was on my merry way to flash a new rom and kernel but I was being careless and also formatted my sdcard and now I have nothing in the card to flash any type of file. Can anyone point me to a directory with a rooted/unrooted odin flashable JB for the Verizon Samsung Galaxy Nexus?
Is that the only way I can make my phone work? See the I can turn it on and put it into Recovery but it won't go anywhere else other than that... yeah i should have made a back-up but I never do and i never realized i would make a careless mistake. Please help as I now have no phone to use!
Thanks!!

Stickied posts made by efrant. XDA search bar if you need help after. Many people have gotten through this..you can too
Bloods thicker than water

mrxtokki said:
I was on my merry way to flash a new rom and kernel but I was being careless and also formatted my sdcard and now I have nothing in the card to flash any type of file. Can anyone point me to a directory with a rooted/unrooted odin flashable JB for the Verizon Samsung Galaxy Nexus?
Is that the only way I can make my phone work? See the I can turn it on and put it into Recovery but it won't go anywhere else other than that... yeah i should have made a back-up but I never do and i never realized i would make a careless mistake. Please help as I now have no phone to use!
Thanks!!
Click to expand...
Click to collapse
Don't use ODIN unless you have to. You seem to have a custom recovery, this usually offers the ADB interface. So, boot into recovery, use adb to push a ROM of your choice to the /sdcard/ and flash away.

namtombout said:
Stickied posts made by efrant. XDA search bar if you need help after. Many people have gotten through this..you can too
Bloods thicker than water
Click to expand...
Click to collapse
I found couple posts that efrant has created but i can't figure out what to do.
currently, my phone is unlocked and rooted. i have CWM but how do i flash anything to my phone when i can't even run it?
i'm just very confused as I always had a phone with an external sdcard and if i was able to just put a rom inside of that... i would be able to use my phone again but I don't have the option.
i'm stuck with a phone with no rom and can't even send anything to the phone

Petrovski80 said:
Don't use ODIN unless you have to. You seem to have a custom recovery, this usually offers the ADB interface. So, boot into recovery, use adb to push a ROM of your choice to the /sdcard/ and flash away.
Click to expand...
Click to collapse
with the custom recovery, ie, the CWM v6 , i went to the sideload option and it says... "now send the package you want to apply to the device with "adb sideload <filename>"
how do i push a rom into the phone? i'm a noob at this so i'm sorry.

mrxtokki said:
with the custom recovery, ie, the CWM v6 , i went to the sideload option and it says... "now send the package you want to apply to the device with "adb sideload <filename>"
how do i push a rom into the phone? i'm a noob at this so i'm sorry.
Click to expand...
Click to collapse
You need to read Efrant's 101 & FAQ post first in order to get some basic Android knowledge. Follow the link in my sig.

Petrovski80 said:
You need to read Efrant's 101 & FAQ post first in order to get some basic Android knowledge. Follow the link in my sig.
Click to expand...
Click to collapse
I have read it but, I still have no idea what I need to be doing.
I really just need a step by step on how to use the sideloader to send the roms through the CWM recovery
All of this is really confusing

mrxtokki said:
I have read it but, I still have no idea what I need to be doing.
I really just need a step by step on how to use the sideloader to send the roms through the CWM recovery
All of this is really confusing
Click to expand...
Click to collapse
Don't use sideloading. You want to use adb push to send a ROM.zip to your /sdcard/. You already have a custom recovery, so you just need
- adb on your PC
- a ROM.zip to push
How to use adb and how to get it, is explained in Efrant's 101 & FAQ.

[Q] URGENT: Flashed Wrong Kernel To My Nexus 7 (flo)!

Hi guys. I recently flashed the Glitched Kernel (http://forum.xda-developers.com/showthread.php?t=2449919) to my Nexus, but I accidently downloaded the wrong one. Not knowing this, I flashed it via TWRP and now my device crashes completely (my computer won't even recognize it) on the lock screen. I can still boot into the bootloader, TWRP, and MultiROM easily. I just can't boot up Cyanogenmod (Only rom I have on the device as of now). I really don't know what to do. I've tried connecting via USB in the bootloader, my computer won't even pick up the device. I've also tried adb sideload a new rom and a new kernel, but I get the error 'protocol fault (no status)' which is weird, because ADB recognizes my device (I typed the 'adb devices' command in CMD) How can I flash the stock kernel back onto it?
Thanks in advance,
~NascarBoy119

Just clean flash cyanogenmod again if you have the Rom as .zip on your device. If not use ADB to get a Rom for flashing on your device.

Restore your backup (nandroid).

detoxN said:
Just clean flash cyanogenmod again if you have the Rom as .zip on your device. If not use ADB to get a Rom for flashing on your device.
Click to expand...
Click to collapse
I can't download anything to my device. ADB sideload won't work also (I get the error 'protocol fault [no status]), as I stated above.
Also @wantabe
Shortly before this I ran Clean Master on my device. Turned out it deleted my backups... After that, all this drama happened. Probably kinda my fault as I used the TWRP backup feature instead of NanDriod.

NascarBoy119 said:
I can't download anything to my device. ADB sideload won't work also (I get the error 'protocol fault [no status]), as I stated above.
Also @wantabe
Shortly before this I ran Clean Master on my device. Turned out it deleted my backups... After that, all this drama happened. Probably kinda my fault as I used the TWRP backup feature instead of NanDriod.
Click to expand...
Click to collapse
adb is your friend. There is plenty of opportunities. You could download a ROM on your computer and sideload or push it in adb. You could also download stock images and fastboot it in the bootloader. Simple...
Sent from my Nexus 7 using Tapatalk

NascarBoy119;49329133]I can't download anything to my device. ADB sideload won't work also (I get the error 'protocol fault [no status]).
Click to expand...
Click to collapse
nikr123 said:
adb is your friend. There is plenty of opportunities. You could download a ROM on your computer and sideload or push it in adb. You could also download stock images and fastboot it in the bootloader. Simple...
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
As you see the text that I put in bold, ADB sideload/pushing gives me an error. I might try the fastboot thing though but then I'll lose all my data, right?

NascarBoy119 said:
As you see the text what I put in bold, ADB sideload/pushing gives me an error. I might try the fastboot thing though but then I'll lose all my data, right?
Click to expand...
Click to collapse
what android version are your running?
anyways grab the gltiched kernel for your device this time.
then put your device i to recovery: up/down volume plus power when device is off
once in recovery type thus from your computer.
fastboot flash boot boot.img
you will need to extract the image from the glitched-kernel.zip
no this will not wipe your data. it is the manual way of flashing a kernel.
hope that helps.

NascarBoy119 said:
As you see the text what I put in bold, ADB sideload/pushing gives me an error. I might try the fastboot thing though but then I'll lose all my data, right?
Click to expand...
Click to collapse
Fastboot is your friend in this case, as long as you didn't relock your bootloader you can flash without losing your data.
userdelroot said:
no this will not wipe your data. it is the manual way of flashing a kernel.
hope that helps.
Click to expand...
Click to collapse
^this
Not using cleanmaster to delete your backups was a lesson you learned the hard way, but it is not unrecoverable and you can chalk it up as a learning experience.
Let us know how it worked out, everything will be fine as long as you take your time and relax. This is something that happens to most people sooner or later and is a great confidence builder (once you work through it).

To avoid this I keep all my backups, zips and other flashaholic stuff on a USB drive mounted using an USB OTG cable. You can mount it and use it in recovery.

megabatteryman said:
To avoid this I keep all my backups, zips and other flashaholic stuff on a USB drive mounted using an USB OTG cable. You can mount it and use it in recovery.
Click to expand...
Click to collapse
This may very well be the top reason to buy an OTG cable and/or OTG Micro SD reader / hub device
Sent from my Nexus 7 using XDA Premium HD app

userdelroot said:
what android version are your running?
anyways grab the gltiched kernel for your device this time.
then put your device i to recovery: up/down volume plus power when device is off
once in recovery type thus from your computer.
fastboot flash boot boot.img
you will need to extract the image from the glitched-kernel.zip
no this will not wipe your data. it is the manual way of flashing a kernel.
hope that helps.
Click to expand...
Click to collapse
oldsoldier2003 said:
Fastboot is your friend in this case, as long as you didn't relock your bootloader you can flash without losing your data.
Not using cleanmaster to delete your backups was a lesson you learned the hard way, but it is not unrecoverable and you can chalk it up as a learning experience.
Let us know how it worked out, everything will be fine as long as you take your time and relax. This is something that happens to most people sooner or later and is a great confidence builder (once you work through it).
Click to expand...
Click to collapse
I did what you guys said and it work flawlessly. Thank you so much! I was worried I permanently bricked my device. I though about buying an OTG cable, but now I think I'm buying it for sure. I'll try to store some backups on it too.

Awesome, glad we could help

[Q] Need help ASAP! CWM problem.

Hey guys, this is my first post on XDA forum.
So I've recently bought a nexus 7, I used wugfresh's root kit to root my nexus but then it didn't work... so I've tired the auto root by chainfire. Then I was able to get root. So then I went to playstore and downloaded rom manager to install CWM. I went to recovery then I get this message:
E : Cant mount /cache/recovery/log etc.....
I've tried everything I can do such as researching, changing recovery, and watching a youtube tutorial but nothing helped.
Thanks.

I would start over from scratch using fastboot to flash a factory image and stock recovery. If your bootloader isn't unlocked already, unlock it.

nhizzat said:
I would start over from scratch using fastboot to flash a factory image and stock recovery. If your bootloader isn't unlocked already, unlock it.
Click to expand...
Click to collapse
I tried to format using wugfresh couple times but still not working...

DO NOT USE TOOLKITS. They cause too many problems. Learn to do things the proper way using fastboot. I agree with the poster above, you should flash a factory image to start over. Download the system image from here- https://developers.google.com/android/nexus/images
You need to unlock your bootloader-
Code:
fastboot OEM unlock
Then run the flash_all.bat. That will automatically wipe and reflash everything to get you back to square one.
Then you need to flash TWRP (don't use CWM)
Code:
fastboot flash recovery recoveryname.img
TWRP will automatically prompt you to flash SU when you reboot. Choose yes, reboot, then install SuperSU from play store, update the SU binaries, reboot again, and then you're done.

_MetalHead_ said:
DO NOT USE TOOLKITS. They cause too many problems. Learn to do things the proper way using fastboot. I agree with the poster above, you should flash a factory image to start over. Download the system image from here- Link Removed
You need to unlock your bootloader-
Code:
fastboot OEM unlock
Then run the flash_all.bat. That will automatically wipe and reflash everything to get you back to square one.
Then you need to flash TWRP (don't use CWM)
Code:
fastboot flash recovery recoveryname.img
TWRP will automatically prompt you to flash SU when you reboot. Choose yes, reboot, then install SuperSU from play store, update the SU binaries, reboot again, and then you're done.
Click to expand...
Click to collapse
I tried to flash TWRP but its still the same error code

z3r0c311 said:
I tried to flash TWRP but its still the same error code
Click to expand...
Click to collapse
I highly advise you start from scratch so do what I told you to do in my last post. I promise if you do it the correct way (ie. without using toolkits) it will work.

_MetalHead_ said:
I highly advise you start from scratch so do what I told you to do in my last post. I promise if you do it the correct way (ie. without using toolkits) it will work.
Click to expand...
Click to collapse
It would be great if u could tell me the commands, im nubby with this fastboot thing.

z3r0c311 said:
It would be great if u could tell me the commands, im nubby with this fastboot thing.
Click to expand...
Click to collapse
I gave you the commands in my first post in this thread.
Here's a guide to get you started-
http://forum.xda-developers.com/showthread.php?t=2277112

Sorry for another nubby question but how do I get flash_all.bat?

z3r0c311 said:
Sorry for another nubby question but how do I get flash_all.bat?
Click to expand...
Click to collapse
It's in the file that you should have downloaded from the link I posted in my first post. The instructions are at that link as well.

_MetalHead_ said:
It's in the file that you should have downloaded from the link I posted in my first post. The instructions are at that link as well.
Click to expand...
Click to collapse
Hey I tried the following:
oem lock
oem unlock
flash-all/flash_all.bat
flash recovery(TWRP)
but then when I reboot into TWRP I don't get a message saying you to install SU... And when I go to 'Install' in TWRP I don't see any internal storage available(0mb). With this error I cant install any roms which is boring.

z3r0c311 said:
Hey I tried the following:
oem lock
oem unlock
flash-all/flash_all.bat
flash recovery(TWRP)
but then when I reboot into TWRP I don't get a message saying you to install SU... And when I go to 'Install' in TWRP I don't see any internal storage available(0mb). With this error I cant install any roms which is boring.
Click to expand...
Click to collapse
Hmm... Can you even boot into the stock ROM at this point? Try formatting /data (done in TWRP). Did the system image flash successfully?

_MetalHead_ said:
Hmm... Can you even boot into the stock ROM at this point? Try formatting /data (done in TWRP). Did the system image flash successfully?
Click to expand...
Click to collapse
I can boot into my stock rom which is 5.0.2, when I try to format /data the error codes comes out...

z3r0c311 said:
I can boot into my stock rom which is 5.0.2, when I try to format /data the error codes comes out...
Click to expand...
Click to collapse
Did the system image flash successfully?

_MetalHead_ said:
Did the system image flash successfully?
Click to expand...
Click to collapse
using flash-all command, yeah

z3r0c311 said:
using flash-all command, yeah
Click to expand...
Click to collapse
Well then I don't know what to tell you at this point. I know Lollipop has been causing issues for some N7 users, but I also know that wugs toolkit causes problems too so honestly I'm not sure what the root of your issue is. I think someone with more experience with Lollipop is gonna have to chime in here, I'm still on 4.4.4 on all of my devices. Sorry I couldn't be of more help.

_MetalHead_ said:
Well then I don't know what to tell you at this point. I know Lollipop has been causing issues for some N7 users, but I also know that wugs toolkit causes problems too so honestly I'm not sure what the root of your issue is. I think someone with more experience with Lollipop is gonna have to chime in here, I'm still on 4.4.4 on all of my devices. Sorry I couldn't be of more help.
Click to expand...
Click to collapse
Thanks for helping me I appreciate it. I hope someone else can help me with this problem... btw can I flash roms with the stock recovery? The stock recovery seems to be working fine...

z3r0c311 said:
Thanks for helping me I appreciate it. I hope someone else can help me with this problem... btw can I flash roms with the stock recovery? The stock recovery seems to be working fine...
Click to expand...
Click to collapse
No, you can only flash custom ROMs if you have a custom recovery.

I installed 7.1.1 by mistake. What now? Help

I bought my 5X in October and came here to root my phone and be able to use the ElementalX and the Advanced Interactive Governor tweaks.
Everything was working fine and my phone really performed outstandingly.
Then I saw the OTA 7.1.1. popping up. I didn't allow it until I installed it by mistake yesterday...
Now I'm stuck with google asking me to lock the bootloader.
I can access the bootloader. I get a lot of options.
I can access the recovery mode and it gets me to RecoveryProject 3.0.2-2 by Teamwin.
I already have the Android platform tools on my desktop and it's working.
From there I have 2 questions :
1. Is there a way to not wipe all the contents on my phone? I didn't get the chance to backup all the data on it.
2. After that how can I get my phone working with the latest android version as I was before, unrooted and running with EX Kernel Manager.
Thanks for your help.

1. try installing the supersu zip from the recovery
2.EX Kernel Manager cannot work without root. so you need to root your device

Thanks a lot for you answer!
1. So by installing SuperSu zip from the recovery I would be able to backup my phone data?
2. I meant rooted sorry. So my phone is already rooted and I'm fine with staying that way.

Enzoli said:
Thanks a lot for you answer!
1. So by installing SuperSu zip from the recovery I would be able to backup my phone data?
Click to expand...
Click to collapse
yes
you can actually backup you device from TWRP recovery.
flash the supersu zip and you will boot normally without any data lose

Insane! thanks a lot.
One more noob question. I got the latest superSu zip.
How can I flash it from the recovery?
How can i transfer it to the phone?

Ok I almost got it.
My only question left is how can I transfer the SuperSu zip file onto my phone since I don't have access to anything else than Bootloader and TWRP

Enzoli said:
Ok I almost got it.
My only question left is how can I transfer the SuperSu zip file onto my phone since I don't have access to anything else than Bootloader and TWRP
Click to expand...
Click to collapse
adb sideload from twrp

OK guys thanks. When I use adb sideload in twrp advanced menu it gets stuck on "Starting ADB sideload feature... "
And when I type ADB devices on the command prompt it does not show my device but if I'm just in the menu before sideload it does find my device and says the serial number + recovery.
What am I doing wrong?
Thanks for helping.

You should be able to transfer files while being in recovery using MTP mode.

How do I use MTP mode? Sorry what does that mean. Can't find an explanation on the internet.
I've looked at all the options in the menu but can't find such a option.
I really feel stupid.

Ok guys I transfered SuperSu to my phone using adb push.
I flashed my phone with SuperSu but when i reboot my phone, it still tells me I need to lock my bootloader.
What shall I do now?

I keep going to the Googl screen with the little locker and then I reach the No Command screen.
The phone won't boot into Android no more. Guys please help I'm desperate. Is my phone dead?

Ok so I guess my phone is now in bootloop.
Still anyone willing to help?

OK I tried many things in despair and now I cannot enter the recovery mode anymore. It just gets stuck on the teamwin screen.
Guess it's time to buy a new phone.

So miracle I could enter the recovery.
Now I don't know where to go. I would like to be able to enter normal android but my phone will keep on showing android screen with little lock and the end on the No command screen. Endlessly.

Ok. THread can be closed. I managed to flash a factory image. Lost all my data but I got a working phone so I guess it's not to bad.

...

Enzoli said:
Ok. THread can be closed. I managed to flash a factory image. Lost all my data but I got a working phone so I guess it's not to bad.
Click to expand...
Click to collapse
If you ever need help on updating your software to the latest Android version, follow my guide as a reference:
https://forum.xda-developers.com/showthread.php?t=3206930
Sent from my Nexus 5X using Tapatalk