Hello, I am trying to flash Chroma rom for my Verizon Nexus 6 but it boots back to the twrp home screen and does not flash the rom. I wipe the phone and the dalvik cache and all that. I was running Blisspop which encrypted my phone I believe. I wiped the phone and tried to flash Chroma and it would just reboot to the twrp home screen. I restored my nandroid backup of my stock rom still being rooted and it still will not flash. Have tried other roms and the only rom it would flash is blisspop. I am currently on the stock rom with franco kernel. Anybody know what is causing the issue? Thanks in advanced.
manofsteel718 said:
Hello, I am trying to flash Chroma rom for my Verizon Nexus 6 but it boots back to the twrp home screen and does not flash the rom. I wipe the phone and the dalvik cache and all that. I was running Blisspop which encrypted my phone I believe. I wiped the phone and tried to flash Chroma and it would just reboot to the twrp home screen. I restored my nandroid backup of my stock rom still being rooted and it still will not flash. Have tried other roms and the only rom it would flash is blisspop. I am currently on the stock rom with franco kernel. Anybody know what is causing the issue? Thanks in advanced.
Click to expand...
Click to collapse
Make sue you have the latest version of TWRP (2.8.6.0) ALso try redownloading the ROM, may you have a bad download?
Are you also wiping system doing a full wipe coming from another rom
Yes, I have the latest version of TWRP. I will try redownloading the ROM. And yes I am wiping the system before trying to flash.
Related
Greetings fellowmen!!
Recently i thought of rooting my nexus 1. So i did some research and found out that the easiest way to do it was by unlocking the bootloader installing a custom recovery (I did Amon Ra) and then wiping the data\factory settings and flashing the cm 7.1 zip. So i did all the above and there you go....I had an n1 running cm 7.1 smoothly but then after a few hours it starts to piss me of. The problem is that whenever i lock the homescreen with the power button and wake it up again it just displays the main homescreen and does nothing i cannot navigate to the left or right homescreen cannot open app drawer in short it just hung up there doing nothing. I had to take out the battery atleast 15 times. I rebooted my device and it kept on giving me the same problem.
So then i reflashed cm 7.1 by wiping the data and factory settings and installing it again. But still it gave me the same problem. So then i thought of flashing 7.0.3 version instead and surprisingly that works like a charm. So is it the mod thats buggy or is it my phone.
One more question. I have the stock 2.3.4 gingerbread rom which i got from here!!
Code:
http://forum.xda-developers.com/showthread.php?t=1061648
This one in particular-
GRK39F OTA (stock vanilla - odexed, unrooted):
MD5: 35C8B4B9FD22DD4CA19C5D026E74411D
So to install this rom do i have to install it the same way i did cm by wiping data/factory settings and then installing flash from zip or is there any other way to do it ?
Thanks in advance for taking out valuable time and reading my long problem!!
I am running the latest version of CM 7.1 that was released within the last week or so without any issues. Got it from here. http://download.cyanogenmod.com/?type=stable&device=passion
Before that I was running the RC for 7.1. One thing to try it wiping multiple times before flashing. I assume you are running Amon RA 2.2.1, which is the latest. I have never had a problem with that recovery, however I flashed my ROM with this recovery. So far I think I like it better than Clockwork and Amon.
http://forum.xda-developers.com/showthread.php?t=1291970
As for installing other ROMs yes you do flash them the same way you flashed CM.
So are you saying that it was the recovery that was causing the problem?
Yes I am using the latest Amon Ra 2.2.1 version.
I also got the rom from that link.
And can you explain whats the difference between all these recoveries?
Thanks for replying!
I am not saying it is the recovery, I highly doubt that is the problem. I was just comparing differences. There does not seem to be much difference in the recoveries for what you are trying to do. The recovery I am running is a fairly new one that I just wanted to test out. I do think I like it better than the others.
First thing I would do is wipe 3, 4 or 5 times before flashing. I have had rare occasions where a single wipe would not do it for me. Also have you verified the Checksum of the CM download? Does recovery say it installed successfully? I have also had error installing a ROM in recovery but then had the phone still load the ROM.
Yes i did check the md5 checksums and they match perfectly. Though i did wipe it out only one time so maybe that could be the problem. I think i should get clockworkmod and wipe it through that and then flash cm 7.1. Amon RA doesnt really give us the option of wiping the system partition. right?
Correct Amon Ra does not have an option to format system partition. It's recommend you also wipe system when coming from a different ROM.
Try this file by temasek's, format-signed.zip
http://www.mediafire.com/?8vbd13b440coxx6
just flash it in recovery and it will clean everything, now you can flash CM7.1 again
Are you sure you can't wipe the system with Amon? I remember having that option, but it's been several months since I have used that recovery. Kind of makes me want to flash it to find out.
Before flashing a different ROM I always wipe system, cache and dalvik cache. It is definitely important to wipe the system before flashing a new ROM. I'm sure that is where your problem lies.
No, ClockworkMod has it, but Amon_RA doesn't. Supposedly it is in the works for the next version, but that was a long time ago when I heard that (probably back when v3 for clockworkmod came out).
I did a nandroid backup and flashed the format zip file and then flashed cm 7.1 and its giving me the same problem!!
I had to restore and go back to 7.0.3
Why is this happening
Edit: I also wiped the dalvik cache and factory reset it also but still it just freezes!!
Any advise?
Have you tried downloading the file again maybe form another location I doubt this is the problem but sometimes it's something you don't expect.
You could try from here http://wiki.cyanogenmod.com/index.php?title=Latest_Version
But how does it matter I checked the md5 checksum and it matches!!
Why not stay on CM7.0.3 theres not much difference between the 2
if you dont want to i suggest to try to flash Clockwork recovery and do a full wipe then reflash CM7.1
But still I want to see how 7.1 is!
The main point here is to upgrade and not taking the alternative of staying at the older version!
Please guys any help would be appreciated!!
Doesn't CM7 need clockworkmod 3.x?? Try to flash CWM3.x over Amon if you can get your hands on the flashable zip or if you can get into a working rom, use romManager to switch from amon.
thealphamale05 said:
Doesn't CM7 need clockworkmod 3.x?? Try to flash CWM3.x over Amon if you can get your hands on the flashable zip or if you can get into a working rom, use romManager to switch from amon.
Click to expand...
Click to collapse
Make no different if you use amon Ra or CWM. I would definitely stay away from cwm 3.x or higher if you're using sd-ext
Looks like Ill have to stay with 7.0.3 there doesnt seem to be a solution!!
This is the second time happening. The first time I came from the previously supported Viper One Rom version from sprint, and when I flashed 5.8 I lose my recovery and just get stuck into bootloader. The second time I was coming from the recent Dirty Unicorns Rom, and the same thing happened. I'm currently using the latest Philz Recovery, and I did wipe my phone numerous times before flashing. Am I installing the wrong file? or Am I doing something else wrong? Also the only way it seems to come back from flashing the rom is using an RUU to get me back to stock. Flashing another ROM after ViperOne failing puts me in a bootloop.
zasuncion said:
This is the second time happening. The first time I came from the previously supported Viper One Rom version from sprint, and when I flashed 5.8 I lose my recovery and just get stuck into bootloader. The second time I was coming from the recent Dirty Unicorns Rom, and the same thing happened. I'm currently using the latest Philz Recovery, and I did wipe my phone numerous times before flashing. Am I installing the wrong file? or Am I doing something else wrong? Also the only way it seems to come back from flashing the rom is using an RUU to get me back to stock. Flashing another ROM after ViperOne failing puts me in a bootloop.
Click to expand...
Click to collapse
... try flashing ViperOne with TWRP 2.6.3.0 at least. i think this is going to solve your problem ...
That's really weird.
I've flashed stock to insertcoin to viper 5.7 to viper 5.8 then to bad seeds sense six. I now go back and fourth between viper and sense six no problems at all.
I've only used twrp though, used 2.6 all the way to the newest 2.7.0.4 I believe it is.
What I do when I switch is:
Nandroid*optional*
Flash superwipe for twrp2*so it wipes clean the Rom*
Restore a previous nandroid*viper, stock, etc*
Clear cache and davlik cache.
Reboot.
That's all I do.
I stopped using cwm a while ago with my DINC, my power button was shot*couldn't press it cause it was damaged* at that time twrp had a touch based recovery*2.3.x I believe*, so been using twrp since then.
I have a nexus 6 running cm 12 which function perfectly well.
the device is unable to install the latest cm12 nightly.
It got downloaded completely and is ready to install but when I reboot the phone to install the latest nightly, it takes me to TWRP recovery.
I dont know why this is happening.
Can anybody please help me?
If you need any more information to solve the issue, let me know
I never do custom ROM OTA's, but don't you flash the nightly manually? If you're dirty flashing just wipe cache/dalvik and install the nightly
joshm.1219 said:
I never do custom ROM OTA's, but don't you flash the nightly manually? If you're dirty flashing just wipe cache/dalvik and install the nightly
Click to expand...
Click to collapse
I always thought that I have to factory reset my device each time I need to flash a ROM.
Can I download the nightly update and flash it manually from recovery without factory resetting my device?
gautamperi said:
I always thought that I have to factory reset my device each time I need to flash a ROM.
Can I download the nightly update and flash it manually from recovery without factory resetting my device?
Click to expand...
Click to collapse
yes. if just updating a rom, you never have to factory reset, only when flashing a new different rom. and you dont ever have to wipe dalvik/art or cache, as when you flash the rom they automatically get wiped. so download the latest cm via your browser, boot into your recovery, then flash it in your recovery.
This is what I see when I tried to flash the downloaded nightly build from the cmupdator folder
simms22 said:
yes. if just updating a rom, you never have to factory reset, only when flashing a new different rom. and you dont ever have to wipe dalvik/art or cache, as when you flash the rom they automatically get wiped. so download the latest cm via your browser, boot into your recovery, then flash it in your recovery.
Click to expand...
Click to collapse
I will download the latest build on my browser and do what you have said.
I think now I am understanding this better:good:
I just updated my bootloader and whenever i try to flash a rom, the booting process takes forever until i wipe my phone myself. But when i flash Andro X rom than it takes max. 3min to boot and then it works.
But i want another rom, how do i fix this?
Do you mean that when u flash lollipop based rom it gets bootloop? if yes then first flash stock lollipop firmware and then try flashing other rom. I mostly wipe my internal storage when going from Kitkat to lollipop it works for me.
Well Firstly Explain your problem clearly (I didnt quite understand it)
OK so here's my solution from what I understood..
1. Restore your stock rom Backup from recovery. Boot it once.
2. Now clean flash (Wipe System, Data , Cache, Dalvik cache) a lollipop based Rom (preferably try to clean flash cm 12.1 build)
3. Dont flash Gapps. First see if your phone boots up properly.
4. Configure data and reboot to recovery and flash Gapps.
If you dont have a Stock backup, Then download Stock Firmware images from gregor's thread and install via fastboot. Then follow from step2.
Hope this helps you.
Haroun16 said:
I just updated my bootloader and whenever i try to flash a rom, the booting process takes forever until i wipe my phone myself. But when i flash Andro X rom than it takes max. 3min to boot and then it works.
But i want another rom, how do i fix this?
Click to expand...
Click to collapse
Use easy installer first and get stock lollipop then u can simply root and install recovery then try roms?
sagar846 said:
Well Firstly Explain your problem clearly (I didnt quite understand it)
OK so here's my solution from what I understood..
1. Restore your stock rom Backup from recovery. Boot it once.
2. Now clean flash (Wipe System, Data , Cache, Dalvik cache) a lollipop based Rom (preferably try to clean flash cm 12.1 build)
3. Dont flash Gapps. First see if your phone boots up properly.
4. Configure data and reboot to recovery and flash Gapps.
If you dont have a Stock backup, Then download Stock Firmware images from gregor's thread and install via fastboot. Then follow from step2.
Hope this helps you.
Click to expand...
Click to collapse
My problem is that when i try to flash roms like CM12, Blisspop it doesn't stop booting, it was taking more than an hour so i shutdown my phone and when i flashed Andro X the booting took around 3mins.
So can anyone explain in easy steps how to fix this?
OK now I understand what your problem is. Give me your full specs (like which Model and and stuff). But if you follow what I said above it might fix your problem.
sagar846 said:
OK now I understand what your problem is. Give me your full specs (like which Model and and stuff). But if you follow what I said above it might fix your problem.
Click to expand...
Click to collapse
I got the XT1068
Haroun16 said:
I got the XT1068
Click to expand...
Click to collapse
are you fully wiping cache and userdata (factory reset) because this is most common problem moving between Roms that causes bootloops and why I include factory reset in my easy installer.
you can only dirty flash when going up (upgrading) the same rom - changing roms or downgrading nearly always causes bootloop / hang.
what i'm trying to do is installing lollipop on my s advance
i was coming from CM11 by epirex, and i decided to try his SlimLP; did all the wipes, flashed rom and gapps with no error at all, and then the phone endlessly rebooted into TWRP
so i did a deep clean installing jb with odin; then rooted, installed cwm, flashed MaxiCM this time without gapps and... again the phone only boots into recovery.
what can i do? can this mean that my phone is dying?
TheSteve87 said:
what i'm trying to do is installing lollipop on my s advance
i was coming from CM11 by epirex, and i decided to try his SlimLP; did all the wipes, flashed rom and gapps with no error at all, and then the phone endlessly rebooted into TWRP
so i did a deep clean installing jb with odin; then rooted, installed cwm, flashed MaxiCM this time without gapps and... again the phone only boots into recovery.
what can i do? can this mean that my phone is dying?
Click to expand...
Click to collapse
Try to flash roms kernel after flashing the zip
madkita said:
Try to flash roms kernel after flashing the zip
Click to expand...
Click to collapse
how do i make it in a flashable zip?
TheSteve87 said:
how do i make it in a flashable zip?
Click to expand...
Click to collapse
Extract the roms zip your will find boot.img
After installing the rom install the kernel
just tried, no errors flashing, still stuck in recovery
TheSteve87 said:
just tried, no errors flashing, still stuck in recovery
Click to expand...
Click to collapse
Try to write every thing including SD card
Wipe data, system, cache, dalvik cache and preload. I had same problem and it disapeared after i have wiped preload partition.
i wiped every single thing i could select included android secure, flashed the kernel afterwards and i'm still stuck in TWRP every time i reboot...
TheSteve87 said:
i wiped every single thing i could select included android secure, flashed the kernel afterwards and i'm still stuck in TWRP every time i reboot...
Click to expand...
Click to collapse
Flash stock with original bit file
madkita said:
Flash stock with original bit file
Click to expand...
Click to collapse
already done twice... i'm trying again
ok i finally got SlimLP to boot :crying: i had to flash the rom's kernel on JB and then rom+gapps, everything seems fine
thank you @madkita and @emirm990 for the suggestions
Hi. I have same problem as TheSteve87 but i try all options also this one which author of topic fixed it but for me nothing work. Help me pls.
Edit: I want too install SlimLP.
TheSteve87 said:
what i'm trying to do is installing lollipop on my s advance
i was coming from CM11 by epirex, and i decided to try his SlimLP; did all the wipes, flashed rom and gapps with no error at all, and then the phone endlessly rebooted into TWRP
so i did a deep clean installing jb with odin; then rooted, installed cwm, flashed MaxiCM this time without gapps and... again the phone only boots into recovery.
what can i do? can this mean that my phone is dying?
Click to expand...
Click to collapse
Even I had the same problem . to fix this go back to stock jb using Odin then root then flash a ROM whose android version is 4.4.2[no need to install gapps] then flash the lollipop ROM it will boot up fine
Sent from my GT-I9070 using XDA-Developers mobile app