Installation Aborted - Status 7 (expected 5 arguments, got 4) - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

I've been trying to flash TheAxman 's [ROMS][ViSiON-X STOCK SHOP][i9505/i337][ViS-STOCK][STABLE BASES][03-18] but i keep getting a status 7, installation aborted error which claims that the the expected number of arguments is 5, got 4.
the steps i did to get this error message were:
wipe data/ factory reset --> wipe cache --> format system --> wipe dalvik --> install VisionX's rom
My device is the i337m, its unlocked im with telus
i attached a screenshot of the about phone info for reference.
The device is rooted using cf-auto, and has cwm 6.0.4.7 installed, running on 4.2.2 stock ROM
Now from what i understood in the installation instructions, I should be flashing my carrier's kernel after installing the new ROM, but i cant even get past the rom installation.. I read around the forums that this might be due to a broken updater script, I 'm also iffy as to where/ how I could get a hold of my carriers kernel file to use after (hopefully) i get Vision-X installed on the device..
according to ktoonsez, I should use [KERNEL][TMO][AOSP/TW/GE - 4.4/4.3/4.2][03/12/2014] KT-SGS4 - MJ5 - KTweaker
lastly, i dont know if this is relevant, but in the CWM log i have a message that shows up saying the following
"can't partition non mmcblk device: /devices/platform/msm_sdcc . 2/mmc_host/mmc2"
thank you in advance for your time and assistance

Anyone?
happiness is a warm mug

The French Tickl3r said:
I've been trying to flash TheAxman 's [ROMS][ViSiON-X STOCK SHOP][i9505/i337][ViS-STOCK][STABLE BASES][03-18] but i keep getting a status 7, installation aborted error which claims that the the expected number of arguments is 5, got 4.
the steps i did to get this error message were:
wipe data/ factory reset --> wipe cache --> format system --> wipe dalvik --> install VisionX's rom
My device is the i337m, its unlocked im with telus
i attached a screenshot of the about phone info for reference.
The device is rooted using cf-auto, and has cwm 6.0.4.7 installed, running on 4.2.2 stock ROM
Now from what i understood in the installation instructions, I should be flashing my carrier's kernel after installing the new ROM, but i cant even get past the rom installation.. I read around the forums that this might be due to a broken updater script, I 'm also iffy as to where/ how I could get a hold of my carriers kernel file to use after (hopefully) i get Vision-X installed on the device..
according to ktoonsez, I should use [KERNEL][TMO][AOSP/TW/GE - 4.4/4.3/4.2][03/12/2014] KT-SGS4 - MJ5 - KTweaker
lastly, i dont know if this is relevant, but in the CWM log i have a message that shows up saying the following
"can't partition non mmcblk device: /devices/platform/msm_sdcc . 2/mmc_host/mmc2"
thank you in advance for your time and assistance
Click to expand...
Click to collapse
Check if your download is good first. However, I don't believe you can use that kernel as it says I337 and not I337m.

Installation Aborted - Status 7 (expected 5 arguments, got 4) > Reply to Thread
DeadlySin9 said:
Check if your download is good first. However, I don't believe you can use that kernel as it says I337 and not I337m.
Click to expand...
Click to collapse
thank you for your input, I will redownload the file to cross that out. as for the kernel, how/where might I be able to find it? Can I simply use the stock kernel on 4.2.2 from telus ?

The French Tickl3r said:
thank you for your input, I will redownload the file to cross that out. as for the kernel, how/where might I be able to find it? Can I simply use the stock kernel on 4.2.2 from telus ?
Click to expand...
Click to collapse
Stock kernel will work as long as you're only using other 4.2.2 Touchwiz ROMs. Otherwise, you can check the development section for any kernel thread that lists I337m

DeadlySin9 said:
Stock kernel will work as long as you're only using other 4.2.2 Touchwiz ROMs. Otherwise, you can check the development section for any kernel thread that lists I337m
Click to expand...
Click to collapse
Kernel is right. TMO for the I337M.
I've had status 7 errors before using philz and they were solved using 1 of 2 methods. First, I would check the rom for asserts (txt at the beginning of the updater-script that checks ur device version code against those intended for the roms use). If u find an assert in the script, just delete it and try the install again.
Second thing u could try that worked for me was (idk if standard cwm has this option but philz does) checking the 'allow old update binary' box in the settings. If it's not there, try philz or twrp.
Lastly, like deadly said, don't flash the kernel til u get the ROM to boot. That way troubleshooting is easier

thank you both for your valuable input. I will give it another shot

Recovery..
The French Tickl3r said:
I've been trying to flash TheAxman 's [ROMS][ViSiON-X STOCK SHOP][i9505/i337][ViS-STOCK][STABLE BASES][03-18] but i keep getting a status 7, installation aborted error which claims that the the expected number of arguments is 5, got 4.
the steps i did to get this error message were:
wipe data/ factory reset --> wipe cache --> format system --> wipe dalvik --> install VisionX's rom
My device is the i337m, its unlocked im with telus
i attached a screenshot of the about phone info for reference.
The device is rooted using cf-auto, and has cwm 6.0.4.7 installed, running on 4.2.2 stock ROM
Now from what i understood in the installation instructions, I should be flashing my carrier's kernel after installing the new ROM, but i cant even get past the rom installation.. I read around the forums that this might be due to a broken updater script, I 'm also iffy as to where/ how I could get a hold of my carriers kernel file to use after (hopefully) i get Vision-X installed on the device..
according to ktoonsez, I should use [KERNEL][TMO][AOSP/TW/GE - 4.4/4.3/4.2][03/12/2014] KT-SGS4 - MJ5 - KTweaker
lastly, i dont know if this is relevant, but in the CWM log i have a message that shows up saying the following
"can't partition non mmcblk device: /devices/platform/msm_sdcc . 2/mmc_host/mmc2"
thank you in advance for your time and assistance
Click to expand...
Click to collapse
that recovery using these?

I switched to twrp 2.6.3.0, and im not getting the stat7 error anymore. granted, im also trying to flash a different rom, slimkat.
problem now is that im getting stuck on the splash screen with the sammie logo..

The French Tickl3r said:
I switched to twrp 2.6.3.0, and im not getting the stat7 error anymore. granted, im also trying to flash a different rom, slimkat.
problem now is that im getting stuck on the splash screen with the sammie logo..
Click to expand...
Click to collapse
You flashed the ROM and Gapps and made sure to wipe data right? Also, which one are you flashing (which model)?

DeadlySin9 said:
You flashed the ROM and Gapps and made sure to wipe data right? Also, which one are you flashing (which model)?
Click to expand...
Click to collapse
hi deadlysin9,
thank you for the follow up
steps were:
boot to twrp 2.6.3.0 recovery, wipe data, cache, system and dalvik
then flash rom and gapps
my device is the i337m (telus but unlocked) and im using the jflteatt found here,

The French Tickl3r said:
hi deadlysin9,
thank you for the follow up
steps were:
boot to twrp 2.6.3.0 recovery, wipe data, cache, system and dalvik
then flash rom and gapps
my device is the i337m (telus but unlocked) and im using the jflteatt found here,
Click to expand...
Click to collapse
Try using the jfltetmo build, from what I've read t-mobile ROMs and kernels work on the I337m. If that doesn't work the international build is the next best bet.

hello,
just a quick update on our latest discussion, it seems that the tmo build is indeed the right one to flash, ive finally rid myself of TW, and running on slimkat. many thanks for your valuable input.

Related

Can no longer flash ROMS/ROOT

Hey guys, I am having some issues flashing roms through CWM as well as rerooting.
A bit of backround info
Device: GT-P7510
Started with latest OTA stock rom. I was wanting to use titanium backup to uninstall some bloatware.
Rooted successfully following the wifi only version forum post on how to root.
Did what i wanted, but now i wanted more.
Decided to try to get Jellybean on my device. Loaded into CWM - flashed - successful.
Now i ran into the issue of no flash support - needed for school work i do on my tablet. Tried to follow guide on installing flash.. did not work, tried the titanium backup method as well with no prevail.
Decided to flash back to ICS. I chose the CM9 ROM.
Loaded into CWM - wiped data / cache/ dalvik / Installed rom from SD card - flashed successfully
I noticed that my home button was not working. so after another data wipe etc. and re flash of the rom it did.
I then could not get googleplay to function just kept getting server error no matter what i tried. I tried installing apk from the web. did not work. and tried loading gapps.zip through odin. Installed other google apps that did work, just not google play..
So i was like holy hell. what to do now. Tried installing another ICS ROM ( the one that mimics jellybean)... It fails instantly after unloading package or something of that nature. I tried about 3 different roms and get the same issue.
So i then followed the guide to unroot - it required flashing the stock ROM through CWM . I tried this but got a status 7 error. Not really sure what that was so i found another guide.
The alternative guide had me load the original ROM for the device via odin. Worked great!!! I thought i was in clear sailing. Updated to the OTA ICS ROM. And then went to follow the root guide again. It acted as if it was rooted, but upon reboot option in CWM it says root access might have been lost.. do you want to fix. I tried both no and yes. Reguardless i do not gain root.
I tried flashing other roms through CWM - they all fail instantly ( not with any specific error messages ) just says aborted.
Any idea on what i may be doing wrong?
What version of cwm u using ?
5.5.0.4 works best for our tabs coz he has not got some verification for unsigned zips something like that .
Hmm i think the problem is when u updated ota it took your root away so i would suggest flashing cf-root again via odin
Just guessing though really strange, perhaps back up data on sd card and format it too i know its a pain but could help aswell
;/
Sent from my GT-P7500 using xda app-developers app
I was on 6. something. So that may be my issue.
I did try an older version v4.0.0.4 which was included in the guide i used but that did not seem to work either. I will download that version and see what happens.
As far as flashing cf-root. I am going to do a forum search but the method i used used the file Samsung_galaxy_tab_10.1_root.zip through CWM.
it is always risk to Odin back to stock and update OTA I have bricked 2 android devices by doing this .......once you install custom roms it is always better not to install official update ..... ur device is not rooted properly just go to unrooted stock rom if possible and later get root.zip then try rooting ur tab using it .......and this might help ...... forum.xda-developers.com/showthread.php?t=1474971..........
CHEERS
HIT THANKS BUTTON IF I HAVE HELPED

Question About Software Error Message

Hi guys. Not new to rooting but new to my AT&T S4. I rooted it tonight with Motochopper and installed CWM recovery. Downloaded and tried to flash a ROM, and it simply didn't work. Then I tried Beanstalk 4.2.2, and it downloads, but then when I rebooted it, it gave me the yellow triangle unauthorized software message. So I pulled the battery and finally got it to boot into recovery, then installed the back up I had from the stock OS. My question is two fold-what's causing this and if I download a ROM with the Loki patch, will that bypass the error message I'm getting. I searched the forums but am not understanding what was written. I'm pretty confused, any help would be greatly appreciated.
chokem said:
Hi guys. Not new to rooting but new to my AT&T S4. I rooted it tonight with Motochopper and installed CWM recovery. Downloaded and tried to flash a ROM, and it simply didn't work. Then I tried Beanstalk 4.2.2, and it downloads, but then when I rebooted it, it gave me the yellow triangle unauthorized software message. So I pulled the battery and finally got it to boot into recovery, then installed the back up I had from the stock OS. My question is two fold-what's causing this and if I download a ROM with the Loki patch, will that bypass the error message I'm getting. I searched the forums but am not understanding what was written. I'm pretty confused, any help would be greatly appreciated.
Click to expand...
Click to collapse
So, to sum up development in this forum for the last 3 months: The ATT version of the S4 has a locked bootloader, which is a fancy way of saying ATT and Samsung don't want custom software on their phone partitions. To keep people from installing custom ROMs, their bootloader requires a verified signature present in the ROM to actually allow the device to boot.
An individual found a way to trick this verification process, and created a patch for it called LOKI.
When a ROM is "Loki'd" it contains this workaround for the verification process in the bootloader, allowing custom software to be installed.
To answer your question, when you root your phone and install the recovery (TWRP or OUDHS): a ROM must be lokied to work. OUDHS recovery has a feature which automatically installs the workaround in every ROM you flash using the utility. I recommend this version of Clockwork Recovery.
The link is here:
http://forum.xda-developers.com/showthread.php?t=2291956
I personally use the nightly CyanogenMod 10.1 builds for the ATT S4 (called jlteatt). They're quick and stable except for a few quirks with the camera, call-audio via headsets, and bluetooth audio.
The link to download is here:
http://get.cm/?device=jflteatt
*This version of CM 10.1 is already Loki'd
Have fun flashing, and if all else fails and you accidentally run into a scenario where you can't boot your phone, use this utility to restore the factory OS that comes with the phone.
http://forum.xda-developers.com/showthread.php?t=2261573
Furies said:
So, to some up development in this forum for the last 3 months: The ATT version of the S4 has a locked bootloader, which is a fancy way of saying ATT and Samsung don't want custom software on their phone partitions. To keep people from installing custom ROMs, their bootloader requires a verified signature present in the ROM to actually allow the device to boot.
An individual found a way to trick this verification process, and created a patch for it called LOKI.
When a ROM is "Loki'd" it contains this workaround for the verification process in the bootloader, allowing custom software to be installed.
To answer your question, when you root your phone and install the recovery (TWRP or OUDHS): a ROM must be lokied to work. OUDHS recovery has a feature which automatically installs the workaround in every ROM you flash using the utility. I recommend this version of Clockwork Recovery.
The link is here:
http://forum.xda-developers.com/showthread.php?t=2291956
I personally use the nightly CyanogenMod 10.1 builds for the ATT S4 (called jlteatt). They're quick and stable except for a few quirks with the camera, call-audio via headsets, and bluetooth audio.
The link to download is here:
http://get.cm/?device=jflteatt
*This version of CM 10.1 is already Loki'd
Have fun flashing, and if all else fails and you accidentally run into a scenario where you can't boot your phone, use this utility to restore the factory OS that comes with the phone.
http://forum.xda-developers.com/showthread.php?t=2261573
Click to expand...
Click to collapse
OK, thanks very much. So I was indeed on the right track. I'll try your ROM recommendation as well as the modified CWM recovery.

[Q] Having tons of problems please help

Ok so before I start I did try to put this on the developers page but I haven't made enough posts yet so it didn't let me .... I am having lots of problems with my Canadian Samsung galaxy s4 sgh 1337m .... I don't even know where to start .. first off im rooted so I have that covered I know that for a fact I also have team win recovery project ... now I want to rom buy my phone will NOT allow me to do it ... I will go online I will download the rom and the Gapps directly to my internal storage ... il go into it il do the whole wipe cache and Delvik and then factory reset .. then ill flash the rom and the Gapps and it says failed to flash the rom but the Gapps are successful .. I then flash my backup and proceed with my day .... YES I am downloading them for the correct device .... why is this happening ?? in my last post someone replied my Twrp may be out dated so I went onto my new computer and tried to install Odin again so I could flash the new Twrp to my device and my computer wont let me open Odin its a new windows 8 and it WILL NOT open it it gives me some Chinese letters and closes ... Why is this happening to me ?? why cant I open Odin or download Roms to my phone ... I've watched numerous instruction videos and it works perfectly for everyone accept for me .. someone please help me .... if my issue is resolved I will be donating to XDA .... this issue has been ongoing for weeks .
have you verified the md5 sum of your downloads?
also what backup method did you use?
muskratt said:
have you verified the md5 sum of your downloads?
also what backup method did you use?[/QUOTE
What is the whole verify thing your telling me about ive never had to do it before on other devices its just been simple .... also I use team win recovery project to create my backups
Click to expand...
Click to collapse
Lets start with what rom are you trying to flash? I noticed you are trying to flash gapps.....so I take it you are trying to flash a aosp rom.
Timtim1234321 said:
muskratt said:
have you verified the md5 sum of your downloads?
also what backup method did you use?[/QUOTE
What is the whole verify thing your telling me about ive never had to do it before on other devices its just been simple .... also I use team win recovery project to create my backups
Click to expand...
Click to collapse
Most roms provide an md5 number to verify a good download. It is a checksum that tells you the download is good. Get a file explorer like FX Explorer. Long press on rom you downloaded and then open details. It will have selection to do a checksum. The number should match the one from the rom site where you downloaded it from. Very common to get a bad download from time to time. You can also use terminal on pc, if you familiar with that and have adb on your pc. I prefer that method. I do it as soon as download to rom to pc.
Also, what version twrp are you on. Most prefer 2.5.0.2. This is a flashable zip for it.
https://www.dropbox.com/sh/yhrq0tia8512rj9/FCjN8C9RMT/TWRP_Flashable-2.5.0.2.zip
Flash thru your current twrp recovery. Unless you already have 2.5.0.2 or the very latest twrp seems ok. On 2.5.0.2 don't ever do a format where you have to type "yes" to comfirm format.
I always wipe thru the Advanced menu manually. I wipe System/Data/Caches 3x. Always do that flashing new roms on new versions to a rom, unless dev says otherwise. Or, on CM Nightlies. Even then it doesn't hurt to do a full wipe on occasion. Crap can build up over time dirty flashing and cause issues.
As Ax said, unless you are flashing a CM roms, no need for gapps. Also, depending on rom you are flashing you may need to flash your carriers kernel after rom.
So, more info may be needed to help you--:good:
Click to expand...
Click to collapse

[Q] i337 - MF3 v4.2.2; unable to change ROM

I currently have the Samsung Galaxy S4 - MF3; v4.2.2; i337. I got the phone unlocked (direct from AT&T); and then
1. followed this method to root my phone - http://forum.xda-developers.com/showthread.php?t=2387577- Worked.
2. Got Safestrap v3.65 - http://blog.hash-of-codes.com/downloads/safestrap/ - Worked.
3. Tried 3-4 different ROMs, none of them have worked.
a. http://forum.xda-developers.com/showthread.php?t=2356276
b. http://forum.xda-developers.com/showthread.php?t=2418522
c. http://forum.xda-developers.com/showthread.php?t=2630085
d. http://forum.xda-developers.com/showthread.php?t=2537495
4. Tried above ROMs with kernels from here - http://forum.xda-developers.com/showthread.php?t=2292341 (v4.2.2 or v4.4 - depending on the ROM) and also the MF3 kernel (can't find the link)
But, irrespective of what I try, I still get stuck while loading the ROM - blank screen, not moving forward. Could you please shed some light on what I should try to do?
Thanks!
Vishoka said:
I currently have the Samsung Galaxy S4 - MF3; v4.2.2; i337. I got the phone unlocked (direct from AT&T); and then
1. followed this method to root my phone - http://forum.xda-developers.com/showthread.php?t=2387577- Worked.
2. Got Safestrap v3.65 - http://blog.hash-of-codes.com/downloads/safestrap/ - Worked.
3. Tried 3-4 different ROMs, none of them have worked.
a. http://forum.xda-developers.com/showthread.php?t=2356276
b. http://forum.xda-developers.com/showthread.php?t=2418522
c. http://forum.xda-developers.com/showthread.php?t=2630085
d. http://forum.xda-developers.com/showthread.php?t=2537495
4. Tried above ROMs with kernels from here - http://forum.xda-developers.com/showthread.php?t=2292341 (v4.2.2 or v4.4 - depending on the ROM) and also the MF3 kernel (can't find the link)
But, irrespective of what I try, I still get stuck while loading the ROM - blank screen, not moving forward. Could you please shed some light on what I should try to do?
Thanks!
Click to expand...
Click to collapse
ROM's C and D didn't work because they're AOSP ROMs, and 4.4. You can't cross versions. Besides that, I'd get the safestrap 3.65 APK from our own safestrap thread to make sure you get the correct JFLTEATT version and the MF3 kernel modules which you need to flash after every ROM. What exactly is your process for flashing, and what slot are you flashing to?
DeadlySin9 said:
ROM's C and D didn't work because they're AOSP ROMs, and 4.4. You can't cross versions. Besides that, I'd get the safestrap 3.65 APK from our own safestrap thread to make sure you get the correct JFLTEATT version and the MF3 kernel modules which you need to flash after every ROM. What exactly is your process for flashing, and what slot are you flashing to?
Click to expand...
Click to collapse
Thanks for the prompt reply! Appreciate it. I did get the exact safestrap 3.65 APK from my JFLTEATT version.
I'm flashing into Slot 1. Size - 1GB, 1GB, 300MB. I'm not entirely sure what you mean by what process, by here goes - Factory Wipe, Flash ROM, Flash MF3/v4.2.2 Kernal, Wipe Dalvik/Cache, attempt to fix permissions (always fails with same message). Restart into slot 1.
Vishoka said:
Thanks for the prompt reply! Appreciate it. I did get the exact safestrap 3.65 APK from my JFLTEATT version.
I'm flashing into Slot 1. Size - 1GB, 1GB, 300MB. I'm not entirely sure what you mean by what process, by here goes - Factory Wipe, Flash ROM, Flash MF3/v4.2.2 Kernal, Wipe Dalvik/Cache, attempt to fix permissions (always fails with same message). Restart into slot 1.
Click to expand...
Click to collapse
I would try bigger partition sizes. Leave them at their defaults, because sizing them down likes to cause issues sometimes. Also, flashing that kernel does nothing as safestrap never touches the kernel partition. You do still need the MF3 module zip from the Safestrap thread however. Also, if you've previously flashed a ROM in the slot, you need to wipe the system in that slot too.
DeadlySin9 said:
I would try bigger partition sizes. Leave them at their defaults, because sizing them down likes to cause issues sometimes. Also, flashing that kernel does nothing as safestrap never touches the kernel partition. You do still need the MF3 module zip from the Safestrap thread however. Also, if you've previously flashed a ROM in the slot, you need to wipe the system in that slot too.
Click to expand...
Click to collapse
Thanks again for the prompt reply, I hope you don't mind me taking more of your time. But, I'm having a hard time finding "latest" ROMs for my version, could you point me to one? I've been scouring through Android Original Development, but they're all 4.3 and 4.4, versions you said I couldn't cross-install. Thank in advance!
DeadlySin9 said:
I would try bigger partition sizes. Leave them at their defaults, because sizing them down likes to cause issues sometimes. Also, flashing that kernel does nothing as safestrap never touches the kernel partition. You do still need the MF3 module zip from the Safestrap thread however. Also, if you've previously flashed a ROM in the slot, you need to wipe the system in that slot too.
Click to expand...
Click to collapse
I tried what you said, and it worked! With ROM (a), I'm now running into System UI ran into an error, problem. Still looking around.
Vishoka said:
I tried what you said, and it worked! With ROM (a), I'm now running into System UI ran into an error, problem. Still looking around.
Click to expand...
Click to collapse
Did you sign in to a google account at the initial setup? I know there's some issues involving that on the Google ROMs.

[ROM][5.0.2][TEST][LOLLIPOP][n7000]RESURRECTION REMIX LP 5.2.5

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

Categories

Resources