[Q] [help] Can't update CM11, install fails during boot - Nexus 4 Q&A, Help & Troubleshooting

I got CM11 on a Nexus 4, the version is 11.0-InstallerXNPQ08Q, core version is 3.40-cyanogenmod-g710ed60 and the compilation is 4.4.2 KOT49H.
I get the notification about a new version, hit install and when the process starts it restarts (so far so good) and then the install animation which lasts a second before it turns to the fail state and before I can read the error or anything it boots back to android/cyanogen.
Is anyone else having this problem? how did you solve it?

MGREX said:
I got CM11 on a Nexus 4, the version is 11.0-InstallerXNPQ08Q, core version is 3.40-cyanogenmod-g710ed60 and the compilation is 4.4.2 KOT49H.
I get the notification about a new version, hit install and when the process starts it restarts (so far so good) and then the install animation which lasts a second before it turns to the fail state and before I can read the error or anything it boots back to android/cyanogen.
Is anyone else having this problem? how did you solve it?
Click to expand...
Click to collapse
Flash stock image first .... then install Cyanogenmod ... hopefully u r not trying F2FS partition....

Ravzz_Sv said:
Flash stock image first .... then install Cyanogenmod ... hopefully u r not trying F2FS partition....
Click to expand...
Click to collapse
Wouldn't be easier to try flashing the latest CM11 zip from CWM without a data wipe? what are the risks?

MGREX said:
Wouldn't be easier to try flashing the latest CM11 zip from CWM without a data wipe? what are the risks?
Click to expand...
Click to collapse
Have you tried downloading the latest CM11, copying it over to the phone, and dirty flashing from a custom recovery? Dirty flashing may cause some apps to stop functioning as some apps will not work under 4.4.4.

Related

[Q] cant install android 4.4 on my defy plus

Hi,
My phone detail --
MB526, have android 4.1.2 and have rom -CM-X MIG 2.02
I have two issues :-
1. my wifi disconnects after some time and i have to disable it for long time and then enable it to work ,so any way to solve it -on my other phone
there is no issue about wifi atall.
2.I been trying to install kitkat 4.4 on my defy plus but always fails to do in recovery with message like this:--
error in /sdcard/.....zip, installation aborted"
tried both recoveries but now on touch TWRP -- any idea ?
Thanks
vaibhavm said:
Hi,
My phone detail --
MB526, have android 4.1.2 and have rom -CM-X MIG 2.02
I have two issues :-
1. my wifi disconnects after some time and i have to disable it for long time and then enable it to work ,so any way to solve it -on my other phone
there is no issue about wifi atall.
2.I been trying to install kitkat 4.4 on my defy plus but always fails to do in recovery with message like this:--
error in /sdcard/.....zip, installation aborted"
tried both recoveries but now on touch TWRP -- any idea ?
Thanks
Click to expand...
Click to collapse
I tooo faced the same problem at the beginning with cm11 (cm-11-20140117-NIGHTLY-mb526) by quarx, though I was able to install cm11(cm-11-20131229-NIGHTLY-mb526) by quarx successfully.... Im a noob to this flashing stuff still managed and understood a bit of this procedure... I believe I read this some where on this forum that if you want to install ***cm11 (cm-11-20140117-NIGHTLY-mb526)*** then you need to go back to the custom rom first then from there you can install , though I'm not 100% Sure and afraid to do any experimentation with my Defy+.... As of now Im on
"Android 4.3.1"
Kernel 2.6.32.9-Aerokernel
10.2-20131030-NIGHTLY-mb526
I am facing almost the same problems as yours "Installation failed" as if there is a problem with the zip file which I'm sure of that isnt the case :/
Please somebody help the noobs...!!!
Thank you.
imdroid87 said:
I tooo faced the same problem at the beginning with cm11 (cm-11-20140117-NIGHTLY-mb526) by quarx, though I was able to install cm11(cm-11-20131229-NIGHTLY-mb526) by quarx successfully....
Thank you.
Click to expand...
Click to collapse
Did you update recovery?
Link for that is in OP of http://forum.xda-developers.com/showthread.php?t=2515036
becer said:
Did you update recovery?
Link for that is in OP of http://forum.xda-developers.com/showthread.php?t=2515036
Click to expand...
Click to collapse
Yes I did the recovery Update and then rebooted and then tried installing cm11 (cm-11-20140117-NIGHTLY-mb526) but unfortunately it failed "Aborted"
imdroid87 said:
Yes I did the recovery Update and then rebooted and then tried installing cm11 (cm-11-20140117-NIGHTLY-mb526) but unfortunately it failed "Aborted"
Click to expand...
Click to collapse
Try maybe installing from scratch (starting with original sbf).
I reinstalled Kitkat on my Defy+ tonight - sbf, rooted sbf, 2ndInit, cm-10-20131030, recovery update and then 140120.
becer said:
Try maybe installing from scratch (starting with original sbf).
I reinstalled Kitkat on my Defy+ tonight - sbf, rooted sbf, 2ndInit, cm-10-20131030, recovery update and then 140120.
Click to expand...
Click to collapse
Buddy "becer" can u please guide me step wise to go back to the Stock Rom then 2init what ever it is I dont understand a thing
I know what stock Rom is but don't know how to degrade to the stock rom from 4.3.1 and how to install this 2init thing
would be a great help if you could guide me through the procedure step wise
Thank You.
1. root with Framaroot http://forum.xda-developers.com/showthread.php?p=37508806
2. Install 2nd init http://forum.xda-developers.com/showthread.php?p=12837303
3. Update recovery with this http://forum.xda-developers.com/showthread.php?p=48501247
4. Install CM11
Sent from my MB526 using Tapatalk
cyrusct82 said:
1. root with Framaroot http://forum.xda-developers.com/showthread.php?p=37508806
2. Install 2nd init http://forum.xda-developers.com/showthread.php?p=12837303
3. Update recovery with this http://forum.xda-developers.com/showthread.php?p=48501247
4. Install CM11
Sent from my MB526 using Tapatalk
Click to expand...
Click to collapse
Buddy Im already running cyanogenmod on my defy+ and in the second link what you gave for installing the 2ndinit Recovery it says:
DO NOT INSTALL THIS IF ARE YOU ALREADY RUNNING CYANOGENMOD. That ROM already has bootmenu pre-installed, and you'll probably end up having to flash an SBF file to recover your phone.
NOTE: You need ROOT installed on your Defy to use this application.
What should I do ???
I will try from start by using original sbf file using RSD and then CM11 and updating recovery after that Kitkat ,btw can you mention which ROM you tried because i tried these 2 earlier --> omni-4.4.2-20140117-mb526-HOMEMADE .zip and AOSPA 4.0+ PARANOIDANDROID [beta]
Kitkat 4.4.2 KOT49H android-4.4.2_r1.
Also can some1 help me with my wifi frequently disconnection problem too please .
vaibhavm said:
I will try from start by using original sbf file using RSD and then CM11 and updating recovery after that Kitkat ,btw can you mention which ROM you tried because i tried these 2 earlier --> omni-4.4.2-20140117-mb526-HOMEMADE .zip and AOSPA 4.0+ PARANOIDANDROID [beta]
Kitkat 4.4.2 KOT49H android-4.4.2_r1.
Also can some1 help me with my wifi frequently disconnection problem too please .
Click to expand...
Click to collapse
I tried this
Mokee
"MK43.1-jordanplus-201312040138-NIGHTLY"
with Gapps
gapps-jb+-20130730_defy-minimal
and
update-recovery
CM11 by Quarx
"cm-11-20131229-NIGHTLY-mb526"
with Gapps
1-16_GApps_Standard_4.4.2_signed
They both worked for me but unable to install the latest one.... I'm trying the method just mentioned by the senior member but unable to root again using framaroot as its showing me this error
"Half-Success :-/ ... system partition is read-only, use local.prop trick. Reboot your device and use adb to see if it run as root"
I don't know what to do now :silly:
imdroid87 said:
I tried this
Mokee
"MK43.1-jordanplus-201312040138-NIGHTLY"
with Gapps
gapps-jb+-20130730_defy-minimal
and
update-recovery
CM11 by Quarx
"cm-11-20131229-NIGHTLY-mb526"
with Gapps
1-16_GApps_Standard_4.4.2_signed
They both worked for me but unable to install the latest one.... I'm trying the method just mentioned by the senior member but unable to root again using framaroot as its showing me this error
"Half-Success :-/ ... system partition is read-only, use local.prop trick. Reboot your device and use adb to see if it run as root"
I don't know what to do now :silly:
Click to expand...
Click to collapse
Mine sbf is rooted alredy so maybe try it first then go to CM10 .
its DEFYPLUS_U3_4.5.1-134_DFP-231_CEE_ROOTED_No_Signed.rar
downloaded it earlier from here only.
I have tried Mokee, but direct return to Quarx compilation made big stability problems too. Solution was to flash with original rom, then rooted one, 2ndInint and Quarx cm10, then cm11.
As I had Android 2.3.6 (3.4.5.1 - 231), I used these roms - http://forum.xda-developers.com/showthread.php?t=1542956.
It is very important to wipe data and cache just after first, original flash - otherwise you will have infinite boot loop and cannot run phone.
Look at http://forum.xda-developers.com/showthread.php?t=966537 too.
becer said:
I have tried Mokee, but direct return to Quarx compilation made big stability problems too. Solution was to flash with original rom, then rooted one, 2ndInint and Quarx cm10, then cm11.
As I had Android 2.3.6 (3.4.5.1 - 231), I used these roms - http://forum.xda-developers.com/showthread.php?t=1542956.
It is very important to wipe data and cache just after first, original flash - otherwise you will have infinite boot loop and cannot run phone.
Look at http://forum.xda-developers.com/showthread.php?t=966537 too.
Click to expand...
Click to collapse
Im phone is f***** , what I did is install this framaroot and installed rootchecker..... I tried to do the rooting using "installsu" and then clicked Gilmo and it gave me this message:
“Half-Success :-/ … system partition is read-only, use local.prop trick. Reboot your device and use adb to see if it runs as root”
then I restarted my phone and check with root checker and found its saying its saying Root access successful and then I wondered which I suppose I shudnt have wondered :crying: to user framaroot and do the "unroot" and again restarted , and now after restart I tried to do the regular thing wipe cache ,Dalvik , Data and the phone is not even mounting them its sayin
E: Can't mount /cache/recovery/command etc
Im able to open the android 4.1.2 (Jb - quarx)
but not able to install a thing in my internal memory coz I messed up bad with the partition table bad:crying:
I tried to fix it through this
http://forum.xda-developers.com/showthread.php?t=1759558&highlight=status+0
but no luck :/
I been able to flash and run cm-10.2-20140120-NIGHTLY-mb526.zip thts-- android 4.3 ,so do factory reset and go here http://quarx2k.ru/roms/defy-cm10.2/ --get latest build .
my problem is only wifi disconnects frequently -seems on this working fine ,will check it for few days ,anyway 4.4 will still have bugs so better be on some lower version.
For the opening post: the first issue is a known bug in 4.4, I did not know it is wrong even in 4.1...
vaibhavm said:
I been able to flash and run cm-10.2-20140120-NIGHTLY-mb526.zip thts-- android 4.3 ,so do factory reset and go here http://quarx2k.ru/roms/defy-cm10.2/ --get latest build .
my problem is only wifi disconnects frequently -seems on this working fine ,will check it for few days ,anyway 4.4 will still have bugs so better be on some lower version.
Click to expand...
Click to collapse
Oooh in that case even if I can install the latest Cm11 by Quarx then I should not be doing it as the problem your saying about the wifi getting disconnecting frequently is not acceptable :silly:
anyways just fighting with my Defy+ as of now , Installing the Stock sbf on it as I bricked the phone
So the new Question arises what CM version is more stable or can I ask whose performance is Better in terms of speed.... As I don't mind with Features but I dont want Lags.... Previously I installed 4.2.1 I Suppose and installed the mininal gapps and was have around 240mb free of RAM...
is that good ???
Thank you for the responses buddies :fingers-crossed:
imdroid87 said:
Oooh in that case even if I can install the latest Cm11 by Quarx then I should not be doing it as the problem your saying about the wifi getting disconnecting frequently is not acceptable :silly:
anyways just fighting with my Defy+ as of now , Installing the Stock sbf on it as I bricked the phone
So the new Question arises what CM version is more stable or can I ask whose performance is Better in terms of speed.... As I don't mind with Features but I dont want Lags.... Previously I installed 4.2.1 I Suppose and installed the mininal gapps and was have around 240mb free of RAM...
is that good ???
Thank you for the responses buddies :fingers-crossed:
Click to expand...
Click to collapse
vaibhavm I have installed this 4.4.2 Android Panroid
http://forum.xda-developers.com/showthread.php?t=2576930
[AOSPA 4.4.2 KOT49H] [Beta] Defy(+) PARANOIDANDROID 4.0+ [18/01/2014]
Working awesome fast and seems stable until now and I have gone through some reviews about it on defy+ on that forum even they are giving it positive reviews..
Check it out for sure:good::fingers-crossed:

Installation Aborted - Status 7 (expected 5 arguments, got 4)

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.

[Q] Please help mates, I got a problem with a kernel!

Hello everybody, I was wondering if you could help me with this problem.
I got an lg g2 D802, I was on the official kit kat rom with knock code, with Dorimanx kernel 7.1, everything was ok, Im using the right baseband from kit kat, but I changed the rom to Paranoid Android new version, doing a full wipe/ clean install. But the first hours of use I noticed that my phone was overheating, so I started to read bout that, and I realize that Dorimanx kernel wasn't for PA Roms, only for stock based, so I decided to change my kernel, I wasn't sure what kind of kernel I need, so I search a bit and a page says that PA Roms was AOSP based, then I downloaded Furnace Kernel 2.5.1, AOSP version, flashed it and when the phone reboots, it repeatedly say: com. android.phone process has stopped. So technically I wasn't able to do anything. I boot into recovery again and try to flash stock kernel for kit kat, and when the phone tries to boot, an lg logo appears and say: Security error. I reboot into recovery once again and try to re- flash Dorimanx kernel, because it was late night and I wanted to sleep, so I though, just need the phone to boot and tomorrow I will change the kernel to a correct one, but when the phone tries to boot, got stuck in lg logo and the led flashing, since that, I ve been trying to flash so many kernels, included furnace stock version and cm version, with no result, I tried too cloudyfa, auxilium, stock, PAEK and nothing seems to work.
I did my backup when I flashed PA, but cause first hours seemed to be ok , I deleted it for storage reasons, so now i cant restore any backup, and I know doing a full wipe /clean install again will solve this problem, but I don't want to lose all my files and photos and stuff from years ago, and I know that is possible to flash a kernel and boot with this rom because when I flash furnace AOSP the phone turn on and show my lock screen and desktop, but the com.android.phone has stopped problem appears and don't let me do anything.
So, I ask to you: What can I do to flash the right kernel and don't lose my stuff?
Thank you for your answers and sorry for my bad English.
@Delintg2 Why don't you just flash paranoid android again? Flashing the rom changes the kernel as well
Art Vanderlay said:
@Delintg2 Why don't you just flash paranoid android again? Flashing the rom changes the kernel as well
Click to expand...
Click to collapse
Ive tried too, with no result, stuck o lg logo, and now the adb sideload say sending package and when 100% nothing happens on the phone :S
Delintg2 said:
Ive tried too, with no result, stuck o lg logo, and now the adb sideload say sending package and when 100% nothing happens on the phone :S
Click to expand...
Click to collapse
You have to flash the sideload zip when that's done. If you still can't boot into your ROM then its back to stock town for you I'm afraid. We've all been there :highfive:
Art Vanderlay said:
You have to flash the sideload zip when that's done. If you still can't boot into your ROM then its back to stock town for you I'm afraid. We've all been there :highfive:
Click to expand...
Click to collapse
Ok backing to stock :S, ty anyway m8

[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

Boot loop on all roms URGENT HELP NEEDED

Help? Every rom seems to give me boot loop after install and a couple of roms get to 50 percent installing then TWRP reboots (mostly pixel rom and rr does this)
I also tried nougat and marshmellow stock roms and they both give drk check error, I flash super su like I used to do to fix drk check error and it just boot loops now
All the roms I used to be able to install fine now just boot loop
Pixel rom
Fast and famous rom
Infinity rom
Lineage os
Resurrection remix
All of these roms above I have had on my phone at some point and all worked fine now I just get boot loop after installing them.
14 views and no one can help me?
Still have no phone as I still cannot boot.
are you using a correct kernel or twrp for your device
blackbravo said:
are you using a correct kernel or twrp for your device
Click to expand...
Click to collapse
I'm not sure my device is G928F Can you link me to the correct kernel? And I think the TWRP is 2.7.8 or something like that
download twrp here: https://twrp.me/samsung/samsunggalaxys6edgeplus.html
flash over odin
and choose one rom with kernel included, because you must have the correct kernel for the rom you install
blackbravo said:
download twrp here: https://twrp.me/samsung/samsunggalaxys6edgeplus.html
flash over odin
and choose one rom with kernel included, because you must have the correct kernel for the rom you install
Click to expand...
Click to collapse
Okay so tried a couple roms and they all crash like sometimes at 10 percent sometimes around 50 but they always crash and TWRP restarts. Something to do with the aroma installer roms, tried multiple different TWRP versions and nothing likes the aroma installer roms, any suggestions? Also tried multiple nougat and marshmellow roms and I get drk check failed everytime.
I used to be able to flash SuperSU zip and it would fix drk check failed but it no longer does
Can someone please give me any suggestions at all as I would like to use my phone again
jacksskinz said:
Okay so tried a couple roms and they all crash like sometimes at 10 percent sometimes around 50 but they always crash and TWRP restarts. Something to do with the aroma installer roms, tried multiple different TWRP versions and nothing likes the aroma installer roms, any suggestions? Also tried multiple nougat and marshmellow roms and I get drk check failed everytime.
I used to be able to flash SuperSU zip and it would fix drk check failed but it no longer does
Can someone please give me any suggestions at all as I would like to use my phone again
Click to expand...
Click to collapse
And install stock ROM via Odin? Not working ?
blackbravo said:
And install stock ROM via Odin? Not working ?
Click to expand...
Click to collapse
It works but when booting I get DRK CHECK FAILED
blackbravo said:
And install stock ROM via Odin? Not working ?
Click to expand...
Click to collapse
Okay I've narrowed it down to system
When installing any rom it seems to crash when it gets to installing system and then TWRP reboots
I've checked that system is mounted which it is
Also it seems system is at EXT4 file system
Dunno if that's good or bad but either way every rom is crashing when it gets to installing system
Any ideas?
jacksskinz said:
Okay I've narrowed it down to system
When installing any rom it seems to crash when it gets to installing system and then TWRP reboots
I've checked that system is mounted which it is
Also it seems system is at EXT4 file system
Dunno if that's good or bad but either way every rom is crashing when it gets to installing system
Any ideas?
Click to expand...
Click to collapse
Can someone help please before I buy a new motherboard? Roms crash when it starts installing system
Download stock nougat, and flash it, but make sure csc is selected, and not home_csc, because csc will put phone to real stock settings.
Flash the latest stock firmware for your *correct variant*. Sammobile's downloads are kind of slow, but I've never had issues with any of their firmwares. Install that with Odin and your phone on download mode. I would recommend to use HOME CSC, just to make sure it is completely clean. After you set it up, flash your *correct variant's* TWRP via Odin. To save yourself some time, you can boot straight into TWRP when it finishes installing by pressing home + power + volume up when the screen goes out. From here you can load ROMs from a PC via USB. Good Luck and Happy Flashing!

Categories

Resources