Related
So I wanted to flash the FNV AoSP ROM on my Galaxy Nexus GSM. First off al I flashed the 4.2 takyu version and rooted it with SuperSU. After that I flashed the recovery with Clockwork 6.0.1.5 after that I did the following things:
- Wipe data/factory reset
- Mounts and storage > Format /system
- Wipe cache
- Wipe dalvik
- Flashed ROM fnv_20121119_003_maguro.zip
- Flash 4.2 gapps
Am I doing something wrong?
When you say, won't work what do you mean?
Does the recovery not flash the file? If so, what error does it say?
Does it not boot after what seems to be a successful flash in recovery? Do you see the bootanimation?
cupfulloflol said:
When you say, won't work what do you mean?
Does the recovery not flash the file? If so, what error does it say?
Does it not boot after what seems to be a successful flash in recovery? Do you see the bootanimation?
Click to expand...
Click to collapse
It flashs the files and all but it gets into a bootloop. I see the costum bootanimation of the ROM, but it keeps playing and it won't start up. After some time the screen goes black, but it's not off, because if I hold down power it won't turn on so I have to pull battery.
CheesieOnion said:
It flashs the files and all but it gets into a bootloop. I see the costum bootanimation of the ROM, but it keeps playing and it won't start up. After some time the screen goes black, but it's not off, because if I hold down power it won't turn on so I have to pull battery.
Click to expand...
Click to collapse
Your ROM name seems to show that it is a recent build. A quick search around, the last official FNV ROM I see was uploaded in September. The Gerrit, Github, Twitter, and threads here and on another site seem to have been untouched for quite some time.
Of course I am a little out of the loop, so perhaps I am missing something. As devs often post things in IRC, or in other non-official channels. Did you get this ROM from a trusted spot?
That said, it could be a ROM issue perhaps.
CheesieOnion said:
So I wanted to flash the FNV AoSP ROM on my Galaxy Nexus GSM. First off al I flashed the 4.2 takyu version and rooted it with SuperSU. After that I flashed the recovery with Clockwork 6.0.1.5 after that I did the following things:
- Wipe data/factory reset
- Mounts and storage > Format /system
- Wipe cache
- Wipe dalvik
- Flashed ROM fnv_20121119_003_maguro.zip
- Flash 4.2 gapps
Am I doing something wrong?
Click to expand...
Click to collapse
it probably doesnt need the gapps. try reflashing, but without the gapps. don't wipe anything.
cupfulloflol said:
Your ROM name seems to show that it is a recent build. A quick search around, the last official FNV ROM I see was uploaded in September. The Gerrit, Github, Twitter, and threads here and on another site seem to have been untouched for quite some time.
Of course I am a little out of the loop, so perhaps I am missing something. As devs often post things in IRC, or in other non-official channels. Did you get this ROM from a trusted spot?
That said, it could be a ROM issue perhaps.
Click to expand...
Click to collapse
I got the rom from the topic here on XDA. It is the build from 19 november.
simms22 said:
it probably doesnt need the gapps. try reflashing, but without the gapps. don't wipe anything.
Click to expand...
Click to collapse
In the instuctions in the ROM-topic it says it needs them and I also need them to use.
CheesieOnion said:
I got the rom from the topic here on XDA. It is the build from 19 november.
In the instuctions in the ROM-topic it says it needs them and I also need them to use.
Click to expand...
Click to collapse
install the gapps from the play store. you can flash without them, besides the ones that you cant get from the play store are included. you can try it, or just stay in your bootloop, its your call.
CheesieOnion said:
I got the rom from the topic here on XDA. It is the build from 19 november.
Click to expand...
Click to collapse
Ah, my bad I didn't realize it was picked up by someone else, I see that now (which I thank you for the heads up that it is back in production). I was just making sure you weren't flashing something that wasn't ready for public use, and that it was a real ROM.
I'm not sure if this is intentional or not, and I couldn't find an answer with a search, but is updating Cyanogenmod with the zip files from get.cm supposed to also update the recovery in the phone at the same time?
I came from using Captivate before, and it updated the recovery as well with the updates, but so far I have not had a recovery update that has come trough a ROM update on my Galaxy S III. I can manually update the recovery trough ROM Manager if I need to, but I was not expecting to need to update recovery with it.
Metal_Koola said:
I'm not sure if this is intentional or not, and I couldn't find an answer with a search, but is updating Cyanogenmod with the zip files from get.cm supposed to also update the recovery in the phone at the same time?
I came from using Captivate before, and it updated the recovery as well with the updates, but so far I have not had a recovery update that has come trough a ROM update on my Galaxy S III. I can manually update the recovery trough ROM Manager if I need to, but I was not expecting to need to update recovery with it.
Click to expand...
Click to collapse
I've flashed cyanogenmod with twrp and it was flawless. Nothing went wrong. Twrp doesnt need much updates like CWM constantly does. but hey your choice!
Now to your question. I have flashed cyanogen mod with twrp and before i had twrp i flashed it with CWM i have never seen it update my recovery. Are you sure that was a feature on that nightly build?
amzi said:
I've flashed cyanogenmod with twrp and it was flawless. Nothing went wrong. Twrp doesnt need much updates like CWM constantly does. but hey your choice!
Now to your question. I have flashed cyanogen mod with twrp and before i had twrp i flashed it with CWM i have never seen it update my recovery. Are you sure that was a feature on that nightly build?
Click to expand...
Click to collapse
Well, I skim trough the patch notes, and I see patch notes about the recovery and how it's being updated in the github, and I was wondering why it wasn't being pushed to the devices at the same time as I update. But if they stopped including the CWM recovery with CM, it would make sense.
Metal_Koola said:
Well, I skim trough the patch notes, and I see patch notes about the recovery and how it's being updated in the github, and I was wondering why it wasn't being pushed to the devices at the same time as I update. But if they stopped including the CWM recovery with CM, it would make sense.
Click to expand...
Click to collapse
While I cannot answer your question myself, I can help elaborate with the hope you get a better response. The question posed here pertains to the recovery image for the ROM that holds the fresh boot image of all the system files ('factory reset')
I haven't spent any time researching how Android recoveries function - but when you update CM through the OTA updater, I believe it only patches modules in the system rather than updating the entire boot image itself - if they updated the whole package daily that would be terribly taxing on the person packaging and distributing the ROM, not to mention ISP bandwidth (I have never tried CM myself, so I couldn't tell you for certain if this is the way it works or not).
In any case, the OP is asking about the ROM image in recovery not the recovery itself (i.e. - TWRP, CWM, etc.) . Hopefully someone with a better understanding of Android can chime in for you.
Sent from my SGH-I747
I've been flashing CM roms for years, for different phones, and have never seen it include a recovery.
marinierb said:
I've been flashing CM roms for years, for different phones, and have never seen it include a recovery.
Click to expand...
Click to collapse
Alright, it might have been special for my Captivate then. Thanks for letting me know.
my current rom is cm-10.1-20130312-NIGHTLY on my HTC one X and once i try to update to any of the new released updates starting cm-10.1-20130313-NIGHTLY the device download the update and install it in the recovery mode .. but once its done and reboot its stuck on the HTC screen
PS : i made a recovery for my cm-10.1-20130312-NIGHTLY and when i restore it then it works again as cm-10.1-20130312-NIGHTLY
- my CWM is updated
- the HBoot version is 1.36
any advice's !
Vendor blobs have been subject to a DMCA takedown since 13th.
None of the nightlies built after that date boot.
Flash a staging build.
Sent from my One X using xda premium
Re: [Q] Problem with updating to cm-10.1-20130315-NIGHTLY
there is no stable mode updates for the Cm 10.1x on HTC one x .. could the update of Hboot fix this problem and can be able to use the new nightly versions !
same problem here, but i don't have any backup from my old rom. One question, is there any way to go back to any rom for me now? or my phone is dead...?
Problem with updating to cm-10.1-20130315-NIGHTLY-
adaspb said:
same problem here, but i don't have any backup from my old rom. One question, is there any way to go back to any rom for me now? or my phone is dead...?
Click to expand...
Click to collapse
as long as there is no back up then you need to install cm-10.1-20130315-NIGHTLY if you have it already .. but for sure you data which not saved or no online backup for it will be lost
ICXC said:
there is no stable mode updates for the Cm 10.1x on HTC one x .. could the update of Hboot fix this problem and can be able to use the new nightly versions !
Click to expand...
Click to collapse
Nope, the dmca crap needs to be cleared first. Flash staging 5 for latest changes.
adaspb said:
same problem here, but i don't have any backup from my old rom. One question, is there any way to go back to any rom for me now? or my phone is dead...?
Click to expand...
Click to collapse
Sure you can. Download it with your PC, transfer to phone, wipe and flash. Then flash boot.
Sent from my One X using xda premium
ICXC said:
my current rom is cm-10.1-20130312-NIGHTLY on my HTC one X and once i try to update to any of the new released updates starting cm-10.1-20130313-NIGHTLY the device download the update and install it in the recovery mode .. but once its done and reboot its stuck on the HTC screen
PS : i made a recovery for my cm-10.1-20130312-NIGHTLY and when i restore it then it works again as cm-10.1-20130312-NIGHTLY
- my CWM is updated
- the HBoot version is 1.36
any advice's !
Click to expand...
Click to collapse
Hi
they mentioned the issue in the official thread
http://forum.xda-developers.com/showpost.php?p=29098167&postcount=1
you need to flash the "vendor installer for endeavoru cm-10.1" after flashing the ROM/update
wipe data / format system (if coming from different ROM)
flash the rom or the update
flash the vendor installed
flash gapps (if not installed)
you can download the vendor installer from here : http://d-h.st/487
I advice you to check on the official thread every once in a while, they update it with a lot of useful info
---------- Post added at 11:38 AM ---------- Previous post was at 11:26 AM ----------
adaspb said:
same problem here, but i don't have any backup from my old rom. One question, is there any way to go back to any rom for me now? or my phone is dead...?
Click to expand...
Click to collapse
if you have an old ROM zip file on your SD, you can just flash it back without any loss of data or settings (in theory)
but if you already flashed a new nightly , just flash the Vendor installer and you're good to go
1st download the vendor installer , found in the official post : Here
now push it to your SD. you can use adb push command or just mound your SD using CWM > mount and storage > mount USB storage
and just copy the file as usual, and flash it over the current ROM and you should be fine
guys, thank you i've got my phone up and working thank to yous. Next time i'll read stuff more carefully, thanks again!
TToivanen said:
Vendor blobs have been subject to a DMCA takedown since 13th.
None of the nightlies built after that date boot.
Flash a staging build.
Sent from my One X using xda premium
Click to expand...
Click to collapse
partially true! , you can still use NIGHTLIES but you need to flash the vendor installer after every update
adaspb said:
guys, thank you i've got my phone up and working thank to yous. Next time i'll read stuff more carefully, thanks again!
Click to expand...
Click to collapse
You're welcome , and it's OK ... I had my share of mystery issues before I learned to read the threads carefully
I'm glad you got things to work again
Maher88 said:
partially true! , you can still use NIGHTLIES but you need to flash the vendor installer after every update
Click to expand...
Click to collapse
I have currently cm-10.1-20130314-NIGHTLY-endeavoru (had to install also that vendor file as well). If I flash newer nightly build (e.g. 20130318) do I have to reconfigure and reinstall all apps after update?
No
MaRmARk0 said:
I have currently cm-10.1-20130314-NIGHTLY-endeavoru (had to install also that vendor file as well). If I flash newer nightly build (e.g. 20130318) do I have to reconfigure and reinstall all apps after update?
Click to expand...
Click to collapse
Not at all, you can update easily using CM updater, or the regular flashing ... you just need to flash the vendor after every update
and the the data/apps/settings will not be touched as long as you don't wipe
don't forget to read the change-logs, if you see kernel related changes, you need to flash the boot.img from the update
otherwise you don't have to
This is a source-built version of CWM version 6.0.4.9 for Oneplus ONLY. Do not attempt to use this recovery on any other device.
Tested on Oneplus 64 Gb and 16 GB
Features:
OpenRecoveryScript-compatible
Backup/Restore
Mount/Unmount/Format Partitions
Warnings:
- I am not to be held responsible if you brick your device using this.
Bugs:
I have not managed to find any. If you find one, feel free to let me know.
Additional Notes:
- I will attempt to maintain this in my spare time. If a new release comes out that you are interested in and I have not updated yet, feel free to let me know.
- To flash this unzip files and click on recovery_start.bat
- To flash via fastboot, use only the Recovery Image File.
Download:
Version 6.0.4.9 (June 11th, 2014)
Link
http://d-h.st/XZ9
EDIT: Typo corrected in OP.
dansou901 said:
Kindle Fire HD 7? In Oneplus One section?
Click to expand...
Click to collapse
sorry typo error. Recovery is for oneplus
@acer73 any chance at compiling the touch version?
dmo580 said:
@acer73 any chance at compiling the touch version?
Click to expand...
Click to collapse
This is last ver with swipe (touch)
acer73 said:
This is a source-built version of CWM version 6.0.4.9 for Oneplus ONLY. Do not attempt to use this recovery on any other device.
Tested on Oneplus 64 Gb and 16 GB
Features:
OpenRecoveryScript-compatible
Backup/Restore
Mount/Unmount/Format Partitions
Warnings:
- I am not to be held responsible if you brick your device using this.
Bugs:
I have not managed to find any. If you find one, feel free to let me know.
Additional Notes:
- I will attempt to maintain this in my spare time. If a new release comes out that you are interested in and I have not updated yet, feel free to let me know.
- To flash this unzip files and click on recovery_start.bat
- To flash via fastboot, use only the Recovery Image File.
Download:
Version 6.0.4.9 (June 11th, 2014)
Link
http://d-h.st/XZ9
Click to expand...
Click to collapse
grazie mille
ha qualche bug ?
Don't quote OP and please use English.
good news!thanks!
Dualboot
Hi everyone
I have a Xiaomi M2s right now and the thing i like the most about the device is that it has 2 system partitions and that I can install MIUI on my first partition and CM11 on my second partition. This is ideal if you want to test a ROM but keep one stable system.
Is there any chance that there will be a way to re-partition the one plus to have this? Also CMW would need to have true dual boot right or is this a stock feature?
I don't know if partitioning is common on other devices?
The backups created appear to not have the correct dates for filenames. They start with 1970...
Is this a offical build? Will it be listened on clockworkmod.com anytime soon?
Does anybody have problems with mounting the SD card through CWM? On my device CWM wont backup because of not being able to mount the sd card. I solved this error by reflashing CWM through fastboot, but why does this error occur?
fiz:ik said:
Does anybody have problems with mounting the SD card through CWM? On my device CWM wont backup because of not being able to mount the sd card. I solved this error by reflashing CWM through fastboot, but why does this error occur?
Click to expand...
Click to collapse
Seems that it happens on all recoveries ATM. Happened to me on TWRP. hopefully the developers can fix the source of the problem soon.
What ROM were you running when this happened? I'm trying to narrow down whether its a ROM or recovery issue...or both...
Sent from my Nexus 7 using Tapatalk
MontAlbert said:
Seems that it happens on all recoveries ATM. Happened to me on TWRP. hopefully the developers can fix the source of the problem soon.
What ROM were you running when this happened? I'm trying to narrow down whether its a ROM or recovery issue...or both...
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Had the problem with Mahdi rom and Philz or cwm ... Hope they will fix this soon !
I found this .. Not really perfect :/ http://forum.xda-developers.com/showpost.php?p=54112729&postcount=24
MontAlbert said:
Seems that it happens on all recoveries ATM. Happened to me on TWRP. hopefully the developers can fix the source of the problem soon.
What ROM were you running when this happened? I'm trying to narrow down whether its a ROM or recovery issue...or both...
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I'm on stock CM11S
I'm try to build a lot of rom but all of these bootloop or take a lot of time to start, or data partition unmount itself after a reboot.
No issue using PA version 20140708
So I think there is some issue in the last sources,otherwise if it was a problem of recovery also paranoid should have bootloop.
Now I'm trying to build PA with last sources
what about an update?touch edition?
blade_ said:
what about an update?touch edition?
Click to expand...
Click to collapse
Would be great, I hate TWRP and Philz, too. CWM is sufficient, but this project here looks abandoned
blade_ said:
what about an update?touch edition?
Click to expand...
Click to collapse
I actually hate recovery touch editions! When I had the ghost touches it f*cked up everything in recovery.
wacky.ddw said:
I actually hate recovery touch editions! When I had the ghost touches it f*cked up everything in recovery.
Click to expand...
Click to collapse
no problems in all my phones with touch
Maybe it's me missing something, I downloaded and installed PA 5.1, build from 20th May which I do not think is an Alpha that I would need to factory reset to do an OTA over.
However today OTA popped up with a update to the 28th May build, the upgrade seems to work but the phone then will not boot up instead I get the initial S3 screen twice with a blank screen in between then it drops in to recovery?
Think I am doing the update right i.e. download in OTA app, click install, phone reboots in to recovery runs install, reboots -- then in theory it should boot back up but at this point I have the above loop and back to recovery...
The recovery that I an using is Philz recovery - added it a couple of nights ago to install the original build of 5.1 and Gapps so that seems to work, there no errors with the OTA as its installed, the caches are being cleared first by the install script everything looks fine until the phone tries to boot back up. Have tried it 3 times now downloading a new copy of the OTA each time in case of corruption and restoring from a good backup on each failure.
Any ideas appreciated?
... and thank you in advance
paped said:
Maybe it's me missing something, I downloaded and installed PA 5.1, build from 20th May which I do not think is an Alpha that I would need to factory reset to do an OTA over.
However today OTA popped up with a update to the 28th May build, the upgrade seems to work but the phone then will not boot up instead I get the initial S3 screen twice with a blank screen in between then it drops in to recovery?
Think I am doing the update right i.e. download in OTA app, click install, phone reboots in to recovery runs install, reboots -- then in theory it should boot back up but at this point I have the above loop and back to recovery...
The recovery that I an using is Philz recovery - added it a couple of nights ago to install the original build of 5.1 and Gapps so that seems to work, there no errors with the OTA as its installed, the caches are being cleared first by the install script everything looks fine until the phone tries to boot back up. Have tried it 3 times now downloading a new copy of the OTA each time in case of corruption and restoring from a good backup on each failure.
Any ideas appreciated?
... and thank you in advance
Click to expand...
Click to collapse
Well, i'm on I9300 and all i can tell you is that i have the same exact problem with the same release, so you're not alone.
I was hoping this new release would work since the one of the 20 may didn't, but this one won't even boot.
I guess I9300 doesn't get love anymore...
You are not alone in this. It is happening with me too since the stable build of 28th May. I tried the on on June 12th too ...but even that is failing as well
How come it is a stable build when it has a bug like this and crashes the phone? Are we making a mistake? Does it require a different kernel or what can I do to make it work?!
~ Manthravadi
I'm stuck with this I have tried the last 3 ota updates with CWM, TWRP and Philz recovery all fail as above. Even tried downloading the full versions and doing a clean install with gapps and they fail. Could be a kernel issue but cannot find anything that states a dependency, is the kernel not part of the download like in a Linux OS? As never upgraded a kernel separately, how would you do that, is it another zip file, any ideas where to get it from?
paped said:
I'm stuck with this I have tried the last 3 ota updates with CWM, TWRP and Philz recovery all fail as above. Even tried downloading the full versions and doing a clean install with gapps and they fail. Could be a kernel issue but cannot find anything that states a dependency, is the kernel not part of the download like in a Linux OS? As never upgraded a kernel separately, how would you do that, is it another zip file, any ideas where to get it from?
Click to expand...
Click to collapse
I actually got it working finally a few days back.
You need to install boeffla kernel version 4 alpha 3 in order get the latest pa rom up and running. Go to boeffla-kernel website. In downloads select the device GT-I 9300. You will find CM12.1 NG version which is not yet stable. In that select version 4 alpha 3. Alpha 6 is latest but does not work too :/ Download Alpha 3 .. a .zip file which can be flashed using TWRP or Philz or CWM.
Wipe cache/dalvik-cache → flash boeffla → flash pa latest → flash pa gapps latest for 5.1
~ Manthravadi
Sent from my GT-I9300 using Tapatalk
I also have problem but thankfully when I did the steps above, it did finally boot but now I have another problem. My S3 boots properly and I can use it for a while then after a few mins it suddenly reboots with boot animation and all and I dunno what to do. It just keeps rebooting after a certain amount of mins.
@Aledresin: glad that I was able to help you. I am not experiencing any such issues at the moment. When the next PA build is released, try to flash it with boeffla 4 alpha 6.
Afaik ..some memory issues were fixed in alpha 6 and as you are using alpha 3..perhaps you are experiencing those issues.
~ Manthravadi
Sent from my GT-I9300 using Tapatalk
Manthravadi said:
I actually got it working finally a few days back.
You need to install boeffla kernel version 4 alpha 3 in order get the latest pa rom up and running. Go to boeffla-kernel website. In downloads select the device GT-I 9300. You will find CM12.1 NG version which is not yet stable. In that select version 4 alpha 3. Alpha 6 is latest but does not work too :/ Download Alpha 3 .. a .zip file which can be flashed using TWRP or Philz or CWM.
Wipe cache/dalvik-cache → flash boeffla → flash pa latest → flash pa gapps latest for 5.1
~ Manthravadi
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Do you happen to have a copy/mirror of "boeffla-kernel-4.0-alpha3-CM12.1-NG-i9300.recovery.zip"
I've been searching for a few days and can't find it anywhere. The official boeffla site no longer hosts this file and a lot of i9300 users need it to run the latest Paranoid OTA.
EDIT: Found it! It's available here: http://boeffla.df-kunde.de/sgs3/boef...load/Test/old/
Thanks to user Hawaiihemd for the info.
paped said:
Think I am doing the update right i.e. download in OTA app, click install, phone reboots in to recovery runs install, reboots -- then in theory it should boot back up but at this point I have the above loop and back to recovery...
Click to expand...
Click to collapse
I had a very similar problem and found that if I let it automatically reboot after flashing, then I was stuck just rebooting to recovery. If I manually shut down after flashing and manually booted, then everything worked fine. You may have the same thing happening here. I also used PhilzTouch and like it a lot. Thanks to the devs!