Database Info

Recovery Issue with both CWM and TWRP

I posted this in Q&A, but no replies led me to post here as well.
Hi. I've been using this Xoom for a couple weeks now, and just started having this problem yesterday.
Before I noticed the promblem I was on EOS 3 Wingman. I had TWRP 2.2.2.0 as recovery.
I wanted to give CM10 nightlies a shot. Downloaded the ROM and GAPPS through Goo. I tried to flash the CM10 ROM and GApps zip through the Goo interface. Xoom rebooted and instead of installing, I just got a contantly repeating error saying the install failed.
Eventually I rebooted the xoom and went into recovery. I tried to wipe data and it said it couldn't be mounted. Same error for wiping system, cache, etc...
Rebooted xoom and the EOS 3 rom was still working fine, I downloaded [Recovery] ClockworkMod 3.2.0.0 (R4c) Modded for Internal media [UPDATED 10/6]" and flash via adb. rebooted to recovery and tried wipe. same issue. nothing could be wiped. everything said "failure mounting <applicable partition>".
I tried flahing rogue recovery and got the same thing. I said screw it and rebooted back into EOS and it's been working fine. EOS was updated last night to 143, so i downloaded and tried to install through goo. I got the repeating errors again. Rebooted into recovery and still got the errors where it seems like none of the partitions are writeable.
I WAS able to install the EOS update directly through recovery.
Has anyone ever seen this behavior before and know how to fix it? I can't even export logs in the 2 CWM recoveries because they fail when trying to write the log file.
If I try to install an update through goo, it reboots to recover and just keeps scrolling "An Update Error has occured".
I can reboot to recovery and install the zip from there directly with no issue.
Here is the log for the failed data wipe...
I:mke2fs command: mke2fs -t ext4 -m 0 /dev/block/mmcblk0p10
mke2fs 1.41.12 (17-May-2010)
/dev/block/mmcblk0p10 is apparently in use by the system; will not make a filesystem here!
E:Unable to format data.
* Verifying filesystems...
I:=> Let's update filesystem types via verifyFst aka blkid, command: 'blkid'.
* Verifying partition sizes...
Ievice has /data/media
I:Total used space on /data is: 5122715648
I:Total in /data/media is: 3962468352
I:Actual data used: 1160247296
du: /data/media/.android_secure: No such file or directory|
once in recovery, if I try to format data, it says "Unable to format data". Log

Well I can't help, I'm in the same boat...hoping to get some insight from any responses you might get.

grey.ghost said:
Well I can't help, I'm in the same boat...hoping to get some insight from any responses you might get.
Click to expand...
Click to collapse
It's extremely unusual to get no responses to an issue like these here at XDA. leads me to believe it might be a very uncommon problem. The folks here are usually on the ball about any issue that has even arisen before.
That being said, I am going to try to flash the stock RUU back on from this link...
http://developer.motorola.com/produ...utm_source=supportforums&utm_term=unlockboard
After I finish, I re-root/unlock.
I'll let you know how it goes.

I'll let you know if I come up with something as well. So far I've managed to erase the sd card and maintain a constant boot loop.

Flashing all of the stock img, relocking, and unlocking again didn't do ****.
Found an original MZ600 SBF, which is what I need for verizon 3g xoom, I'm installing this via RSD Lite to see if it blows away whatever is causing the issue.

I was able to wipe the entire system and use adb to repeat the unlock and root steps. So far so good. I'm using the CWM 3.2.0.0 recovery image right now though. I have at least been able to get into a clean copy of a ROM and no bootloops yet. Can't restore data off old Nandroids, so I'm about to update to the newer CWM based recovery image and see if that will help.

I think I'm OK now.
I installed the SBF. Let all of the OTA updates come in including the ICS update where my 3g stops.
flashed the ROGUE recovery from fastboot.
I was able to format all partitions and install and boot CM9 nightly.

Me too, i was sweating hard for a bit, but was able to go through the entire process from stock, unlock, root, rogue recovery and then flashed CNA. Got that working without boot loops or fc and then advance restored data from a previous nandroid through rogue to get it back. A couple of apps had to be redownloaded from the market, but it looks as if I'm back in business. I want to try TWRP, but every time I do something screws up, so I think I'll stop trying.
Thanks for the help.

grey.ghost said:
Me too, i was sweating hard for a bit, but was able to go through the entire process from stock, unlock, root, rogue recovery and then flashed CNA. Got that working without boot loops or fc and then advance restored data from a previous nandroid through rogue to get it back. A couple of apps had to be redownloaded from the market, but it looks as if I'm back in business. I want to try TWRP, but every time I do something screws up, so I think I'll stop trying.
Thanks for the help.
Click to expand...
Click to collapse
Are you installing Twrp from goo manager. Cause I have not had any issues with the goo manager download. But did have issues with the zip file here on xda. I dont kknow if it is worth a try but that is how I did it.
Sent from my Xoom using xda app-developers app

Well sense this is a twrp related issue I would think u would have asked in my thread where I released the port for twrp to Xoom,
Having said that, at one point n time there was a note n the open about open script recovery. But its is also buried in the thread too. So I will answer your question and also presume a few things... and please correct me if I am wrong anywhere.
Once u set the download path in goo app to /data/media/goomanager/ and downloaded a ROM, clicked flash ROM, and entered recovery once u saw all the E/ update error u manually rebooted the Xoom and did not let the script finish installing the ROM? If I am correct that so far. That's what cause your additional problems. You basically rebooted recover while mid install of a ROM.
Now as stated it the twrp thread for Xoom, these errors are false errors and should be ignored. To add it the reassurance that they are intact false errors, from goo app select to flash a ROM again and simple allow the script to finish and then the tablet will reboot on its own when it is finished with the script. And you will be greeted with your new ROM you just successfully flashed.
Again let me know if I am wrong on assuming you forced a reboot mid install ( aka while u saw all the errors)
Sent from my Nexus 7 using Tapatalk 2

runandhide05 said:
Well sense this is a twrp related issue I would think u would have asked in my thread where I released the port for twrp to Xoom,
Having said that, at one point n time there was a note n the open about open script recovery. But its is also buried in the thread too. So I will answer your question and also presume a few things... and please correct me if I am wrong anywhere.
Once u set the download path in goo app to /data/media/goomanager/ and downloaded a ROM, clicked flash ROM, and entered recovery once u saw all the E/ update error u manually rebooted the Xoom and did not let the script finish installing the ROM? If I am correct that so far. That's what cause your additional problems. You basically rebooted recover while mid install of a ROM.
Now as stated it the twrp thread for Xoom, these errors are false errors and should be ignored. To add it the reassurance that they are intact false errors, from goo app select to flash a ROM again and simple allow the script to finish and then the tablet will reboot on its own when it is finished with the script. And you will be greeted with your new ROM you just successfully flashed.
Again let me know if I am wrong on assuming you forced a reboot mid install ( aka while u saw all the errors)
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
No, after pushing the TWRP recovery to the Xoom using adp, I would clean install a ROM and get one of two results....1) the ROM would run for a few seconds and then reboot, or 2) the ROM would run, but everything would fc. Fixing permissions, wiping everything, etc., wouldn't help the issue. No matter what I tried under TWRP, those were the results. I ended up having to start from scratch to negate whatever it was that was making the xoom go funky. Once I pushed rogue and followed the same process, I was back in business.
Sent from my Xoom using Tapatalk 2

[Q] Symlink: some symlink failed...(status 7) installation aborted

Getting this error! Symlink: some symlink failed...(status 7) installation aborted
I've been trying to flash a new rom for a few days and have spent countless hours trying to figure out the issue. I'm trying to flash the KK-Beanstalk 4.4.215 - OC. I flashed an earlier release without an issue. I believe the error I'm getting has to do with the space on my system partition. I've tried all the basic troubleshooting; clean flash- factory reset, formatting system, re downloading the rom, used CWM 6.0.4.3 and Philz custom recovery. I've checked my system partition while running the rom and am using 435/588MB. I assume the wipe/factory reset and system format would take care of that but I'm not so sure.
I am stumped and haven't found this clearly answered on any other forum. I'm out of ideas on what I can try and would not prefer having to move to another rom. I apologize I would have posted this on that thread but I usually don't have to post, I can get away with reading and researching.
Thanks!

dirtycurty said:
Getting this error! Symlink: some symlink failed...(status 7) installation aborted
I've been trying to flash a new rom for a few days and have spent countless hours trying to figure out the issue. I'm trying to flash the KK-Beanstalk 4.4.215 - OC. I flashed an earlier release without an issue. I believe the error I'm getting has to do with the space on my system partition. I've tried all the basic troubleshooting; clean flash- factory reset, formatting system, re downloading the rom, used CWM 6.0.4.3 and Philz custom recovery. I've checked my system partition while running the rom and am using 435/588MB. I assume the wipe/factory reset and system format would take care of that but I'm not so sure.
I am stumped and haven't found this clearly answered on any other forum. I'm out of ideas on what I can try and would not prefer having to move to another rom. I apologize I would have posted this on that thread but I usually don't have to post, I can get away with reading and researching.
Thanks!
Click to expand...
Click to collapse
read this for a clean install http://forum.xda-developers.com/showthread.php?t=2176593
still fails, try cwm 6037 or even twrp 2.6.1.0

I'll try these steps today. I thought there might be something more specific with that error instead of the way I was flashing.

Vanir/Commotio won't flash

So i downloaded a nightly off the [ROM] Vanir/Commotio TF700
and i was trying to flash it on twrp it failed i made sure to wipe and factory reset prior. I put cromni back on without any problems.
It says it can't find md5 file... during the flashing process

Paprika88 said:
So i downloaded a nightly off the [ROM] Vanir/Commotio TF700
and i was trying to flash it on twrp it failed i made sure to wipe and factory reset prior. I put cromni back on without any problems.
It says it can't find md5 file... during the flashing process
Click to expand...
Click to collapse
Snag the recovery.log after the flash and it will provide more info.

here's my log
its attached
I'm trying out all the roms i can until i land one that might fix my wifi reception.
Anyways i'm also trying crombi-kk.. and I'm having trouble with this step. its asking me to fix root and then won't boot when i flash it...
(this is coming from cromi x
I can't find the root sub section after i open developer options.
1. Enable developer options by clicking the build number 7 times in settings - about tablet
2. Go to developer settings
3. In the first section click Root access and change to Apps and ADB
I'm also asked to fix permissions after I flash Commotio

Paprika88 said:
here's my log
its attached
I'm trying out all the roms i can until i land one that might fix my wifi reception.
Anyways i'm also trying crombi-kk.. and I'm having trouble with this step. its asking me to fix root and then won't boot when i flash it...
(this is coming from cromi x
I can't find the root sub section after i open developer options.
1. Enable developer options by clicking the build number 7 times in settings - about tablet
2. Go to developer settings
3. In the first section click Root access and change to Apps and ADB
I'm also asked to fix permissions after I flash Commotio
Click to expand...
Click to collapse
You need to update your TWRP version - please move to TWRP 2.7.1.1
This is why the rom is failing to flash:
Code:
ApplyParsedPerms: removexattr of /system/addon.d/50-vanir.sh to 0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
It's either a bug in the installer or related to the older TWRP - I suspect the latter.

Thanks!
I installed twrp 7.2.1.1 and it flashed successfully. however now i rebooted it and I see commotion with a picture of the ocean and sunset looping.
the booting screen i presume. I figured it was just loading everything up but it's been like this for 20 minutes now...
i'll try crombi kitkat
Edit: K nevermind I flashed the gapps and it worked
It loaded and I received a warning message:
UIDS on the system are inconsistent you need to wipe your data partition or your device will be unstable... with a i'm feeling lucky button.
I'll try factory wipe
it worked

Paprika88 said:
Thanks!
I installed twrp 7.2.1.1 and it flashed successfully. however now i rebooted it and I see commotion with a picture of the ocean and sunset looping.
the booting screen i presume. I figured it was just loading everything up but it's been like this for 20 minutes now...
i'll try crombi kitkat
Edit: K nevermind I flashed the gapps and it worked
It loaded and I received a warning message:
UIDS on the system are inconsistent you need to wipe your data partition or your device will be unstable... with a i'm feeling lucky button.
I'll try factory wipe
it worked
Click to expand...
Click to collapse
Glad you got it working.
For future reference: Whenever you move from one rom to another you have to perform a factory wipe in recovery. Preferably before you flash the rom. Saves you a lot of headache

Phone Stuck on 1+ Logo wont boot HELP

Ok was trying to install a ROM and got an error that there was no OS installed and now the phone wont boot up
I rooted it via Bacon root toolkit and I took a back up before I rooted but I cannot get it to reboot. The back up is saved on the PC and phone not getting picked up by PC
Anyone tried to restore android back up file and went to ab file on pc but it wont load. Can go into fastboot and recovery but not showing on PC
HELP

Delete duplicate post

This is why you shouldn't use toolkits, you have no access to fastboot and no idea how to fix it. What drivers are installed on your PC? I guess it doesn't matter, my advice is to completely delete anything that the toolkit installed and start fresh. Go to my guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
I have links to the Android SDK (which contains adb/fastboot) and the right drivers for this phone. Make sure you reboot your PC after deleting everything, then install the SDK and the drivers, reboot PC again, connect phone.
Transmitted via Bacon

timmaaa said:
This is why you shouldn't use toolkits, you have no access to fastboot and no idea how to fix it. What drivers are installed on your PC? I guess it doesn't matter, my advice is to completely delete anything that the toolkit installed and start fresh. Go to my guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
I have links to the Android SDK (which contains adb/fastboot) and the right drivers for this phone. Make sure you reboot your PC after deleting everything, then install the SDK and the drivers, reboot PC again, connect phone.
Transmitted via Bacon
Click to expand...
Click to collapse
Live and Learn and got back to the stock using adb/fastboot and installing images and back to normal again. I want to update to Lollilop and Sabermod but after trying may just stick with Stock for a while as I kept getting errors when trying to load the ROM??
Thanks

funkyirishman said:
Live and Learn and got back to the stock using adb/fastboot and installing images and back to normal again. I want to update to Lollilop and Sabermod but after trying may just stick with Stock for a while as I kept getting errors when trying to load the ROM??
Thanks
Click to expand...
Click to collapse
Exactly what error are you getting when trying to flash? Are you checking the md5 when you download? What recovery are you using?
Transmitted via Bacon

timmaaa said:
Exactly what error are you getting when trying to flash? Are you checking the md5 when you download? What recovery are you using?
Transmitted via Bacon
Click to expand...
Click to collapse
When I tried to flash initially I got the below
Went into recovery and did Factory reset and then wipe cache partition. Then tried Apply update and scrolled to the ROM file and apply update and I get the below error
Install Failed
Finding Update Package
Opening Update Package
Verifying Update Package
E: Failed to verify whole-file signature
E:signature verification failed
Installation aborted
I have the files saved in the download folder.
Then when I tried to install with TWRP rather than update I clear cache, dalvik and system and tried to load and got the below error
Checking for MD5 File
Skipping MD5 Chekck: no MD5 file found
Comparing TZ Verionsioj TZ. BF.2.0-2.0.0109 to TZ
BF 2.0-2.0.0096
assert failed oppo verify trustzone
I got the message that no os installed and I could not reboot so I flashed it back to stock using the below
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Phone now rooted and unlocked and like to update but afraid I will just experience it all over again:crying:
Any help appreciated
Thanks

funkyirishman said:
When I tried to flash initially I got the below
Went into recovery and did Factory reset and then wipe cache partition. Then tried Apply update and scrolled to the ROM file and apply update and I get the below error
Install Failed
Finding Update Package
Opening Update Package
Verifying Update Package
E: Failed to verify whole-file signature
E:signature verification failed
Installation aborted
Click to expand...
Click to collapse
Ok, you got this error because you're trying to flash a custom ROM with the stock recovery. The stock recovery can only flash zips signed by CM (official updates)
funkyirishman said:
Then when I tried to install with TWRP rather than update I clear cache, dalvik and system and tried to load and got the below error
Checking for MD5 File
Skipping MD5 Chekck: no MD5 file found
Comparing TZ Verionsioj TZ. BF.2.0-2.0.0109 to TZ
BF 2.0-2.0.0096
assert failed oppo verify trustzone
I got the message that no os installed and I could not reboot so I flashed it back to stock using the below
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Phone now rooted and unlocked and like to update but afraid I will just experience it all over again:crying:
Any help appreciated
Thanks
Click to expand...
Click to collapse
Your problem here is that you're trying to install a ROM but you don't have the correct firmware installed. When flashing a Lollipop ROM for the first time you need to first flash Lollipop firmware and Lollipop modem. Once you've flashed those they're always there so you don't need to do it again. The only reason you'd need to flash firmware and modem again would be if you wanted to return to a KitKat ROM, and then it'd be KitKat firmware and modem that you'd need to flash. Anyway, you'll find the modems here:
http://boeffla.df-kunde.de/bacon/modems
And I mirror the firmwares here:
https://drive.google.com/folder/d/0B98G0KTJwnBFRGhZeUNpMEI4ajg/edit
PS. I also noticed you weren't wiping properly before attempting to install the ROM. When flashing a ROM you need to perform a full wipe, this includes system, data, cache, and dalvik cache. This didn't cause the problem you experienced, but had the install succeeded you would have had other problems.
It might benefit you to read the OnePlus One FAQ thread:
http://forum.xda-developers.com/oneplus-one/help/faq-oneplus-one-frequently-questions-t2895136
And my guide thread:
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon

timmaaa said:
Ok, you got this error because you're trying to flash a custom ROM with the stock recovery. The stock recovery can only flash zips signed by CM (official updates)
Your problem here is that you're trying to install a ROM but you don't have the correct firmware installed. When flashing a Lollipop ROM for the first time you need to first flash Lollipop firmware and Lollipop modem. Once you've flashed those they're always there so you don't need to do it again. The only reason you'd need to flash firmware and modem again would be if you wanted to return to a KitKat ROM, and then it'd be KitKat firmware and modem that you'd need to flash. Anyway, you'll find the modems here:
http://boeffla.df-kunde.de/bacon/modems
And I mirror the firmwares here:
https://drive.google.com/folder/d/0B98G0KTJwnBFRGhZeUNpMEI4ajg/edit
PS. I also noticed you weren't wiping properly before attempting to install the ROM. When flashing a ROM you need to perform a full wipe, this includes system, data, cache, and dalvik cache. This didn't cause the problem you experienced, but had the install succeeded you would have had other problems.
It might benefit you to read the OnePlus One FAQ thread:
http://forum.xda-developers.com/oneplus-one/help/faq-oneplus-one-frequently-questions-t2895136
And my guide thread:
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
Click to expand...
Click to collapse
Cheers thanks for that. I thought the ROM updated the firmware and modems so that's a lesson learned
So I download the modem and firmware and copy these into the download folder on the phone and install via TWRP recovery correct? Modem first then firmware? This will then put lollipop on the phone correct?
Then if I want to install a new ROM I need to do a full wipe. I just did not see that option and was just following the video tutorial associated with the Sabermod thread by wiping cache system and dalvik
Read your thread and will be doing a full nandroid & EFS back up prior to do any of the above
Thanks again

funkyirishman said:
Cheers thanks for that. I thought the ROM updated the firmware and modems so that's a lesson learned
Click to expand...
Click to collapse
CM12 does do that, but no other ROMs do.
funkyirishman said:
So I download the modem and firmware and copy these into the download folder on the phone and install via TWRP recovery correct? Modem first then firmware? This will then put lollipop on the phone correct?
Click to expand...
Click to collapse
Yes, install via TWRP recovery. It doesn't matter which order you flash them in. So install both, then go to the reboot menu, and select to reboot back to the recovery. This doesn't install Lollipop as such, this installs Lollipop compatible firmware.
funkyirishman said:
Then if I want to install a new ROM I need to do a full wipe. I just did not see that option and was just following the video tutorial associated with the Sabermod thread by wiping cache system and dalvik
Click to expand...
Click to collapse
Go to the wipe menu in TWRP, then select advanced wipe, from there you can choose which partitions you want to wipe (system, data, cache, dalvik cache), just don't wipe internal storage (that's your virtual sd card).
funkyirishman said:
Read your thread and will be doing a full nandroid & EFS back up prior to do any of the above
Thanks again
Click to expand...
Click to collapse
Very good, that's super important. It doesn't happen often, but sometimes the EFS partition will just randomly become corrupt, if you don't have a backup in that situation your phone is useless (you can't use someone else's EFS backup because it contains unique device identifiers).
Transmitted via Bacon

timmaaa said:
CM12 does do that, but no other ROMs do.
Yes, install via TWRP recovery. It doesn't matter which order you flash them in. So install both, then go to the reboot menu, and select to reboot back to the recovery. This doesn't install Lollipop as such, this installs Lollipop compatible firmware.
Go to the wipe menu in TWRP, then select advanced wipe, from there you can choose which partitions you want to wipe (system, data, cache, dalvik cache), just don't wipe internal storage (that's your virtual sd card).
Very good, that's super important. It doesn't happen often, but sometimes the EFS partition will just randomly become corrupt, if you don't have a backup in that situation your phone is useless (you can't use someone else's EFS backup because it contains unique device identifiers).
Transmitted via Bacon
Click to expand...
Click to collapse
Reading about back ups etc on the below when creating a recovery
-Make sure you check the md5 to verify its integrity.
How and what do you check?
Also I first do the back up. Then install the firmware and modems and then update the ROM.
I dont need to flash the stock kernal or fastboot images, correct?
Also doing a back up does it back it up to an internal SD Card or should I keep it on PC
Cheers

funkyirishman said:
Reading about back ups etc on the below when creating a recovery
-Make sure you check the md5 to verify its integrity.
How and what do you check?
Also I first do the back up. Then install the firmware and modems and then update the ROM.
I dont need to flash the stock kernal or fastboot images, correct?
Also doing a back up does it back it up to an internal SD Card or should I keep it on PC
Cheers
Click to expand...
Click to collapse
The download page for a ROM or kernel usually lists the md5 checksum for that particular file. An md5 is like a digital fingerprint of the file, so once you've downloaded it you use an md5 checking app/program to confirm that the md5 of the downloaded file matches the md5 listed on the download page. This confirms that the file hasn't become corrupt during the download, if even a single byte of information is corrupt in a file the md5 will be drastically different.
You don't need to flash the stock kernel or stock images, the numbered parts in my guide aren't steps, they're sections.
When you create your nandroid backup using TWRP it will automatically be saved to your internal storage. You should keep at least one backup on your phone at all times, think of it as an insurance policy just in case something goes wrong, you'l always have a known working OS there to save you. You should also copy it to your PC for safe keeping.

timmaaa said:
The download page for a ROM or kernel usually lists the md5 checksum for that particular file. An md5 is like a digital fingerprint of the file, so once you've downloaded it you use an md5 checking app/program to confirm that the md5 of the downloaded file matches the md5 listed on the download page. This confirms that the file hasn't become corrupt during the download, if even a single byte of information is corrupt in a file the md5 will be drastically different.
You don't need to flash the stock kernel or stock images, the numbered parts in my guide aren't steps, they're sections.
When you create your nandroid backup using TWRP it will automatically be saved to your internal storage. You should keep at least one backup on your phone at all times, think of it as an insurance policy just in case something goes wrong, you'l always have a known working OS there to save you. You should also copy it to your PC for safe keeping.
Click to expand...
Click to collapse
Perfect I will google an md5 checking app/program so for the Sabermod I need to check on the download page on their link below
http://forum.xda-developers.com/oneplus-one/development/rom-kernel-sabermod-cm-11-0-t2880407
Just checked their download link is not working but I downloaded the ROM to my PC previously and its in zip format can you check the MD5 v this?
Thanks

funkyirishman said:
Perfect I will google an md5 checking app/program so for the Sabermod I need to check on the download page on their link below
http://forum.xda-developers.com/oneplus-one/development/rom-kernel-sabermod-cm-11-0-t2880407
Just checked their download link is not working but I downloaded the ROM to my PC previously and its in zip format can you check the MD5 v this?
Thanks
Click to expand...
Click to collapse
You have nothing to check it against though.
Transmitted via Bacon

timmaaa said:
You have nothing to check it against though.
Transmitted via Bacon
Click to expand...
Click to collapse
Ok so the ROM I downloaded is called cm-12-20150324-ROBBIEL811-UBER4.8-bacon and is in zip format and the download link on the developers page is dead so I cannot check the md5 file?
Thanks

funkyirishman said:
Ok so the ROM I downloaded is called cm-12-20150324-ROBBIEL811-UBER4.8-bacon and is in zip format and the download link on the developers page is dead so I cannot check the md5 file?
Thanks
Click to expand...
Click to collapse
Well yeah, if you can't reach the download page there's no way to see what the md5 is. Not all download pages have it anyway, they should, but not all do.
Transmitted via Bacon

TWRP infinitely installs a ROM

I didn't know where to post this so i am posting it here.
I tried to flash the latest version of CrDroid some hours ago and although the installation began with no errors, the whole thing got stuck on an infinite installation of the ROM. The log displayed "Patching system image unconditionaly."
After about 30 minutes i just lost faith and held down power button to force a reboot. Then, TWRP got reset to the screen which you see when you first flash TWRP, the one ascing about wether to keep system read only or not.
I will post screenshots too as soon as i figure out how to do it
.

Set it back to RW mode from RO mode. If it constantly turns back to RO, try reflashing the recovery image.
If you are lucky enough to abruptly abort a ROM installation, you will be able to atleast use the device. I had aborted a nandroid restore and my entire data partition was corrupted.
In any case you should post it in the appropriate ROM thread.

Make sure system is mounted writable, wipe system, data, and caches, and flash... it's that simple. If it fails use another ROM.
BTW, it is usually useful to tell which device (specifically), what ROM/Gapps, what version of TWRP, etc... the devil is usually in the details, the more the better.

Yeah i forgot about that, im new here. So, its the latest version of TWRP and the ROM was the latest version of crDroid (April 17th). Anyways, me being extremely stubborn as usual, I tried flashing the ROM through FlashFire and the problem is still there. By the way I did mount everything and it doesnt get better. I dont care anyways i'll just return to some other Nougat ROM. Thanks for replying though!

mike.... said:
Yeah i forgot about that, im new here. So, its the latest version of TWRP and the ROM was the latest version of crDroid (April 17th). Anyways, me being extremely stubborn as usual, I tried flashing the ROM through FlashFire and the problem is still there. By the way I did mount everything and it doesnt get better. I dont care anyways i'll just return to some other Nougat ROM. Thanks for replying though!
Click to expand...
Click to collapse
Weird... We can pretty much guarantee nothing is working in TWRP though, or at least it's not processing even the boot image of your ROM or the device wouldn't boot.
What is bootloader status?