Database Users

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

[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:

[GUIDE] [SOLVED] HOW TO FLASH CM11 ON BRAVO (Previously "Cm11 Issue, Status 0 Error")

[GUIDE] [SOLVED] HOW TO FLASH CM11 ON BRAVO (Previously "Cm11 Issue, Status 0 Error")
So, I tried to flash CM11 for the MB520 Bravo, found in this post:
http://forum.xda-developers.com/showthread.php?t=2515036
So I copy the ROM .zip to the SD card in my Bravo, and I reboot into CWM Recovery version 5.0.3.9, with the name "CyanogenDefy Recovery v5.0.3.9-jordan" on the top of the screen. This version of recovery came from josuearisty's one click tool for rooting and putting a recovery on the MB520 Bravo, which can be found here:
http://forum.xda-developers.com/showthread.php?t=1559109
I factory reset/clear cache like I know I am supposed to when flashing a custom ROM, but when I select the "Install zip from sd card" option and select the CM11 MB520 Nightly to flash, it gives me this:
Finding update package...
Opening update package...
Installing update...
E:Error in /sdcard/cm-11-20140407-NIGHTLY-mb520.zip
(Status 0)
Installation aborted.
So then as I read on further in the CM11 install page, it says this: "For CM10,10.1,10.2 < 07.11.13 users: To install KitKat, need update recovery. Do not forget reboot, after install recovery. http://defy.bytekiste.de/cm11-nightl...e-recovery.zip". The thread is for the DEFY+ according to the title, but since I see there's also a Bravo download link, I assume that this means that I should install this updated recovery as well, since I am running the stock rooted 2.2.1, which is in fact "less than" 10.x or 4.x. I select the same "Install zip from sd card" option, and the same Status 0 is presented to me.
Then I go and try putting on CM10.x first, because then according to the thread's instructions I won't have to install this updated recovery if I am running that currently. I find a link for CM10.2 for the Bravo here:
http://forum.xda-developers.com/showthread.php?t=1779324
I download it, do the same install method, and I STILL GET A STATUS 0 saying it is unable to flash the zip!
Now I've done some research, and I THINK the status 0 means the zip is not compatible with my phone. I could see that with the updated-recovery.zip, but I don't see why that is showing up for the ROM's themselves because they are in fact made for the mb520.
Can someone please tell me what I am doing wrong, and if possible post a set of step-by-step instructions as to how I can go installing CM11 on my MB520 Bravo? Thanks.

*BUMP*
UPDATE: I seemed to get around the Status 0 issue in CM10.2 so far. First, I went from 2.2.1 to CM9 4.0.4. Then, I went from CM9 to CM10.1 in quarx2k's "archive" folder on his website. This updated my recovery to TWRP 2.6.0.0. From this new TWRP, I was able to flash the latest 10.2 nightly CM rom. I will keep this posted on how things go, in case anyone out there is actually following this

*BUMP AGAIN, PROBLEM SOLVED*
I got CM11 finally running on the Bravo. Here's the steps I took to get it on there. Some of these steps may be unnecessary, but I'm just going to list EXACTLY what I did in case all of these steps really are necessary:
1) I started out with stock 2.2.1. I rooted it, and used josuearisty's tool for one click root and recovery just to put recovery on it.
2) I flashed a build of CM9 from quarx2k's website. Here is a direct link to download it. Flashing this ROM also updated my cwm recovery. HOWEVER, this new version of recovery had scrolling issues with the volume rocker, so I just rebooted and pressed the vol. down button at the blue flashing LED light to boot into the boot menu. From there, I select to go to recovery, but instead of selecting "Custom Recovery" I select "Stable Recovery". This takes me back to the older recovery I got with the one click tool.
3) I flashed one of quarx2k's builds of CM10.1, which you can get for yourself here. Doing this updated my recovery again. It went from CWM 5 to TWRP 2 (I believe it was 2.6.0.0).
4) I flashed a CM10.2 build for the bravo from quarx2k, which I got from here. This updated my recovery YET AGAIN, to TWRP 2.6.3.0.
5) From here, I was able to flash the update-recvery.zip that is mentioned in the CM11 topic. I don't think this was necessary, because when I then booted into recovery again after flashing the update-recovery.zip, the version number for TWRP still read 2.6.3.0, the exact same as last time. But I just did it anyway to be safe. Here is a direct download link to the update-recovery ZIP mentioned on quarx's CM11 thread.
6) FINALLY, I flash the CM11 nightly zip from quarx2k's website. I get an error, but this time it's not a status 0 error, this tells me that the ZIP is not compatible with my device.
7) I give myself a facepalm, and take 3 deep breaths. "All hope is lost..." I think to myself.
7.5) A GOOGLE SEARCH TELLS ME THAT ALL HOPE IS NOT LOST!!! (that's supposed to signal you to keep reading)
8) Turns out, there is a way to disable the device compatibility check. So what I did was copy the CM11 zip to my pc, and unzip all of its contents. I go to META-INF\com\google\android\, and add a .txt ending to the "updater-script" file, which allows me to open it with Notepad++. It is possible to edit this with plain old Notepad in Windows, but it doesn't format the code very neatly like Notepad++ does. If you open the file in Notepad and Notepad++ and compare them you will see what I mean. Anyway, the line of code that reads...
assert(getprop("ro.product.device") == "mb520" || getprop("ro.build.product") == "mb520" || abort("This package is for \"mb520\" devices; this is a \"" + getprop("ro.product.device") + "\"."); (ignore that winking face in the line of code, that is supposed to be a "; )" but without the space between them.)
... was the one I deleted from the updater-script file. This should be the first line of code. I save, exit Notepad++, and remove the .txt ending from the updater-script so that it returns to an unknown filetype. Now, I take the META-INF, system, and file_contexts files that came from the original CM11 ROM zip and I create a NEW ZIP with all of the NEW files and folders.
9) I reboot to TWRP with the ROM zip copied to my phone's SD card, and I flash the new, fixed ROM zip. "Installation completed."
10) My Bravo is rebooted, it boots up, and i get a "Welcome!" bubble in my brand-new homescreen in KitKat
11) I nearly cried. Seriously.
So looking back I think it was really the recovery that was the issue for the Status 0 problem, and the only real way to update the recovery and solve the Status 0 problem is by flashing all these ROMs in the order I mentioned, but that's as far as I know, there may be a better and quicker way to do this that I just don't know about.
So basically this thread turned into a how-to. I wanted to post the instructions here because on the CM11-for-the-Defy-and-Bravo topic did NOT have any instructions whatsoever for flashing the Bravo CM11 build on the Bravo. If anyone has questions about what I wrote, then you can certainly post them below and I'll respond to them as soon as I can, and I'll answer them to the best of my abilities.

Thanks for the Guide
I just wanted to thank you for this well-written, step-by-step guide. I haven't tried it since I'm a beginner and need some more reading to do. I'm glad you overcame those issues, though.
Anyway, I wanted to ask you how smooth it ran and if it was worth it. Also I'm starting with Android 2.1, would that make a difference?

Gastnow said:
I just wanted to thank you for this well-written, step-by-step guide. I haven't tried it since I'm a beginner and need some more reading to do. I'm glad you overcame those issues, though.
Anyway, I wanted to ask you how smooth it ran and if it was worth it. Also I'm starting with Android 2.1, would that make a difference?
Click to expand...
Click to collapse
I think you should upgrade to 2.2.1 to make sure the one-click tool works with it because I do not know if the one click root and recovery works with 2.1. Upgrade to 2.2.1 just to be safe.
Sent from my SAMSUNG-SGH-I847

Thanks for the guide
Appreciate the work. What gapps are you using.

Doesn't have much support
I tried it. A lot slower then CM7.2 and very difficult to get my most important apps working (and I don't use many).
I would not recommend it for a daily (as mentioned on the Defy link). But, has potential if a developer takes up the task.

ilikepcs said:
Appreciate the work. What gapps are you using.
Click to expand...
Click to collapse
ilikepcs said:
I tried it. A lot slower then CM7.2 and very difficult to get my most important apps working (and I don't use many).
I would not recommend it for a daily (as mentioned on the Defy link). But, has potential if a developer takes up the task.
Click to expand...
Click to collapse
The gapps for this KitKat ROM can be found here. This came from the 4.4 thread:
QUARX2K'S KITKAT GAPPS
I used this as a daily driver for a little bit, until an update (I believe was from April 10th) with the Android 3.0 kernel broke the Camera. Whenever you would try to open the camera it would say "Can't connect to Camera". I'm not sure if this issue was fixed since then, and I know the versions before this had the 2.x kernel which was fine with the camera. I lent my Bravo to a family member because their phone broke, so I can't really do anything with the phone because it is not in my possession.
Anyway, check back at this thread and the link that it gives to the Bravo version of 4.4 to keep up with the latest version. This thread does not give a change log for the BRAVO version, but I assume that it's basically the same as the main version that the majority of the thread is talking about:
ANDROID KITKAT FOR DEFY AND DEFY PLUS (ALSO FOR THE MOTOROLA BRAVO)

Help please
The procedure to install cm11 after October 1 is the same? Or did it change? @jasonmerc
Quarx on their website does not mention cm10 and cm10.1
Sent from my mb520 using XDA Free mobile app

@jasonmerc
You are not using CM11 anymore? Do you know if the camera problem has been solved (I assume that with the 2.6.x kernel the original motorola camera drivers were used which most likely do not work with a 3.x kernel)? What was your general experience (especially regarding performance) with CM11 on the Bravo?
Thanks,
Markus

oldschool63 said:
@jasonmerc
You are not using CM11 anymore? Do you know if the camera problem has been solved (I assume that with the 2.6.x kernel the original motorola camera drivers were used which most likely do not work with a 3.x kernel)? What was your general experience (especially regarding performance) with CM11 on the Bravo?
Thanks,
Markus
Click to expand...
Click to collapse
Its been forever since I've used my Bravo let alone CM11. From what I can remember the new CM11 was EXTREMELY FAST compared to other ROMs. The only issue was the camera.
Sent from my LG-D415 using XDA Free mobile app

can you create a backup of it because some of the downloads don't work i got cm 9 4.0.4 im 12 and i ran into
a problem on cm 10.1 i cannot download it or flash it thx

[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

Help me,, Cannot boot in to recovery

Please help needed!!
I'm stuck here for 3 days
Ok I'm going to tell everything I did,,
My Gionee E7 is indian version.
First I rooted my phone with kingo Root.
Than I flashed CWM chinese version.
I upgraded my system to kitkat and changed the recovery to stock.
I used it for a week than some how my music player and gallery were corrupted.
I don't have any rom so I download one but it was in chinese, flashed it to my gionee. than after rooting,,
I flashed the CWM, same I flashed weeks ago
Here my problem started :crying:
The CWM is not starting. I used recoery tool to boot into recovery after boot up it shows black screen. I used every method holding Vol+ and power button but the same result.
than I tired to get back to my stock recovery but it does the same.
flashed many times both recoveries but didn't worked.
I searched a lot and find a TWRP. I flashed it and wow it worked Finally I can boot into recoery mode.
Now I find the Nandroid backup of indian version. I made it a zip and flashed it through twrp.
My phone is back to indian version but its slow, not too much but its slow; camera, gallery and other apps take some time to open. I can't make or rcv phone calls. Now what i did is download the update form System update.
Now i got kitkat rom.zip but twrp failed to install it.
Some one on the internet was saying that its the problem with my Kernel. I have the latest kernel so CWM won't work cuz it uses old kernel and display drivers.
My
android version is 4.2.2
Kernel version is 3.4.0-svn2155
I also got TWRP for lolipop,
and I patched binary_update in my kitkat rom too but TWRP can't flash it
Thats my whooooolllleeeee story. "
I got stuck with this for almost 3 days now I'm damn tired can't do it anymore plz help :crying::crying::crying:

I figured it out by myself
Ok guyz didn't get any help so I figured it out by my self.
I'm posting it here so if anyone gets stuck like me could solve his issue
I used GNQC Download tool and flashed the whole firmware of my cell including, kernel, rom, recovery, boot everything.
Now I'm back to stock indian rom (jellybean) with stock recovery and now I'm going to upgrade to kitkat
I'm new user so I can't posts links just replace the (dot) in the link,
First download stock firmware of Gionee e7 in following link, GNQC download tool and drivers also included in this zip:
www(dot)androidxda.com/download-gionee-stock-rom-models
Just unzip it and follow the instructions on this site:
www(dot)androidxda.com/gnqc-downlod-tool
I didn't slept last night bcuz of this mess now going to sleep whole day :silly:
Goodnite and bless you all :angel:

AkashX4686 said:
Ok guyz didn't get any help so I figured it out by my self.
I'm posting it here so if anyone gets stuck like me could solve his issue
I used GNQC Download tool and flashed the whole firmware of my cell including, kernel, rom, recovery, boot everything.
Now I'm back to stock indian rom (jellybean) with stock recovery and now I'm going to upgrade to kitkat
I'm new user so I can't posts links just replace the (dot) in the link,
First download stock firmware of Gionee e7 in following link, GNQC download tool and drivers also included in this zip:
www(dot)androidxda.com/download-gionee-stock-rom-models
Just unzip it and follow the instructions on this site:
www(dot)androidxda.com/gnqc-downlod-tool
I didn't slept last night bcuz of this mess now going to sleep whole day :silly:
Goodnite and bless you all :angel:
Click to expand...
Click to collapse
Hello my friend, please help me.
I am trying to flash stock inidan rom 4.2 but.. I installed all CWM for E7 found on the internet and I am getting black screen. I managed to Install TWRP but TWRP cannot flash the rom that I need to flash. I flashed a chinese 4.2 but is piece of garbage..
gngc-download-tool said that the com port is closed.
I have windows 64 is this the problem causing gngc not working?

No its not, it is working on 64bit windows very well.
In TWRP factory reset and format system and data, than install
Chinese 4.2 ROM. After that boot it and try it again.
It should work!

bllkarv said:
Hello my friend, please help me.
I am trying to flash stock inidan rom 4.2 but.. I installed all CWM for E7 found on the internet and I am getting black screen. I managed to Install TWRP but TWRP cannot flash the rom that I need to flash. I flashed a chinese 4.2 but is piece of garbage..
gngc-download-tool said that the com port is closed.
I have windows 64 is this the problem causing gngc not working?
Click to expand...
Click to collapse
For me...problem!

there´s a cwm recovery that flashes over the kernel...
i flashed it and than i was unable to go to recovery, every time i tried the phone power off
Solution: Flash the stock boot.img
Use the file according to the Android version...

Help
I just rooted my gionee elife e7. Flashed the chinese recovery which seemed to be the only one which would be compatible. But, while changing a few setting using pimp my rom, the software just stopped working. Errors keep showing up on the screen - "system.ui is not working", "android app is not working", I cannot even go the settings because "settings is not working". Third party apps still seem to work, so, whatsap and stuff continue to function. Doing a factory reset or flashing firmware again seem to be the only viable option.
But, when I try to load up the bootloader using the power and volume keys, it gets stuck on the screen showing the gionee logo and it reads 'fastboot mode' in the bottom left hand side corner. So,
a. can you offer any advice which may be useful ?
b. can you share the link from where you got a TWRP recovery which will work on the Elife ?
c. do you have any idea what exactly went wrong here ?
Any help you can provide will be appreciated because, it's my mausi's phone and I will have a very tough time explaining what really went down here.
Regards,