Hello, i just bought Nexus S i9020 from Carphone Warehouse UK, and just cant install ICS rooms. in ClockworkMod Recovery 3 it says:
assert failed: get.prop("ro,product.device") == "crespo" || get.prop("ro.build.product") == "crespo"
E:Error in /sdcard/cm_crespo-ota-eng.kalimochoaz.a20.p1.zip
Status 7
This is: [ROM] [i9020/23] CyanogenMod 9 v4.0.3 Alfa 20p1 room
Also tried MIUI: http://miuiandroid.com/2012/01/miui-rom-2-1-6-ics-v4-0-miuiandroid-english-version/
Update: just tried office stable build CM7.1, same...
I searched and found on other forum that this could be wrong device. But how is this possible, i know that it's Nexus S and not Nexus S 4G, and on the back where is SN it says i9020
And when going to ClockworkMod Recovery it takes about 1min to get there? for example booting to bootloader and then going to Recovery, and it loads CWM about 1min maybe longer. I also tried differenced recovery it also takes about 1 min to load, can’t remember how it called but i used Root Guide from this source: http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s-or-nexus-s-4g-new/
I hope some one will know what is the problem. Thank you for your time.
Update your recovery. CWM is on version 5.
Also make sure you are installing via the install zip from SD card method and not the install update.zip
Sent from my Nexus S 4G using xda premium
you need to update your clockworkmod recovery to v5.X.X.X , your version is old.
Fast responce thank you
I Have opened this thread for test purposes only
THIS is a thread of Ressurection Remix 5.2.5 android 5.0.2
LINK to rom here
LINK TO gapps Here
Link to raw kernel here
FIRST YOU NEED the compaitble recovery and kernel ,the same one that cm12 uses
Refer THIS Thread
installing:
copy Rom+Google Apps to sdcard
boot into recovery
(factory reset) (if you get fc's or bootloops after updating from an older rom)
flash the rom and gapps zip file
reboot
now remember always take a nadroid backup of previous rom
some users report this error
Code:
error status 7
assert failed: package_extract_file("boot.img", "/tmp/boot.img")
somebody knows how to fix this error please feel free to share here and test the ROM
status 7 error as I have always seen is related to incompatible recovery.
People got it while trying to flash kk ROMs coming from JB using a non SE Linux recovery.
Maybe try raw kernel?
remember not to boot system after flashing that kernel but reboot to recovery.
REVENGE SOLVES EVERYTHING
Help needed
Hi developers, testers, and community members
@bauner
@TouchLeclouds
@tysonraylee
@01000010
@Dekuki
sorry for mentioning you guys here,
hopefully we can create varieties for Lollipop, :angel:
and probably with this development, we can also helping each other, sharing knowledge and such :highfive:
here's my workaround for attempting flashing this rom,
#method 1
1. reboot into recovery, flash forest v5 cm11 philz -based kernel/recovery
2. do wipes (everything),
3. flash the rom,
4. failed with status 7 error,
#method 2
1. reboot into recovery, flash bauner's cwm-based kernel/recovery v1.2.1
2. do wipes (everything),
3. flash the rom,
4. failed with status 7 error,
#method 3
1. reboot into recovery, flash raw kernel v7 for cm11 twrp-based kernel/recovery
2. do wipe (everything),
3. flashed the rom,
4. failed with status 7 error,
#method 4
1. redownload zips,
2. apply recovery method #1, #2, #3,
3. flashed the rom,
4. still failed with status 7
#method 5
1. redownload zips, replaced bauner's NightOwl boot.img into Ress.Remix 5.0
2. apply reovery method #1, and #2,
3. flashed the rom,
4. failed with status 7, as well
that's my report, tester : me and @nitangle17
please post a screenshot of the error
----------------
update : according to my findings this "status 7 assert" error is either because
1) you trying to flash a different model/variant ROM on device i.e S2 ROM on S3
2) incompatible recovery i.e non se Linux compatible.
there is a workaround for the issue 1 but we need to make sure that this ROM file IS for N7000 or it WILL BRICK the device.
tysonraylee said:
please post a screenshot of the error
----------------
update : according to my findings this "status 7 assert" error is either because
1) you trying to flash a different model/variant ROM on device i.e S2 ROM on S3
2) incompatible recovery i.e non se Linux compatible.
there is a workaround for the issue 1 but we need to make sure that this ROM file IS for N7000 or it WILL BRICK the device.
Click to expand...
Click to collapse
I have compiled this from bauners sources so its 100% for n7000 ..come on :-/
And even the updater script says so
varund7726 said:
I have compiled this from bauners sources so its 100% for n7000 ..come on :-/
And even the updater script says so
Click to expand...
Click to collapse
well in that case take a look here http://forum.xda-developers.com/showthread.php?t=2522762
and I think you should have the idea what's going on and how to solve it
REVENGE SOLVES EVERYTHING
tysonraylee said:
well in that case take a look here http://forum.xda-developers.com/showthread.php?t=2522762
and I think you should have the idea what's going on and how to solve it
REVENGE SOLVES EVERYTHING
Click to expand...
Click to collapse
Thw cauae of the status 7 error here is becauae of the SE linux disabled recovery
I dont think removing lines like assert is recommented but i will ask my testers to give it a try.
But the cm12 dev uses the exact same updater script as mine
And some users are able to flash it and some arent (getting this same error)
tysonraylee said:
please post a screenshot of the error
----------------
update : according to my findings this "status 7 assert" error is either because
1) you trying to flash a different model/variant ROM on device i.e S2 ROM on S3
2) incompatible recovery i.e non se Linux compatible.
there is a workaround for the issue 1 but we need to make sure that this ROM file IS for N7000 or it WILL BRICK the device.
Click to expand...
Click to collapse
unfortunately I can't this the only phone I had, my S plus are not with me currently,
anyway, I'm not sure any of this issue causing the error are appear to be mine only, but I'm sure it is
status 7 error failed to write..bla..bla "/tmp/boot.img.."
I already forgot how's the error,
I'll try again in some time, currently at work and kinda busy, :crying:
so sorry guys,
hopefully others help too, :highfive:
please :good:
varund7726 said:
Thw cauae of the status 7 error here is becauae of the SE linux disabled recovery
I dont think removing lines like assert is recommented but i will ask my testers to give it a try.
But the cm12 dev uses the exact same updater script as mine
And some users are able to flash it and some arent (getting this same error)
Click to expand...
Click to collapse
you are right I too think we should not try it. Maybe bauner could look into it. I will see if I am able to flash it later
REVENGE SOLVES EVERYTHING
tysonraylee said:
you are right I too think we should not try it. Maybe bauner could look into it. I will see if I am able to flash it later
REVENGE SOLVES EVERYTHING
Click to expand...
Click to collapse
goodluck buddy! :highfive: :victory: :highfive:
I heard 4.2.2 is going to landed on our device by old sammy, seems nice for forest kernel development! :victory:
kazuna69 said:
Hi developers, testers, and community members
@bauner
@TouchLeclouds
@tysonraylee
@01000010
@Dekuki
sorry for mentioning you guys here,
hopefully we can create varieties for Lollipop, :angel:
and probably with this development, we can also helping each other, sharing knowledge and such :highfive:
here's my workaround for attempting flashing this rom,
#method 1
1. reboot into recovery, flash forest v5 cm11 philz -based kernel/recovery
2. do wipes (everything),
3. flash the rom,
4. failed with status 7 error,
#method 2
1. reboot into recovery, flash bauner's cwm-based kernel/recovery v1.2.1
2. do wipes (everything),
3. flash the rom,
4. failed with status 7 error,
#method 3
1. reboot into recovery, flash raw kernel v7 for cm11 twrp-based kernel/recovery
2. do wipe (everything),
3. flashed the rom,
4. failed with status 7 error,
#method 4
1. redownload zips,
2. apply recovery method #1, #2, #3,
3. flashed the rom,
4. still failed with status 7
#method 5
1. redownload zips, replaced bauner's NightOwl boot.img into Ress.Remix 5.0
2. apply reovery method #1, and #2,
3. flashed the rom,
4. failed with status 7, as well
that's my report, tester : me and @nitangle17
Click to expand...
Click to collapse
Status 7 error is caused while the ROM’s updater script file checks to see if the phone model of your phone is compatible with the ROM you are installing,
Back up your things
Flash DU 8.1 (Because it have Latest TWRP recovery)
Reboot into recovery
Clear cache, Factory rest
Flash the Rom + Gapps
TouchLeclouds said:
Status 7 error is caused while the ROM’s updater script file checks to see if the phone model of your phone is compatible with the ROM you are installing,
Back up your things
Flash DU 8.1 (Because it have Latest TWRP recovery)
Reboot into recovery
Clear cache, Factory rest
Flash the Rom + Gapps
Click to expand...
Click to collapse
Status 7 here is due to se linux recovery
varund7726 said:
Status 7 here is due to se linux recovery
Click to expand...
Click to collapse
I had the same issue before, my problem was solved by changing the update script
TouchLeclouds said:
I had the same issue before, my problem was solved by changing the update script
Click to expand...
Click to collapse
So can we change bauner update script and check the possibility
mjrifath said:
So can we change bauner update script and check the possibility
Click to expand...
Click to collapse
you can try that, but also keep in mind that this issue could be caused anything else. i just gave the solution that worked for me
Ok i got it to boot.thanks for the help guys.ill open a thread in the dev section and close this one
Hello guys, since I've installed CM12 I've been getting errors from TWRP when flashing CM updates.
I had a Nexus 4 and when I installed CM updates it usually rebooted to recovery and then TWRP would install it automatically, but it's not happening on my G2 D802. I have TWRP 2.8.5, installed with Autorec before flashing CM12 for the first time.
Error log says shortly after I start to flash CM updates:
E: ZIP file is corrupt!
E: Error installing zip fie '/cache/recovery/block.map'
Then it goes on and finishes flashing and it says successful, in fact it always works, but should I be concerned? Am I doing something wrong or it has something to do with the bootloader? I've read somewhere that you had to downgrade the bootloader in order to flash, but also read somewhere that autorec does that for you. I've also read that it could have been that I was using an old recovery, but I'm using the latest, I don't know what it could be...
Thanks in advance
Rino7617 said:
Hello guys, since I've installed CM12 I've been getting errors from TWRP when flashing CM updates.
I had a Nexus 4 and when I installed CM updates it usually rebooted to recovery and then TWRP would install it automatically, but it's not happening on my G2 D802. I have TWRP 2.8.5, installed with Autorec before flashing CM12 for the first time.
Error log says shortly after I start to flash CM updates:
E: ZIP file is corrupt!
E: Error installing zip fie '/cache/recovery/block.map'
Then it goes on and finishes flashing and it says successful, in fact it always works, but should I be concerned? Am I doing something wrong or it has something to do with the bootloader? I've read somewhere that you had to downgrade the bootloader in order to flash, but also read somewhere that autorec does that for you. I've also read that it could have been that I was using an old recovery, but I'm using the latest, I don't know what it could be...
Thanks in advance
Click to expand...
Click to collapse
No, wait. I got the same issue with BUMPED TWRP, please install the classic OpenTWRP 2.5.0 (not bumped) and you will upgrade the system without any issue.
Buona giornata, stammi bene e buon modding!
I'm using normal TWRP, downloaded latest versione from its website, I'm not using the bumped one.
cm 12 corrupt update and wifi problems
I have the same problem as u do! And when I leave my home wifi, and later return to it, I have to reboot the phone in order for it to connect to the home wifi again... In the wifi settings it says either "Connecting" or "Saved".
I would be very grateful for any help!
Same happens here, it installs fine, I just have to do it manually. I'm on TWRP v2.8.5.0.
Same here,I have to flash the zip manually.
The last week got the update of 22.5 mb
But I am on the twrp and rooted so I can download it but can't install because its gives error while installing
I m also tried to flashing stock recovery then install same doesn't work
Any one idea about how to convert for this update to twrp
Plz do that
Here the link any one want to install offline original update
Plz don't put direct link
http://viid.me/999O4
It says emmc not matching means the update could be of a different region that is S135.
Sent from my K016 using Tapatalk
No bro it gives status error 7
onkar.35 said:
No bro it gives status error 7
Click to expand...
Click to collapse
I think you have to use flashfire theres option to flash ota update, hope it will help you
Same is with me, flashfire is not able to detect my downloaded OTA package.
Any more solutions?
I make a flashig file .But after flashing, IMEI number and some lag issue in my device i have faced.
Let me time .I'll try.