So i flashed L and played around with it. I need an app that doesnt work with L so i need to go back to kitkat. Is it as simple as restoring my backup from TWRP? Or will that brick something since im going from newer to older?
Yes it's that simple. Going from newer to older has never been an issue with a Nexus.
nhizzat said:
Yes it's that simple. Going from newer to older has never been an issue with a Nexus.
Click to expand...
Click to collapse
For some reason i cant get twrp flashed on my nexus 7. When i flash it via fastboot and reboot to it, it either stays at the google screen with the lock. Or if i reboot and try it goes back to stock android recovery. Also noticed it says SECURE BOOT: Enabled which i dont think it says on my nexus 5
I don't think your Nexus 5 should say secure boot as disabled. As for the stock recovery, after flashing twrp, you have to rename recovery_from_boot.p in /system to recovery_from_boot.bak
Related
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?
I rooted my tablet and installed TWRP end of august.
Two days ago I installed 4.4 with an OTA update which broke the phone, it always booted into recovery. I learned that TWRP was incompatible with 4.4 older versions of TWRP might cause problems with 4.4 and flashed the 4.3 factory image using adb. The tablet is now working again.
I'm just not sure how to proceed now. It seems the TWRP recovery is gone, because from Fastboot when I select recovery I get the dead android with the red triangle. Can I just update by following this post?
bur2000 said:
I rooted my tablet and installed TWRP end of august.
Two days ago I installed 4.4 with an OTA update which broke the phone, it always booted into recovery. I learned that TWRP was incompatible with 4.4 and flashed the 4.3 factory image using adb. The tablet is now working again.
I'm just not sure how to proceed now. It seems the TWRP recovery is gone, because from Fastboot when I select recovery I get the dead android with the red triangle. Can I just update by following this post?
Click to expand...
Click to collapse
Where have you read twrp is not compatible with 4.4? Many people are using twrp with 4.4. You should use the latest version which supports SELinux security contexts.
It is probably easiest if you just flash the KRT16S factory image from that thread.
sfhub said:
Where have you read twrp is not compatible with 4.4? Many people are using twrp with 4.4. You should use the latest version which supports SELinux security contexts.
Click to expand...
Click to collapse
It doesn't seem to happen for everybody, maybe it's older versions of TWRP. Mine was from August. I rephrased my original post to make that clear. There are some threads here about the problem and if you google for it you'll find some more warnings. It's always the same thing, the tablet will only boot into recovery after an OTA with TWRP:
http://forum.xda-developers.com/showthread.php?p=47709956
http://forum.xda-developers.com/showthread.php?p=47713265
http://forum.xda-developers.com/showthread.php?t=2537669
http://www.droid-life.com/2013/11/1...krt16o-official-update-for-nexus-7-2012-wifi/ (in the comments)
http://forum.xda-developers.com/showthread.php?t=2510810
Thanks for your reply though, so I'll try flashing the factory image. Should I use adb for that or newest TWRP? Also the red triangle means my custom recovery is gone, correct?
bur2000 said:
It doesn't seem to happen for everybody, maybe it's older versions of TWRP. Mine was from August. I rephrased my original post to make that clear. There are some threads here about the problem and if you google for it you'll find some more warnings. It's always the same thing, the tablet will only boot into recovery after an OTA with TWRP:
http://forum.xda-developers.com/showthread.php?p=47709956
http://forum.xda-developers.com/showthread.php?p=47713265
http://forum.xda-developers.com/showthread.php?t=2537669
http://www.droid-life.com/2013/11/1...krt16o-official-update-for-nexus-7-2012-wifi/ (in the comments)
http://forum.xda-developers.com/showthread.php?t=2510810
Thanks for your reply though, so I'll try flashing the factory image. Should I use adb for that or newest TWRP? Also the red triangle means my custom recovery is gone, correct?
Click to expand...
Click to collapse
Personally I think it is easiest to flash the factory image but you probably need around the same number of steps either way.
The factory image is meant to flash in boot loader using fastboot, not using adb.
The fallen android means you are using stock recovery. It is an image that hides the recovery menu. press/hold power, press/release VolUp, release Power to see the actual recovery menu and any errors which might have occured
sfhub said:
Personally I think it is easiest to flash the factory image but you probably need around the same number of steps either way.
Click to expand...
Click to collapse
Thanks again, all worked well going along with your guide. Only thing to do now is getting TWRP and SU flashed.
It seems like I'm not really up-to-date anymore when it comes to flashing, I only knew of using recovery and never heard of sideload or using fastboot to flash any images.
My phone current status
Unlocked
S-on (I looked for this and couldn't find solution to s-off)
Latest twrp flashed
I try to flash the supersu, it flashed, but supersu app doesn't detect the root binary. :l
Within twrp, I try to do a back up of nandroid, but i get error that the backup file is 0 bytes and back up failed.
Everytime I reboot system from twrp, it says there's no OS, but I boot into the stock OS fine.
-
From this what else do I need to do or fix?
can I just flash a custom rom? I don't ever do backup on any of my android. if something goes wrong, I just flash a new rom :l
I came from a nexus 6 so this is a bit confusing.
Use the older version of twrp. I think 5.0. I had the same issue until I did that.
I used twrp 2.6.8.3 after that no probs all good, before on 2.8.6.0 no os and no back up
dustin4vn said:
My phone current status
Unlocked
S-on (I looked for this and couldn't find solution to s-off)
Latest twrp flashed
I try to flash the supersu, it flashed, but supersu app doesn't detect the root binary. :l
Within twrp, I try to do a back up of nandroid, but i get error that the backup file is 0 bytes and back up failed.
Everytime I reboot system from twrp, it says there's no OS, but I boot into the stock OS fine.
-
From this what else do I need to do or fix?
can I just flash a custom rom? I don't ever do backup on any of my android. if something goes wrong, I just flash a new rom :l
I came from a nexus 6 so this is a bit confusing.
Click to expand...
Click to collapse
I found I had to flash the Beta version of recovery, and an additional step. Definitely backup stock as there are few RUUs right now. Check out details HERE
angasreid said:
I found I had to flash the Beta version of recovery, and an additional step. Definitely backup stock as there are few RUUs right now. Check out details HERE
Click to expand...
Click to collapse
Thanks. I noticed that. I keep flashing with the stable version and nothing works lol. I don't ever back up my roms lmao. Had like 50 android phones, I hate stock with all my might. No reason to ever go back to stock for me lol.
So for installing older ROMs I wanted to flash the jellybean factory image and "update" it using the a rom but when I tried it after unlocking the bootloader, I installed 4.3, 4.4, and 4.4.4 none of which worked. So I was wondering what is wrong with the device. (By not working I mean not even bootlooping just on the "Google" screen). Then after a 100 tries I got an idea to install 5.0 and it worked, phew! But still I am quite disappointed I can't install older firmwares. I did get this device like 3 days ago, so it might have a different hardware revision or something, I also noticed it has something called "secure boot" which didn't sound good to me. Hopefully you guys can clarify what is wrong. Thanks!
Did you flash the bootloader image as well as the boot and system.img? It's different between 4.x and 5.x.
If you did then I don't know.. run fastboot format cache after flashing the images it can fix things sometimes. Nothing more should be needed. Secure boot has nothing to do with it. That's on mine bought in '13.
Why would you want to flash JB to "update it using the a rom?" Not really clear.
Do you mean take all the ots? That's probably a bad idea just flash the latest image. If you mean you want to flash a custom rom just flash twrp then flash whatever rom you want doesn't matter what was previously on it but you'll need the right bootloader.
If you just want to check out all the versions you should be able to easily with just the bootloader, boot and system images from the factory image zip. Unless it's something to do with that new batch that popped up earlier this year (I think?).
Trying Something Different
Ok I reinstalled latest 6.0, now I see another problem after flashing custom recovery (TWRP) I see mounting errors for example " E:Unable to mount '/system' " even though I can still boot into android fine. (I can't mount anything, I was hoping to at least have a custom recovery.) Anyway hope you can help me out, I am probably doing a dumb mistake.
Fixed!
googleiscoul said:
Ok I reinstalled latest 6.0, now I see another problem after flashing custom recovery (TWRP) I see mounting errors for example " E:Unable to mount '/system' " even though I can still boot into android fine. (I can't mount anything, I was hoping to at least have a custom recovery.) Anyway hope you can help me out, I am probably doing a dumb mistake.
Click to expand...
Click to collapse
Ok cool fixed my recovery problem with this post - http://forum.xda-developers.com/nexus-7-2013/nexus-7-2013-qa/mount-recovery-t3064562
so i permanetly installed twrp and was trying to put on a custom rom. I wiped everything and now twrp wont boot at all from the boot loader. i tried the temporary boot in fast boot and it still wont boot and i have no recovery os. PLEASE help to get andoid ten back on or anything i cant afford to loose this phone !
anntaoo95 said:
so i permanetly installed twrp and was trying to put on a custom rom. I wiped everything and now twrp wont boot at all from the boot loader. i tried the temporary boot in fast boot and it still wont boot and i have no recovery os. PLEASE help to get andoid ten back on or anything i cant afford to loose this phone !
Click to expand...
Click to collapse
TWRP is not compatible with Android 10. I hope someone can help you out.
i have twrp on my phone but cant install any apps the boot loader never shows up i keep getting error 7s when trying to install a rom. i just want to get the factory os back on. THere has to be a way
anntaoo95 said:
i have twrp on my phone but cant install any apps the boot loader never shows up i keep getting error 7s when trying to install a rom. i just want to get the factory os back on. THere has to be a way
Click to expand...
Click to collapse
Can you just flash back to a factory image??
Grab factory image from https://developers.google.com/android/images
And you'll be all set. Yes, you'll lose root and any data, but you'll be back on stock.
Thanks so much.so i tried flashing the os before and it failed. this time i went back and copied and pasted the fastboot files into the os folder with the script. It worked perdectly. I really want to put roms on my phone. I think i may have messed something up when installing twerp and formating and wiping the data
Afaik, twrp is not (yet) installable, so you'd have to
Code:
fastboot boot twrp.img
every time to access twrp. Android 10 is still very young, so have a little patience, and in couple of months you'll have plenty of fun with ROMs
And congrats for success, even if it is returning to stock.
calinorg said:
Android 10 is still very young, so have a little patience.
Click to expand...
Click to collapse
To be honest, I doubt TWRP will ever fully work on Q for the newer pixel devices. We have a logical partitioning system so it's impossible to mount /system /vendor and /product to be writable.
From what I've been hearing, custom rom developers have just been flashing their ROMs while in stock recovery. I'm going to assume that'll be the norm when Q ROMs are released for us.
Sent from my Google Pixel 3a XL using XDA Labs
I do believe someone will come up with a solution. If John wu managed to get magisk working (and rooting is ever so harder with new Android partitioning system), I don't see why couldn't we have twrp. Maybe it won't be installable, but it could work...