Basically what the topic says, every time I try installing Beta 6 using TWRP, it'll tell me there's no MD5, a warning that there's no "file_context" (if I remember correctly), and then a red "failed" message after 30-50 seconds. Then I'd have to use my backup file I created before flashing the ROM just to reboot the phone.
And just in case someone asks for what phone/ROM I'm using:
Galaxy Nexus (Toro)
Paranoid Android 3.99
Any idea why this is happening?
Have you updated twrp to the newest version. That's the most common problem
Sent from my Nexus 5
Not sure how to do that, can anyone explain how to do that? Goo.im doesn't want to update it for me, or, even want to work. ._.
Fastboot flash the image on
Sent from my Nexus 5
Related
my bro got a rooted galaxy nexus with CWM recovery !
we want to install the OTA updates (Device status is normal so he can download the update) the problem is he gets Failed message when he tries to install updates because of CWM recovery! anyone knows how to get back to Stock recovery on nexus i'm noob in nexus fastboot stuff (CMD fastboot command)! also the proper stock recovery.img PLZ ... (i've attached a screen shot of the setting -> About device Screen).
he does not get the error message because of CWM.
he gets the error message because something isnt stock.
what is the assert error message when you try and install the update in CWM?
Zepius said:
he does not get the error message because of CWM.
he gets the error message because something isnt stock.
what is the assert error message when you try and install the update in CWM?
Click to expand...
Click to collapse
not in CWM the phone downloads the update pakage restarts and tries to install the updates and it fails there is not error message just fails!
If you want to set the phone to stock...
http://forum.xda-developers.com/showthread.php?t=1626895
If you want to just update to a newer/non-stock ROM, pick one and flash it.
Parsa-n7100 said:
not in CWM the phone downloads the update pakage restarts and tries to install the updates and it fails there is not error message just fails!
Click to expand...
Click to collapse
TWRP shows me the error message...
either way, his phone isnt stock. thats the problem. he modded some system file or tried a diff radio, etc.
its not failing because of cwm.
looks like i need to backup every thing and flash a stock ROM! where can i find the latest official rom for galaxy nexus ?
or what about CM is it stable enough for Daily use?
Parsa-n7100 said:
looks like i need to backup every thing and flash a stock ROM! where can i find the latest official rom for galaxy nexus ?
or what about CM is it stable enough for Daily use?
Click to expand...
Click to collapse
In the link I posted
Doesn't anybody use search or browses the forums around before asking questions??
a maguro wrote this.
bk201doesntexist said:
Doesn't anybody use search or browses the forums around before asking questions??
a maguro wrote this.
Click to expand...
Click to collapse
or read even.
Hey guys, I don't know if I am posting this on the right place, but there it goes.
I've been trying, without sucess, to update my Galaxy Note II LTE to the omni 4.4 android rom. I'm using the goomanager app, but when the countdown to download the image finishes, it gives me an error, something like "the server is down".
So I downloaded the img from a mirror but the app doesn't have a function to use a downloaded image, you have to do it with the app.
But, as I said, I can't download it
Is there any other method to do it?
Yep. With your downloaded TWRP zip (the latest one, I hope), go to your current Custom Recovery and flash that zip there. It will take 2 minutes and will update your Recovery to the desired one. Then proceed with the ROM flash, GAPPS and everything else.
The error you get is because the host has some maintenance problems, I went through the same thing 3 hours ago
Thanks man, it helped a lot!
I had no problems rooting my s3 and putting custom recovery but when I attempt to flash either cyanogenmod or resurrection remix I get the status error 7. Then if I delete the Assert portion I either get status 6 error or it goes into a boot loop and I have to reinstall stock again with odin. I have also downloaded notepad++ as recommended to no avail.
You need to be on at least MD5 bootloader/firmware.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
You need to be on at least MD5 bootloader/firmware.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I just looked on the firmware I flashed on my phone whenever it wouldn't boot and it is md5.
So are you saying you tried to flash MD5 and it would not boot? What were you running before flashing? Did you factory reset?
DocHoliday77 said:
So are you saying you tried to flash MD5 and it would not boot? What were you running before flashing? Did you factory reset?
Click to expand...
Click to collapse
I have tried multiple roms and sometimes got error 7 sometimes error 6 and sometimes unable to boot, at which point I would then flash the stock firmware with odin on it and then it would work again, but I want to be able to put a firmware with kitkat on it.
Youd probably be best off updating to 4.3 firmware if you haven't already. If you're out of warranty there is little reason not to update imo.
Then use twrp 2.7.0.0 for your recovery. Some have had recent problems flashing with cwm.
If you still have issues, let us know exactly what steps you followed and exactly what you were trying to flash.
Sent from my SGH-T999 using Tapatalk
It came with 4.3, that's not the issue, I have tried both twrp and cwm to flash a cyanogenmod kitkat rom and I get the status error 7 at first, if I do what is said to get rid of that and delete the lines at the start then it gets a status error 6. At which point it no longer boots then I need to flash it back to the stock firmware.
Did you try the latest version of either Recoveries ? If its not the latest version you'd get error.
With the 4.3 firmware, you do not have to remove any Assert Lines from the updater Script. Just in case go back to the last stable release of CM 11.
27a
Just updated to a newer cwm to no avail, still getting status 7 error.
What CWM Version is that ?
6.0.4.5
Please post the Recovery Log. Its present in /cache/recovery
62453634 08
I don't see a cache folder
deadly8123 said:
I don't see a cache folder
Click to expand...
Click to collapse
You need a Root Explorer with Root access. Remount System as R/W in your Root Explorer.
Finally was able to do it I flashed a d2lte rom instead of a d2tmo rom.
I just received my Nexus 7 2013 16gb WiFi from amazon a few days ago, and it's been great. The recovery has had issues though, it tried to do an OTA update the first day I got it, and when it rebooted, it just stayed on a black screen instead of actually going to recovery, so I had to hard reboot it, to get back to the jellybean it came with. This wasn't a major issue at the time, since then I've just unlocked it and flashed kitkat via fastboot (I'll get lollipop once it has gravitybox or something similar). But since then, I've rooted it and installed TWRP, and TWRP runs fine, but has some weird issues. It seems to not actually see the OS at all, or even the storage filesystem. I have to do a hard reboot to even get out of TWRP, as trying to get out normally gives me the error "Warning blah blah no OS installed, are you sure?", to which I tell it I'm sure and it just reboots recovery. But doing a hard reboot boots into the OS just fine. Am I doing something wrong? TWRP was installed AFTER I installed KitKat and the updated bootloader with the official google factory images, is this a problem?
Some images of what I'm seeing:
1
2
Maybe it's because you're running TWRP 2.8.2.0 which is for Lollipop. If it doesn't work with 2.8.1.0, try with the lastest 2.8.2.2. Running Lollipop at least, everyone had the same problem with both 2.8.2.0 and 2.8.2.1.
where can I place the recovery image where twrp will see it?
Thanks for your suggestion LittleConfucy. I was wondering if you can tell me where to put recovery image that TWRP can see it?
Flashing is a problem without being able to access the image to flash in the stripped down rom file system that twrp boots into. No shared directory in /cache.
Nevermind I got it dialed in.
Sent from my Nexus 7 using xda app-developers app
What did you do to fix this? I just had the exact same thing happen. I had a 5.0 rom and tried to flash a different one but once in twrp no files and the no os line when I tried to reboot. I'm on 2.8.2.0
kingston73 said:
What did you do to fix this? I just had the exact same thing happen. I had a 5.0 rom and tried to flash a different one but once in twrp no files and the no os line when I tried to reboot. I'm on 2.8.2.0
Click to expand...
Click to collapse
I just flashed to 2.8.2.2 and twrp started seeing my internal storage again.
el80ne said:
I just flashed to 2.8.2.2 and twrp started seeing my internal storage again.
Click to expand...
Click to collapse
So if I hold power down and force it to reboot it should boot back into the OS? And once in the OS will I be able to use TWRP manager to flash the latest?
kingston73 said:
So if I hold power down and force it to reboot it should boot back into the OS? And once in the OS will I be able to use TWRP manager to flash the latest?
Click to expand...
Click to collapse
That's what I did.
Sent from my SM-G900V using XDA Free mobile app
So here is the deal. I'm not new to flashing and rooting and whatnot... I've been doing this for a while and I've never been stumped like this.
I just got a Nexus 7 for Christmas and after using it for all of 5 minutes, I realized that CM just has a lot of features that are just missing from the stock Nexus experience. I also want to get ROOT access. Now, like a complete moron, the first time I booted up my new tablet, I let it run through all the OTAs, so now I'm on 6.0.1.
From what I've read and what I've seen, things have changed quite a bit for Marshmallow. But here is where I'm at and hopefully someone can help me out.
I've unlocked the bootloader using ADB (so you can assume I know how to use ADB and fastboot on it own without any other toolkits)
I've downloaded TWRP, SuperSU and the latest nightly of CM13.
I used fastboot to flash TWRP and this is where things get crazy.
- First if I reboot after flashing TWRP and reboot back into recovery, TWRP is gone and stock recovery is restored.- I believe that the OEM ROM is re-flashing my recovery at startup... no problem... flashing CM13 should fix that- Second. If I flash TWRP, then boot into TWRP immediately without booting the ROM, TWRP doesn't recognize any of my partitions.If I tell TWRP to reboot, it actually tells me that there is no ROM installed.
So, that's where I'm stuck.
Do I flash TWRP, then just flash CM13 and SuperSU and like magic everything works? Is there a step I'm missing? Is there some special version of a zip I'm missing...
I've got downloaded right now:
TWRP: twrp-2.8.7.0-flo
CM13: cm-13.0-20151229-NIGHTLY-flo
GAPPS: open_gapps-arm-6.0-nano-20151225
SuperSU: UPDATE-SuperSU-v2.46
I was in a similar situation to you I managed to root my new nexus 7 with the Nexus Root Toolkit then had to use an app called flashify for installing TWRP hope this helps.
Figured it out. Turns out Google started using a new flash part in the Nexus 7 that I got. Using the MultiRom version of TWRP I was able to flash CM13.
Source:
http://forum.xda-developers.com/nexus-7-2013/nexus-7-2013-qa/mount-recovery-t3064562
i'm working on the same thing. did you have any luck installing open gapps? I'm getting an error system is out of space
cursixx said:
i'm working on the same thing. did you have any luck installing open gapps? I'm getting an error system is out of space
Click to expand...
Click to collapse
Yea I'm having the same issue, I flashed pure nexus and gapps with no issue, but when I tried to flash CM13, I got the "out of space" error when installing gapps
^Is the CM rom bigger? Maybe system is low on space.
Can you flash a smaller version of open gapps?
yosmokinman said:
^Is the CM rom bigger? Maybe system is low on space.
Can you flash a smaller version of open gapps?
Click to expand...
Click to collapse
yes I was able to flash the nano package
I flashed the Open GAPPS nano package right off the bat and I had no such problems. I prefer the minimum package anyways since I don't care about such apps as Google Newsstand and such. Anything I want, I just download off the Play store.
According to what I have read, you should have a custom kernel in order for you to root Marshmallow.