Develop Bugs

Cant enter recovery

my phone will not boot into recovery mode through CWM or by powering off and manually starting it. I get a dead android with a red triangle and ! sign, how can i fix this?
galaxy nexus (verizon)
4.0.2
rooted via Gnex tool kit

That is the stock recovery. You need to permanently flash CWM (a.k.a. a custom recovery) for you to get into it.

anton2009 said:
That is the stock recovery. You need to permanently flash CWM (a.k.a. a custom recovery) for you to get into it.
Click to expand...
Click to collapse
If you are rooted, you need to check the CWM thread for the file to delete through root explorer and then re-flash CWM to get it to stick.

Or use rom manager to flash it.

Jubakuba said:
Or use rom manager to flash it.
Click to expand...
Click to collapse
Ah yea, good point.
I prefer the difficult and manual way lol

Or re-flash your recovery from fastboot, then boot into it, and install whatever ROM you wanted.

OR don't flash cwm at all, just 'fastboot boot cwm.img', allow it a few seconds to enter cwm, then do your thing, flash your rom/much needed zips, reboot and you're good to go.
this world is all about choice ain't it?

bk201doesntexist said:
OR don't flash cwm at all, just 'fastboot boot cwm.img', allow it a few seconds to enter cwm, then do your thing, flash your rom/much needed zips, reboot and you're good to go.
this world is all about choice ain't it?
Click to expand...
Click to collapse
I agree. This option will let you boot into cwm once. when you finish there and reboot your nexus will wipe every trace of cwm. When you need it again just use the same trick again.
Sent from my Galaxy Nexus using XDA

anton2009 said:
That is the stock recovery. You need to permanently flash CWM (a.k.a. a custom recovery) for you to get into it.
Click to expand...
Click to collapse
Before anybody suggests I use search - I DID search, and it brought me to this thread.
Background: After unboxing my shiny new GNex last week, I immediately flashed stock yakju IMM76D using GNex Tookit.
So ... let me make sure I understand this. With stock recovery, when I fire up fastboot and select recovery, it is NORMAL to get the little dead robot with a red triangle above him? And the only way I've found to get out of it is to pull the battery? Seems odd.....
(I did temporarily flash CWM via the Toolkit and it worked fine. I don't want to leave it on as I understand it will prevent me from getting future OTA updates.)

As long as you run stock ICS, you'll always get that error upon every boot, even if you rename/delete the "boot-from-recovery.p" or whatever. The only solution is to flash a custom ROM and that error will be permanently gone.
At least what I've read and heard and what it's like for me.
If you get that error, your phone will reboot after a minute or so, but like I said it should be gone after flashing a custom ROM.

Theshawty said:
As long as you run stock ICS, you'll always get that error upon every boot, even if you rename/delete the "boot-from-recovery.p" or whatever. The only solution is to flash a custom ROM and that error will be permanently gone.
At least what I've read and heard and what it's like for me.
Click to expand...
Click to collapse
no.
you delete the file, then flash CWM.
it is not a error. that is the stock recovery and if you press vol up and vol down (might have to press power too) it should get you a menu.

Zepius said:
no.
you delete the file, then flash CWM.
it is not a error. that is the stock recovery and if you press vol up and vol down (might have to press power too) it should get you a menu.
Click to expand...
Click to collapse
I renamed it, it should be the same as doing away with it. However, upon rebooting, I faced that triangle. I ran stock 4.0.4 by the time.

you still have to reflash CWM after deleting/renaming the file.

Zepius said:
you still have to reflash CWM after deleting/renaming the file.
Click to expand...
Click to collapse
Which I did, but the problem wouldn't wanna go away.

Theshawty said:
Which I did, but the problem wouldn't wanna go away.
Click to expand...
Click to collapse
Step-by-step:
1) Delete /system/recovery-from-boot.p (need root of course).
2) Delete /system/etc/install-recovery.sh (need root of course).
3) Check to make sure that the above files no longer exist.
4) Flash CWM AFTER making sure the above files are not present on your system.
5) Reboot.

efrant said:
Step-by-step:
1) Delete /system/recovery-from-boot.p (need root of course).
2) Delete /system/etc/install-recovery.sh (need root of course).
3) Check to make sure that the above files no longer exist.
4) Flash CWM AFTER making sure the above files are not present on your system.
5) Reboot.
Click to expand...
Click to collapse
Thanks, but no thanks. I run a a custom ROM now so the issue doesn't seem to be there anymore.
I haven't read about the install script but ill be sure to follow your guide when and if I ever return to stock. They're awesome.
Sent from my Galaxy Nexus using Tapatalk 2

Theshawty said:
Thanks, but no thanks. I run a a custom ROM now so the issue doesn't seem to be there anymore.
Click to expand...
Click to collapse
Just for additional info, those files are not present on any original stock ROMs. They are added to a stock ROM if that stock ROM is updated, i.e., OTA update. They serve no purpose but to re-flash the stock recovery (i.e., which is the android lying on its back with the red !) On every boot of your device.
Sent from my Galaxy Nexus using Tapatalk 2

efrant said:
Just for additional info, those files are not present on any original stock ROMs. They are added to a stock ROM if that stock ROM is updated, i.e., OTA update. They serve no purpose but to re-flash the stock recovery (i.e., which is the android lying on its back with the red !) On every boot of your device.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Ah, ok.
Speaking of nothing, what's the real deal with no OTA's available for yakju users? Is Google really working on fixing the notorious signal-drop issue?

Theshawty said:
Ah, ok.
Speaking of nothing, what's the real deal with no OTA's available for yakju users? Is Google really working on fixing the notorious signal-drop issue?
Click to expand...
Click to collapse
Who knows? I personally don't care, and no one else should either, as:
1) the OTA update file to IMM76D is availability for any yakju user to install,
2) the full IMM76D image is available to install,
3) the IMM76D source has been pushed to AOSP.
Those are three options for you to get IMM76D on your device, with the first one being the same as an OTA update.
For me, IMM76D runs perfectly fine, and better than ICL53F.
Sent from my Galaxy Nexus using Tapatalk 2

efrant said:
For me, IMM76D runs perfectly fine, and better than ICL53F. 2
Click to expand...
Click to collapse
What radio are you using? The XXLA2?

Jellybean root

ok you need to have clockworkmod installed...
Code:
fastboot flash recovery recovery.img
(insecure boot.img)
unzip boot.img.zip, boot to bootloader and
Code:
fastboot flash boot boot.img
or flash JRN84D-insecure-boot.zip from recovery
-put the CWM-SuperSU-v0.92-mod.zip on your sd and flash
done. :good:
if you have problems...
flash Koush's Jellybean repack (IMM76I OR IMM30D) http://d-h.st/Gkh
If recovery isn't sticking for you, delete recovery-from-boot.p in /system
I can do this for the other superuser as well...this is chainfire's super su

Thanks. May I clarify if I have to do both to get root or either one?

mcdull said:
Thanks. May I clarify if I have to do both to get root or either one?
Click to expand...
Click to collapse
the boot image is insecure...not necessarily needed

Oic.. thanks alot.
Is there any chance to pack the insecure kernel into cwm package as well?
I have no access to computer that allow me to apply fastboot flash. I am sure a lot of ppl will be in the same situation. Thanks alot.

mcdull said:
Oic.. thanks alot.
Is there any chance to pack the insecure kernel into cwm package as well?
I have no access to computer that allow me to apply fastboot flash. I am sure a lot of ppl will be in the same situation. Thanks alot.
Click to expand...
Click to collapse
sure, give me a minute

Okay I installed the jellybean rom from rom manager but I lost clockwork recovery, anyone got any suggestions?

pablo1215 said:
Okay I installed the jellybean rom from rom manager but I lost clockwork recovery, anyone got any suggestions?
Click to expand...
Click to collapse
bootloader mode -> reflash clockwork recovery using fastboot.

pablo1215 said:
Okay I installed the jellybean rom from rom manager but I lost clockwork recovery, anyone got any suggestions?
Click to expand...
Click to collapse
fastboot a new one in...new one will stick
Code:
fastboot flash recovery recovery.img

Thanks guys appreciate the tip.

not working
Just flashed the two .zips. SuperSU is installed, but it says that the binary needs to be updated. When it tries to update it fails, and no root apps work.

krishmasand said:
Just flashed the two .zips. SuperSU is installed, but it says that the binary needs to be updated. When it tries to update it fails, and no root apps work.
Click to expand...
Click to collapse
reboot, then open supersu and then update

Worked like a charm, I've got clockwork back after a little adb action and now I'm restoring some apps with titanium. Can't wait to see the development on this. Just think I almost sold this phone and bought a Galaxy S3 today, may wait a week or so now.

Thanks guys you are amazing!!!

Flashed both zips in cwm
Super su app is there but needs to update binary
It fails on update

tramane said:
Flashed both zips in cwm
Super su app is there but needs to update binary
It fails on update
Click to expand...
Click to collapse
ok your the second guy...first hasn't responded back. did you reboot and try again?
which "jellybean" version are you on? koush's on rom manager seems to be the best (no wifi issues for one)

ogdobber said:
fastboot a new one in...new one will stick
Code:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Is there a reason why my CWM won't stick? I fastboot a new one in and right after, I can access CWM from the bootloader menu if I don't boot into the OS yet. However, once I do boot into the OS and use ADB to reboot into recovery, it goes back to the Android with the red triangle.
What am I doing wrong? I'm usually pretty good with this stuff.

other superuser
still doesn't work, do you think you can try the other SuperUser app? D:

Enhanced said:
Is there a reason why my CWM won't stick? I fastboot a new one in and right after, I can access CWM from the bootloader menu if I don't boot into the OS yet. However, once I do boot into the OS and use ADB to reboot into recovery, it goes back to the Android with the red triangle.
What am I doing wrong? I'm usually pretty good with this stuff.
Click to expand...
Click to collapse
You'll need to delete that recovery from boot.p file otherwise it'll keep deleting CWM

[please delete]

IINexusII said:
You'll need to delete that recovery from boot.p file otherwise it'll keep deleting CWM
Click to expand...
Click to collapse
I knew common sense told me that I would need to delete the /system/recovery-from-boot.p file, but it wasn't posted here so I didn't bother.
Thanks.

Can't start ClockworkMod (URGENT)

I've installed it correctly but once i boot into recovery I just get a picture of android with a warning sign being pulled out of his stomach...
so im with factory reset phone in the middle of flashing a new rom and can't continue

I really don't know what's wrong bud you may need to use a toolkit or a program to fast boot your device back to stock. Which version of the nexus do you have?
Sent from my Galaxy Nexus using xda app-developers app

I just flashed CWM, but every time I try to boot into CWM, I keep seeing the stock recovery. Why?
If you update your Android build either using an OTA update file (either manually or over-the-air), the update placed two files on your device that re-flash the stock recovery every time you reboot your device. These two files are:
/system/etc/install-recovery.sh <== this is the script that installs the patch file
/system/recovery-from-boot.p <== this is the patch
You have to rename (or delete) one or both of them, then re-flash your custom recovery. Now it will stick.
Click to expand...
Click to collapse
This is from Efrant's Android 101 guide: http://forum.xda-developers.com/showthread.php?t=1812959

Don't delete the files, simply rename them. If you ever want to get back to stock recovery (for instance, for an OTA to install you need it to be stock) you can simply name it back to original and reboot.

Petrovski80 said:
Don't delete the files, simply rename them. If you ever want to get back to stock recovery (for instance, for an OTA to install you need it to be stock) you can simply name it back to original and reboot.
Click to expand...
Click to collapse
or you can just flash the stock recovery with fastboot.

thank you for the super fast answers guys
i tried to rename them with astro but says that i don't have permissions for that
i'm rooted

Fking1 said:
thank you for the super fast answers guys
i tried to rename them with astro but says that i don't have permissions for that
i'm rooted
Click to expand...
Click to collapse
You have to mount /system as read/write

DynamicRam said:
You have to mount /system as read/write
Click to expand...
Click to collapse
no idea how to do that

Fking1 said:
no idea how to do that
Click to expand...
Click to collapse
Use another file explorer such as Solid Explorer. https://play.google.com/store/apps/details?id=pl.solidexplorer

This is amazing, got help within minutes and as i write this the new rom is being installed, thank you so much!

JB-MR1 Help!

Hi all, I was on AKOP's milestone ROM before trying to flash their newest one. I did not do anything to the kernel or anything by the way.
I'm using ClockworkMod Recovery v6.0.2.7 and I rebooted into recovery and flashed super dark side wipe and then JB-MR1 and then gapps.
I went through the entire start up process with inputting your information and then finally I got into the actual home screen. I clicked around to see how the UI looked and then decided to reboot through the menu.
It was in the rebooting animation icon for at least 30 min before I decided to pull the battery. I want to wipe and start again but my cwm recovery isn't installing anything.
EDIT: The phone still works as I can boot into the phone and use it. I'm trying to reboot now: power button hold>reboot, but its taking ages still...need help on this reboot thanks
Any help here?
EDIT 2: Pretty much phone is "functional" but any method of trying to reboot or reboot into recovery fails
Thanks all!

Check the Md5 hash to make sure it is a good download.
Otherwise it sounds like it is CWM that can be causing issues.
Which version of gapps are you flashing?

8Fishes said:
Check the Md5 hash to make sure it is a good download.
Otherwise it sounds like it is CWM that can be causing issues.
Which version of gapps are you flashing?
Click to expand...
Click to collapse
Checked the Md5 with an app and it matches up perfectly with akop's main website.
I'm running 6.0.2.8 cwm. Is it even possible that its cwm? I used the same version to flash AKOPs new ROM.
and im flashing gapps-jb-20121212-signed.zip
Does it have anything to do with my kernel?

You aren't supposed to use super wipe with cwm 6. That is probably your problem.

meekrawb said:
You aren't supposed to use super wipe with cwm 6. That is probably your problem.
Click to expand...
Click to collapse
Thanks so much for pinpointing the problem! Is there a fix to this?
And is this the recommended method of flashing? (Taken from http://forum.xda-developers.com/showthread.php?t=1926754):
1. Wipe factory data/reset
2. Wipe cache
3. Go into mounts and storage
4. Format /system
5. Format /data
6. Format /cache
7. Enter advanced
8. Wipe dalvik
9. Flash ROM then gapps
10. Reboot and let the ROM settle for 5-10 minutes if flashing TW ROMs, this step is unnecessary for AOSP based ROMs.
11. (Optional) if flashing a new radio flash AFTER the ROM has been initially booted for the first time. No wipes are necessary when flashing a new radio but it HAS to be flashed after the ROM is loaded and settled in. Flashing a radio first and then a ROM has caused issues like the phone not even recognizing there is a network for it. ( phone remains in emergency mode )
Edit:
Pretty sure my phone is bricked now... in a continuous boot up loop... BUT i can still access recovery

Ostyrion said:
Thanks so much for pinpointing the problem! Is there a fix to this?
Edit:
Pretty sure my phone is bricked now... in a continuous boot up loop... BUT i can still access recovery
Click to expand...
Click to collapse
Yes, those are the proper flashing instructions for CWM6.
It sounds like you have a soft brick. I think your best bet is to Odin back to stock. Have a look here:
http://forum.xda-developers.com/showthread.php?t=1858435
Good luck.

meekrawb said:
Yes, those are the proper flashing instructions for CWM6.
It sounds like you have a soft brick. I think your best bet is to Odin back to stock. Have a look here:
http://forum.xda-developers.com/showthread.php?t=1858435
Good luck.
Click to expand...
Click to collapse
You sir are a saving grace!
I'll try this at once!!
I have 2 questions though.
1. in regard to kernels. Do i need to do anything (aka change my kernel?) Or is the stock kernel suitable for 4.2.1?
2. If i cant boot into my phone to get to my SD card, how do i download and put files onto my phone?

Ostyrion said:
You sir are a saving grace!
I'll try this at once!!
I have 2 questions though.
1. in regard to kernels. Do i need to do anything (aka change my kernel?) Or is the stock kernel suitable for 4.2.1?
2. If i cant boot into my phone to get to my SD card, how do i download and put files onto my phone?
Click to expand...
Click to collapse
Stock kernel is just fine.
Odin will flash the stock OS to your phone from the computer. Make sure to read the Odin directions a few times before trying it because it could hard brick if something goes wrong.

meekrawb said:
Stock kernel is just fine.
Odin will flash the stock OS to your phone from the computer. Make sure to read the Odin directions a few times before trying it because it could hard brick if something goes wrong.
Click to expand...
Click to collapse
I'm trying to read through the thread you gave me but its kinda cluttered and its hard finding exactly where to start...pointers?

From the first post of that thread you will need
1. The prerequisites
-Odin
-Drivers
-Kies(dunno if this is mandatory but I guess it couldn't hurt.)
2. T-Mobile t989 uvlhi stock ROM(Odin)
You will need some type of zip software to extract the files from this.
3. Follow the steps under Installation - Odin installation(skip step 1)
After you get the stock ROM running you can install custom recovery and then flash your custom ROMs.

meekrawb said:
From the first post of that thread you will need
1. The prerequisites
-Odin
-Drivers
-Kies(dunno if this is mandatory but I guess it couldn't hurt.)
2. T-Mobile t989 uvlhi stock ROM(Odin)
You will need some type of zip software to extract the files from this.
3. Follow the steps under Installation - Odin installation(skip step 1)
After you get the stock ROM running you can install custom recovery and then flash your custom ROMs.
Click to expand...
Click to collapse
IT WORKS!!!! I LOVE YOU!! THANK YOU SO SO SO SO SO MUCH!!
THANK YOU THANK YOU THANK YOU!!
So now that I'm back on stock ROM, is my phone still rooted? Or do i need to reroot?
Edit: Downloaded a root checker. Looks like I need to reroot. Thank you again SOOOOO much!!!

Ostyrion said:
IT WORKS!!!! I LOVE YOU!! THANK YOU SO SO SO SO SO MUCH!!
THANK YOU THANK YOU THANK YOU!!
So now that I'm back on stock ROM, is my phone still rooted? Or do i need to reroot?
Click to expand...
Click to collapse
You are welcome. You are now unrooted so you have to download the recovery of your choice to the internal SD card and flash it from the stock recovery. After you reboot back into recovery you can flash a ROM and you will be rooted.

meekrawb said:
You are welcome. You are now unrooted so you have to download the recovery of your choice to the internal SD card and flash it from the stock recovery. After you reboot back into recovery you can flash a ROM and you will be rooted.
Click to expand...
Click to collapse
So in essence, once i have cwm/twrp on my phone, i have "root"?
Just to check:
1. download cwm recovery
2. via usb put onto phone.
3. reboot into recovery
4. flash cwm
5. restart phone
6. copy AOKP ROM onto phone
7. reboot into recovery
8. flash AOKP ROM?
Again, i cant thank you enough!

Ostyrion said:
So in essence, once i have cwm/twrp on my phone, i have "root"?
Just to check:
1. download cwm recovery
2. via usb put onto phone.
3. reboot into recovery
4. flash cwm
5. restart phone
6. copy AOKP ROM onto phone
7. reboot into recovery
8. flash AOKP ROM?
Again, i cant thank you enough!
Click to expand...
Click to collapse
That should do it. You won't be rooted until you install a custom ROM though(they come already rooted).

meekrawb said:
That should do it. You won't be rooted until you install a custom ROM though(they come already rooted).
Click to expand...
Click to collapse
Apparently stock recovery doesn't allow to install via internal SD card so I need odin to flash cwm dont i?
What boxes do i need checked besides the PDA checkbox?

Ostyrion said:
Apparently stock recovery doesn't allow to install via internal SD card so I need odin to flash cwm dont i?
What boxes do i need checked besides the PDA checkbox?
Click to expand...
Click to collapse
If you download the flashable zip from the first post here:
http://forum.xda-developers.com/showthread.php?p=30497342
you should be able to flash it from stock recovery. If it doesn't work I will have to look up how to install it with Odin.

meekrawb said:
If you download the flashable zip from the first post here:
http://forum.xda-developers.com/showthread.php?p=30497342
you should be able to flash it from stock recovery. If it doesn't work I will have to look up how to install it with Odin.
Click to expand...
Click to collapse
I actually got cwm 5.0.2.7 on my phone through odin. I just need root now to upgrade it to the most recent version.
I've been seeing busybox paired with superuser.
Do i need busybox? Or can i just flash superuser through cwm recovery 5.0.2.7?

Ostyrion said:
I actually got cwm 5.0.2.7 on my phone through odin. I just need root now to upgrade it to the most recent version.
I've been seeing busybox paired with superuser.
Do i need busybox? Or can i just flash superuser through cwm recovery 5.0.2.7?
Click to expand...
Click to collapse
Why do you need root? You should be able to just flash the newer cwm zip.

Here is a superuser zip that I used successfully on my t989:

meekrawb said:
Here is a superuser zip that I used successfully on my t989:
Click to expand...
Click to collapse
Thanks for the file!
I downloaded cwm from this site:
http://www.clockworkmod.com/rommanager
but it comes as an img file...and I dont seem to be able to flash that from recovery

[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.