[Q] Status 7 error, CWM 6.0.1.2 - AT&T Samsung Galaxy S II Skyrocket SGH-I727

I'm trying to flash CM9 or 10, or really any update to what I have now. I'm rooted (verified in titanium backup pro), am on some ICS (It's been months and I don't remember, not stock). I'm running clockworkmod recovery touch 6.0.1.2.
I keep getting "status 7" error messages when I try to install the cyanogen mod zips. I've tried the latest stable release of 9, and a nightly of 10. I've done the recommended formatting/wipes from team chopstick's page, also tried wiping davlik. I had previously tried the wiping everything three times, that also did not work. The radio/modem installs fine, but I always get the status 7 when I try installing a different rom zip via CWM recovery.
In googling status 7, I came across several suggestions (for other phone models) that updating CWM should help, but Vincom's sticky suggests I should not update CWM.
I know I did update CWM following advice from here, I initially didn't have touch recovery, but that was months ago and I can't find the instructions to update to the latest CWM.
I'd also like to verify that status 7 can be solved by updating CWM before actually doing it. And what the heck is status 7 anyway?
Apologies in advance, I keep forgetting what I've read, as it's been months since I last did surgery on my phone.

Could be because of a md5 mismatch, check that first. Otherwise, time to upgrade cwm. Personally, i'd upgrade to the latest anyway.

I did check the MD5 sums and they matched.
I'm a little nervous about upgrading CWM since again, vincom's post says not to. I'm pretty sure last time I just ran the zip from inside CWM 4 or so, is that safe to do this time?

interkin3tic said:
I'm trying to flash CM9 or 10, or really any update to what I have now. I'm rooted (verified in titanium backup pro), am on some ICS (It's been months and I don't remember, not stock). I'm running clockworkmod recovery touch 6.0.1.2.
I keep getting "status 7" error messages when I try to install the cyanogen mod zips. I've tried the latest stable release of 9, and a nightly of 10. I've done the recommended formatting/wipes from team chopstick's page, also tried wiping davlik. I had previously tried the wiping everything three times, that also did not work. The radio/modem installs fine, but I always get the status 7 when I try installing a different rom zip via CWM recovery.
In googling status 7, I came across several suggestions (for other phone models) that updating CWM should help, but Vincom's sticky suggests I should not update CWM.
I know I did update CWM following advice from here, I initially didn't have touch recovery, but that was months ago and I can't find the instructions to update to the latest CWM.
I'd also like to verify that status 7 can be solved by updating CWM before actually doing it. And what the heck is status 7 anyway?
Apologies in advance, I keep forgetting what I've read, as it's been months since I last did surgery on my phone.
Click to expand...
Click to collapse
my sticky states not to use rom manager to update cwm, but its ok to update sk8's cwm from his op

Status 7 is md5 mismatch. Try downloading the rom again. And yes, use sk8's recovery rather than rom manager.
Sent from my CvD Nibbled Skyrocket
Quando Omni Flunkus Moritati

Apologies, I found that information eventually, updated via CWM, and was able to install cm9

Related

[Q] xt926 CM10.2 Stuck on Boot Logo After 1st Reboot

xt926 with unlocked bootloader and can run 10.1 nightly from get.cm with no problem. However, when I install a 10.2 nightly - whether from get.cm, epinter, dhacker or skrilaz - even though the initial boot comes up clean, rebooting after the initial boot gets stuck on the boot logo.
I have tried different recovery images - cwm, twrp, oudhs - and different versions of each.
I have tried clean installs, full formats and dirty upgrades from 10.1.
I have tried multiple force boots from this state (power+vol up).
I have tried with and without the updated gapps and UPDATE-SuperSU-v1.51.zip.
Restoring from backup does not get past this hang. The only way out is to revert to stock (I use mattlegroff's DROID_RAZR_HD_Utility_1.21).
Does anyone have any idea how I might get past this or even get a log?
Only thing that fixed this for me was to flash back to stock 4.1.2, flash newest CWM touch recovery, then flash newest nightly, Gapps, and SU. Then, a popup comes up saying something about the ROM wants to flash your boot image, and asks if you'd like to fix this. I answered YES (fix) and been working since.
Any chance you could link where you got your recovery and SU?
Much appreciated.
Same issue here...
I've also tried everything listed above. I've done everything i can possibly think of to get cm 10.2 on my xt926. For some reason my phone just isn't making it after the first reboot. I've searched and found similar issues but none of the troubleshooting has been working for me. I hope to find a way around this. I need that 10.2!
Same issue here. Not just CM, every 4.3 based ROM I've tried has either failed to boot or failed to boot more than once (more often than not, they won't boot at all).
I've been at this for hours, but I've had no success so far. I'll let you know if I come up with anything.
EDIT:
Here's my setup:
After every try, I flash back to stock 4.1.2 with VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_CFC.xml. I've edited it so it doesn't flash the stock recovery and so it flashes a modified logo that doesn't show the bootloader warning. Partway through, I booted up and updated to the latest OTA, so I had to comment out the tz.mdm files as well. I was using TWRP 2.2.2.1, but I updated to 2.6.0.0 earlier.
GeorgeHahn said:
Same issue here. Not just CM, every 4.3 based ROM I've tried has either failed to boot or failed to boot more than once (more often than not, they won't boot at all).
I've been at this for hours, but I've had no success so far. I'll let you know if I come up with anything.
EDIT:
Here's my setup:
After every try, I flash back to stock 4.1.2 with VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_CFC.xml. I've edited it so it doesn't flash the stock recovery and so it flashes a modified logo that doesn't show the bootloader warning. Partway through, I booted up and updated to the latest OTA, so I had to comment out the tz.mdm files as well. I was using TWRP 2.2.2.1, but I updated to 2.6.0.0 earlier.
Click to expand...
Click to collapse
one of 2 things should fix this problem,
use cwm 6.0.3.5 from here or
go to recovery/mounts and storage and format the data-media line (i know it says sd card but its internal, do not format the external ed card line or you will loose data on it)
also i updated matts utiliity to the latest ota, so you dont have to take the ota just to get the baseband. its in the dev forum. i will be updating it to a newer version if you wait until later, with the newest recoveries.
edit, btw 2.6.0.0 is not the latest twrp although i recommend using cwm as some have had issues with twrp including me.
First off, the latest TWRP seems to have fixed the problems (for me, anyway). Second, you'll need to use the most up-to-date GAPPs when you flash. Also, a lot of people have noted that mounting sytem prior to doing their wipes has solved the reboot issues.
Thanks a ton for the help. Flashed latest CWM and bumped up to 4.4 and everything's working fine. I appreciate the help!

[Q] CWM not flashing the ROM despite no error

Hi.
So my GT-I9003 is running on 2.3.6 Stock. I flashed Bagaria CWM so as to flash a CyanogenMod ROM. However, when I tried it, CWM gave a Status 7 error.
I then changed the updater-script as mentioned on one of the XDA Forums. This time when I tried flashing, CWM began the process and mid-way, the device went blank after which it rebooted on its own.
There was no error displayed, whatsoever.
Any help regarding this process is appreciated. Also, if an alternated process needs to be followed, please do mention it.
Thanks.
FYI - I tried CM 7 and CM 10 (Stable versions) and both didn't work.
To avoid status 7 error do All wipes, format system and flash from internal sd. No need to change anything in the roms.

[Q] help upgrading from 4.1 to 4.3/4

ok guys, stupid question time. i have been out of the hacking game for a while and havent been keeping up with the S3 since i was running a pretty stable version of cyanogenmod. i picked up a S5 last month and the S3 has just been sitting but the wifes phone is on its last leg so i figured i would update the S3 and give it to her since it would be an upgrade to what she has now. i was running CM 4.1.2 and tried to flash the 4.3 AllianceRom. did my usual, updated CWM, downloaded the rom, checked the MD5, flashed the new modem and rom using CWM and everything looked good. then it happened. stuck at the "galaxy SIII" logo screen. nothing got me out of it. wiped everything, tried a reinstall, downloaded the rom again and did an install, nothing. tried another rom and the install failed, tried another rom and again, install failed. so i had a copy of cleanrom 5.6 which is a 4.1.1 rom and damn if that didnt hand as well. so i did a battery pull and luckly it had installed and the phone actually booted up and into android. the only downside is for some reason i cant connect to wifi with the rom. so, i still want to try either 4.3 or 4.4 on this phone so the question is, WTF am i doing wrong that it wont boot? shouldnt i be able to go from 4.1.1 to 4.3 or 4.4 by just using CWM? help a brother out.
Make sure u cwm is the most recent
Sent from my SCH-I535 using XDA Premium 4 mobile app
Mylt1 said:
ok guys, stupid question time. i have been out of the hacking game for a while and havent been keeping up with the S3 since i was running a pretty stable version of cyanogenmod. i picked up a S5 last month and the S3 has just been sitting but the wifes phone is on its last leg so i figured i would update the S3 and give it to her since it would be an upgrade to what she has now. i was running CM 4.1.2 and tried to flash the 4.3 AllianceRom. did my usual, updated CWM, downloaded the rom, checked the MD5, flashed the new modem and rom using CWM and everything looked good. then it happened. stuck at the "galaxy SIII" logo screen. nothing got me out of it. wiped everything, tried a reinstall, downloaded the rom again and did an install, nothing. tried another rom and the install failed, tried another rom and again, install failed. so i had a copy of cleanrom 5.6 which is a 4.1.1 rom and damn if that didnt hand as well. so i did a battery pull and luckly it had installed and the phone actually booted up and into android. the only downside is for some reason i cant connect to wifi with the rom. so, i still want to try either 4.3 or 4.4 on this phone so the question is, WTF am i doing wrong that it wont boot? shouldnt i be able to go from 4.1.1 to 4.3 or 4.4 by just using CWM? help a brother out.
Click to expand...
Click to collapse
You need to use the latest PhilZ Touch Recovery (https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/) (just flash it in your current recovery). It is the best, and it works great. I would first go to "Wipe Data/Factory Reset" and choose to "Clean to Install a New ROM." Then I would go into "Advanced" and wipe dalvik cache. Then I would go into "Mounts and Storage" and format boot and modem. Then I would flash the newest modem (http://www.mediafire.com/download/v0als76t6nmtpbo/DNE1.modem.zip). Then finally install your ROM and then GApps.
yes, CWM was updated just before flashing. i installed the recommended modem for the rom i was installing. not sure why it was stuck at the logo on 4.3 when i flashed a 4.1.1 rom and it booted right up just fine.
resolved. thanks guys.
Mylt1 said:
resolved. thanks guys.
Click to expand...
Click to collapse
Curious to know what you had to do to get it working?
I have two (2) S3's that I need to update and they're both running 4.1.1 ROMs.
Any info would be much appreciated.
CenFlo said:
Curious to know what you had to do to get it working?
I have two (2) S3's that I need to update and they're both running 4.1.1 ROMs.
Any info would be much appreciated.
Click to expand...
Click to collapse
i used the Philz touch CWM found here, http://forum.xda-developers.com/showthread.php?t=2201860 worked like a charm.
jonny30bass said:
You need to use the latest PhilZ Touch Recovery (https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/) (just flash it in your current recovery). It is the best, and it works great. I would first go to "Wipe Data/Factory Reset" and choose to "Clean to Install a New ROM." Then I would go into "Advanced" and wipe dalvik cache. Then I would go into "Mounts and Storage" and format boot and modem. Then I would flash the newest modem (http://www.mediafire.com/download/v0als76t6nmtpbo/DNE1.modem.zip). Then finally install your ROM and then GApps.
Click to expand...
Click to collapse
I did all of the above and I can't get anything to work....
I updated to Philz, updated the modem and went to install a new ROM and it's error'ing out every time?
This phone was rooted from way back and it appears that I may have lost root... It's stuck at the Samsung Galaxy S III boot screen and I'm trying to get it to boot in to recovery at this time.
Edit: Was able to get in to recovery and restoring a backup now. Somethings not right when trying to go to a newer ROM.
CenFlo said:
I did all of the above and I can't get anything to work....
I updated to Philz, updated the modem and went to install a new ROM and it's error'ing out every time?
This phone was rooted from way back and it appears that I may have lost root... It's stuck at the Samsung Galaxy S III boot screen and I'm trying to get it to boot in to recovery at this time.
Edit: Was able to get in to recovery and restoring a backup now. Somethings not right when trying to go to a newer ROM.
Click to expand...
Click to collapse
Did you update to the latest version? If your on an old version and attempt to flash a 4.4 rom you will get a status 7 error everytime
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
ShapesBlue said:
Did you update to the latest version? If your on an old version and attempt to flash a 4.4 rom you will get a status 7 error everytime
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
I thought I updated to the latest Phliz and I do believe that's the error I was getting when I tried to load the ROM.
I'll check again Monday.
I appreciate the info.
The issue was with Philz.
I upgraded to the latest TWRP and loaded the new ROM fine.

[Q] Rogers Infuse 4G (i997r) help upgrading to kitkat

I have a Rogers Infuse 4G (i997r) and I have been trying to upgrade it to kitkat by using a unofficial Cyanogenmod rom. More recently have been trying to use Carbon rom to update it. I have been running into problem after problem, error after error and I have finally decided to post something on XDA in hopes that someone with more experience can help me out. More information about the errors and what I have done to the phone below.
About a year ago I got this Rogers infuse 4G from a friend. I messed around with it for a bit but what I really wanted to do with it was install a custom rom and update it to a more recent version of Android (It started out on gingerbread (2.3)).
I had a real hard time getting modified recovery 3e because there was not original recovery file in system>bin to replace.
I forget most of what happened but it ended with me using a application to convert the cwm recovery zip to a md5 because I couldn't get modified 3e to work.
I tried using odin to flash the files I made but odin got stuck (or was just taking forever) and I unplugged my Infuse.
The infuse was bricked and would only show "firmware upgrade encountered an issue please select recovery mode in kies and try again". The phone would'nt enter recovery or download mode. It was recognized by odin but seemed as if it was not responding.
About 3 days ago I finally decided to try to unbrick the phone again (I don't know why just felt like it) and I found GTG ultimate unbrick with a pit file. I tried uploading this using odin and the phone responded and downloaded the files.
The phone showed a AT&T splash screen and then the Samsung logo. It hanged at the Samsung logo for about 3 minutes then would turn off reboot, show the AT&T splash screen then the hang at the Samsung logo for 3 minutes again.
I decided that I didn't actually need to install working android because I just needed CWM Recovery and found a CWM Recovery that was flashable with odin.
Now that the phone would actually show a splash screen I could access download mode and the stock 3E recovery.
I went to download mode and flashed CWM Recovery 6 - Voodoo Lagfix with odin
In the CWM Recovery I clicked install update.zip
The phone said installing and when it finished it rebooted.
It showed the AT&T logo and then the Samsung screen then it started talking (which btw scared the **** out of me) and it said installing voodoo lagfix, estimated time remaining 2 minutes
After it was done installing it rebooted and I had the same problem as before. It would show the AT&T logo then hang at the Samsung screen for 3 minutes.
I reflashed the GTG unbrick with odin then I reflashed the CWM Recovery and I was back into the recovery. (It wouldn't just let me boot into it I had to reflash it which was weird)
This time instead of clicking install update.zip I installed the Cyanogenmod-11-infuse-4g-unofficial-2014(some build number).zip
I got (status 7) installation aborted.
when the phone rebooted it showed a cyanogen mod loading screen and I got really excited
after the loading screen it went straight to proper CWM Recovery then it instantly crashed with a little fallen over Android and a red triangle over it.
It kept boot looping like this so I asked for the unbrick files for a Rogers Infuse 4G and installed those.
Once I installed the Rogers Infuse 4G Rom I set it up but I ran into the same problem I had last time.
I can't install the modified 3E recovery because the recovery file is not system>bin. CWM Recovery also fails to install even though it says it has installed.
It turns out the recovery file is on the root of my phone not /system/bin
Im not really sure what to do and guidance would be appreciated.
It's because the CWM is not only device specific, but carrier specific (at least for the Infuse).
Flash the following file (extracted) with Odin. It will talk to you as well after reboot, but it will give you CWM red which you can use to move on to custom ROMs:
https://www.dropbox.com/s/t0kc92124jat6yt/CWM Infused Kernel.zip?dl=0
Be sure to disable Voodoo Lagfix before installing any ROM's, especially if shortcut'ing directly to CarbonROM (versus installing CM9, then CM10.1 and finally a KitKat ROM).
Good luck, let me know if you have any questions.
Thanks so much for both the Rogers stock rom and the help today. I left out one crucial piece of information earlier by mistake. I tried installing both cyanogenmod and carbon rom earlier using the voodoo fix version of CWM Recovery and I got another status 7 installation aborted. I deleted the assert part of the update-script. My problem now is I get status 6 installation aborted and I haven't been able to find a quick fix for it. I just tried again using the red version of CWM Recovery you gave me and I still get the same error
Thanks so much for both the Rogers stock rom and the help today. I left out one crucial piece of information earlier by mistake. I tried installing both cyanogenmod and carbon rom earlier using the voodoo fix version of CWM Recovery and I got another status 7 installation aborted. I deleted the assert part of the update-script. My problem now is I get status 6 installation aborted and I haven't been able to find a quick fix for it. I just tried again using the red version of CWM Recovery you gave me and I still get the same error. Accidentally Double Posted... Im a noob. If someone could delete this repost it would be appereciated
OnfireNFS said:
Thanks so much for both the Rogers stock rom and the help today. I left out one crucial piece of information earlier by mistake. I tried installing both cyanogenmod and carbon rom earlier using the voodoo fix version of CWM Recovery and I got another status 7 installation aborted. I deleted the assert part of the update-script. My problem now is I get status 6 installation aborted and I haven't been able to find a quick fix for it. I just tried again using the red version of CWM Recovery you gave me and I still get the same error
Click to expand...
Click to collapse
Just to be clear. With the original ROM file, did you try installing the ROM with this CWM and Voodoo Lagfix disabled? That is go into CWM's options menu, and disable there?
Just trying to pick the low hanging fruit, unfortunately I don't know where to go from there (as this is my only idea now, besides re-downloading the ROM).
I have no problem reflashing the roms are anything. I have a iPhone 5S (hoping to get a S5 or S6 in 2015 once my contract expires ) so I have no important files or anything on this phone. (In fact I just reflashed that rogers rom yesterday from a blank slate) I noticed you have (had?) a Infuse 4G running Carbon 4.4.4 and honestly that's all I want to get to. If you want me to reflash roms or files I have no problem doing so. I just would like my infuse to run Carbon 4.4.4.
OnfireNFS said:
I have no problem reflashing the roms are anything. I have a iPhone 5S (hoping to get a S5 or S6 in 2015 once my contract expires ) so I have no important files or anything on this phone. (In fact I just reflashed that rogers rom yesterday from a blank slate) I noticed you have (had?) a Infuse 4G running Carbon 4.4.4 and honestly that's all I want to get to. If you want me to reflash roms or files I have no problem doing so. I just would like my infuse to run Carbon 4.4.4.
Click to expand...
Click to collapse
It used to be that in order to get from Gingerbread to say, Jellybean, you needed to install the Ice Cream Sandwich ROM (CM9) first. This gives you a relatively new CWM in order to do your bidding. But you man need to install a Jellybean ROM (I suggest CM10.1) in order to get a CWM that will like the installation of KitKat.
So Stock (Infused CWM) -> CM9 -> CM10.1 -> CarbonROM 4.4.4
Of course, I did say used to. Apparently if you disable Voodoo lagfix in CWM you can go straight to CarbonROM. I never tried it, but it is worth a shot (avoids having to go on a scavenger hunt).
But if you already tried it with no success, now you know the classical way.
Thanks a lot. By upgrading to cm9 then cm10 then finally Carbon Rom I was able to get the phone to kitkat!
Cheers

[HELP THREAD] cm-13 on gt-p5100

Hello guys,
I installed cm-13 successfully and it was operating fine until yesterday. Today I tried to install a theme or something and it hung. So i just felt like doing a factory reset and I did it through my cwm recovery. But before that i made a backup, then i did the reset, then i did the restore...ever since then i havent been able to open the OS...it gets stuck on the samsung GALAXY Tab2 10.1 screen. I can however access the cwm recovery. I did infact try to unzip the cm-13 that i had previously used, and it doesnt work...
Please help guys!
I am pretty new to this and i feel like i cant figure out what to do next.
Is there a way to maybe restart the whole process, like get rid of the cm-13 that is already installed and redo the whole thing again?
Kindly help guys, i was really enjoying the cm experience and i messed it up :/
killermara said:
Is there a way to maybe restart the whole process, like get rid of the cm-13 that is already installed and redo the whole thing again?
Kindly help guys, i was really enjoying the cm experience and i messed it up :/
Click to expand...
Click to collapse
you did a backup before factory reset, then you restored the same data after reset. this hardly changed anything. the reason it didn't boot, is that The problem lies at the system partition, you should wipe system partition, data partition as well and flash the same cm-13 zip again along with gapps, if you had.
now let the system start. it should boot up with a clean installation. you can then try to advance restore and chose only data partition.
later just switch to twrp recovery by Android-Andi
HELP!
billysam said:
you did a backup before factory reset, then you restored the same data after reset. this hardly changed anything. the reason it didn't boot, is that The problem lies at the system partition, you should wipe system partition, data partition as well and flash the same cm-13 zip again along with gapps, if you had.
now let the system start. it should boot up with a clean installation. you can then try to advance restore and chose only data partition.
later just switch to twrp recovery by Android-Andi
Click to expand...
Click to collapse
Hello, actually I did exactly that, i wiped system partition and all of that...then i did try with cwm, and it didnt work, what is happening is that i select the option to flash the ROM, then the screen goes blank for a second and comes back to the home screen of the cwm recovery. So basically i selected the zip and nothing happened! I then tried flashing using twrp and the problem now was that there was the "no md5 file found" message and the installation would not stop, it would go on for too long, like some sort of loop. I then switched back to cwm and tried again and it still doesnt seem to work...kindly advice on what to do next
killermara said:
Hello, actually I did exactly that, i wiped system partition and all of that...then i did try with cwm, and it didnt work, what is happening is that i select the option to flash the ROM, then the screen goes blank for a second and comes back to the home screen of the cwm recovery. So basically i selected the zip and nothing happened! I then tried flashing using twrp and the problem now was that there was the "no md5 file found" message and the installation would not stop, it would go on for too long, like some sort of loop. I then switched back to cwm and tried again and it still doesnt seem to work...kindly advice on what to do next
Click to expand...
Click to collapse
first thing check if you have updated to last official stock jellybean rom prior to cm13 upgrade.
this thread will help you to update your bootloader to jb from ics. if you have a jb bootloader already. you can skip this.
forum.xda-developers.com/showthread.php?t=2642005
next thing you should get twrp 3.0.2.8
https://www.androidfilehost.com/?w=files&flid=48848&sort_by=date&sort_dir=DESC
after wiping, restart recovery, then flash the Rom zip
it takes time with the new CM13 builds to complete installation. some earlier twrp recoveries had issues(3.0.0.1 and 0.2, not sure right now, try latest only). cwm is not supported and twrp is the only preferred recovery by the Rom developers to flash the newer roms.
remember p5100 tab is called espresso3g now, since development has been unified. you need files marked as espresso3g for your p5100.
I don't which files are you using, development has changed so confirm the files that you're using are for unified builds and not device specific.
billysam said:
first thing check if you have updated to last official stock jellybean rom prior to cm13 upgrade.
this thread will help you to update your bootloader to jb from ics. if you have a jb bootloader already. you can skip this.
forum.xda-developers.com/showthread.php?t=2642005
next thing you should get twrp 3.0.2.8
https://www.androidfilehost.com/?w=files&flid=48848&sort_by=date&sort_dir=DESC
after wiping, restart recovery, then flash the Rom zip
it takes time with the new CM13 builds to complete installation. some earlier twrp recoveries had issues(3.0.0.1 and 0.2, not sure right now, try latest only). cwm is not supported and twrp is the only preferred recovery by the Rom developers to flash the newer roms.
remember p5100 tab is called espresso3g now, since development has been unified. you need files marked as espresso3g for your p5100.
I don't which files are you using, development has changed so confirm the files that you're using are for unified builds and not device specific.
Click to expand...
Click to collapse
I followed all the steps that you suggested, and the thread suggested.
I installed custom recovery, then I updated the bootloader.
Then i flashed the new twrp, which is alot more easier to operated compared to the cwm .
then i wiped , restarted recovery, then flashed the rom,
the exact same thing that was previously happening with the cwm happened : I tapped on the rom, then a blank screen appeared and it went back to the main menu of the twrp...
The ROM i am using is: cm-13.0-20160220-1347-UNOFFICIAL-p5100.zip
i also tried using the ROM i got from get.cm : cm-11-20160822-NIGHTLY-p5100.zip
Okay so i played a slow mo video to see what the screen says before it goes back to the welcome screen:
Updating partition details. . .
. . . done
Full SElinux support is present.
MTP Enabled
Then after this pops up, it goes back to the main menu of the twrp.
What if i just reinstall the stock OS then do the whole process of getting cyanogenmod again from rooting onwards?
Kindly assist!!
killermara said:
I followed all the steps that you suggested, and the thread suggested.
I installed custom recovery, then I updated the bootloader.
Then i flashed the new twrp, which is alot more easier to operated compared to the cwm .
then i wiped , restarted recovery, then flashed the rom,
the exact same thing that was previously happening with the cwm happened : I tapped on the rom, then a blank screen appeared and it went back to the main menu of the twrp...
The ROM i am using is: cm-13.0-20160220-1347-UNOFFICIAL-p5100.zip
i also tried using the ROM i got from get.cm : cm-11-20160822-NIGHTLY-p5100.zip
Okay so i played a slow mo video to see what the screen says before it goes back to the welcome screen:
Updating partition details. . .
. . . done
Full SElinux support is present.
MTP Enabled
Then after this pops up, it goes back to the main menu of the twrp.
What if i just reinstall the stock OS then do the whole process of getting cyanogenmod again from rooting onwards?
Kindly assist!!
Click to expand...
Click to collapse
OKAY! So i have had some progress in the situation i got myself into! Now i just changed the sd card and tried to flash the ROM, so it didnt successfully flash, it says:
Zip file is corrupt!
Error installing zip file ..*the directory of the ROM*
This doesnt make sense though because i used the exact same ROM earlier and it worked, i used it for a whole day and it was fine...
killermara said:
OKAY! So i have had some progress in the situation i got myself into! Now i just changed the sd card and tried to flash the ROM, so it didnt successfully flash, it says:
Zip file is corrupt!
Error installing zip file ..*the directory of the ROM*
This doesnt make sense though because i used the exact same ROM earlier and it worked, i used it for a whole day and it was fine...
Click to expand...
Click to collapse
do what @billysam said.
dont use device specific stuff. the latest twrp will only work with unified builds. for your device you need espresso3g builds.
you will find the latest roms on android-andis github site http://andi34.github.io/index.html
killermara said:
OKAY! So i have had some progress in the situation i got myself into! Now i just changed the sd card and tried to flash the ROM, so it didnt successfully flash, it says:
Zip file is corrupt!
Error installing zip file ..*the directory of the ROM*
This doesnt make sense though because i used the exact same ROM earlier and it worked, i used it for a whole day and it was fine...
Click to expand...
Click to collapse
you're using device specific Rom build, cm13.0 unofficial p5100, the latest twrp recovery you have, is a unfied espresso3g one.
latest roms, are build upon espresso3g for p5100,p3100 and espressowifi for p5110,p5113 p3113.
use latest cm13 rom zip, marked espresso3g.
there are device specific roms and recovery, which developers have stopped working on, your issue is because of this. get unified recovery and rom.
billysam said:
you're using device specific Rom build, cm13.0 unofficial p5100, the latest twrp recovery you have, is a unfied espresso3g one.
latest roms, are build upon espresso3g for p5100,p3100 and espressowifi for p5110,p5113 p3113.
use latest cm13 rom zip, marked espresso3g.
there are device specific roms and recovery, which developers have stopped working on, your issue is because of this. get unified recovery and rom.
Click to expand...
Click to collapse
Yea i thought so too, thats why i downloaded the cm-13.0-20161117-NIGHTLY-espresso3g.zip, then i wiped and tried to flash this rom, this also gave me the same error,
i also noticed that before the lines
Zip file is corrupt
there was:
Checking for MD5 file. . .
Skipping MD5 check: no MD5 file found.
killermara said:
Yea i thought so too, thats why i downloaded the cm-13.0-20161117-NIGHTLY-espresso3g.zip, then i wiped and tried to flash this rom, this also gave me the same error,
i also noticed that before the lines
Zip file is corrupt
there was:
Checking for MD5 file. . .
Skipping MD5 check: no MD5 file found.
Click to expand...
Click to collapse
maybe the zip got corrupted, checked your pc with anti-virus? are you downloading the zip file from androidfilehost of android-andi? or some other source? checked your sd card as well?

Categories

Resources