Hi all,
I started playing with my Samsung Galaxy Ace and would want at some point to install CyanogenMod on it.
An issue that arise is that I have the GT-S5830D variant (Telus, TLKI4).
To flash the recovery, I downloaded recovery-clockwork-4.0.0.9-galaxyace.img from http://download.clockworkmod.com/recoveries/ and tried to use "flash_image" as recommended on CyanogenMod's wiki, but flash_image fails. I think flash_image tries to access /proc/mtd which is non-existent on the GT-5830D while present on other GT-5830 variants.
So I used recovery-clockwork-5.0.2.6-galaxyace-fix.zip from http://forum.xda-developers.com/showthread.php?p=18178563#post18178563 but this failed too. Looking at the updater-script in it showed an assert against certain models. I thus added mine to the assert, repackaged and resigned it. It flashed fine.
Before installing CM 7.2.0-RC1, I want to make sure I wont brick my phone. Looking at its updater-script, I see it's writing "boot.img" to "boot". My guess is that "boot" is a partition, but since the GT-5830D seem to be different enough, I wanted to verify first.
So my question is, does anybody knows the exact difference between the GT-5830D and any other GT-5830 variants??
Thanks a lot!!
The assert thingy allows you to specify what model this one should be flashed with .
It has no real effect .
Herpderp Defy.
Ok thanks.
The assert is there to protect the user from installing a rom on a different phone. The assert needs to be strict so the rom is installable only on the supported phone, but not too strict as to prevent variants of the phone...
I was just unsure as to if the S5830D was enough the same as the S5830 so that even if the assert passes, flashing wouldn't brick the phone.
Yesterday, I installed CM 7.2.0-RC1 (da26c44f36032e202e7dd21c13bf14b7 from here get.cm/?device=cooper) successfully. The assert passed fine.
I must say I am deeply impressed by CM compared to stock!
Issues I've found:
Torch does not work. The application stays open, crashes all the time and restart. Only way to disable it is restarting.
Screen does not turn off during conversation. Proximity sensor not working?
"Menu" and "Back" buttons kind of randomly lights up for a couple of seconds every couple of minutes.
These are known issues though. Even the camera works!
Thanks CM dev and supporters
After hours of searching, you have been the first person ive found that has confirmed cyanogen definitely works on the 'D'.
have you had any other problems come up on the phone?have you managed to flash the stable version? im fairly new to this, so trying not to brick my phone on the first go.
i had gotten as far as rooting and cwm, but couldnt get the stable rom to install (status 7 jobbie)
if this does work, is there a step by step guide to change the assert within the rom?
cheers
clous
Clous87 said:
After hours of searching, you have been the first person ive found that has confirmed cyanogen definitely works on the 'D'.
have you had any other problems come up on the phone?have you managed to flash the stable version? im fairly new to this, so trying not to brick my phone on the first go.
i had gotten as far as rooting and cwm, but couldnt get the stable rom to install (status 7 jobbie)
if this does work, is there a step by step guide to change the assert within the rom?
cheers
clous
Click to expand...
Click to collapse
Why are you digging up old threads......
Sent from my Jelly Beaned Ace
erm... thought it was pretty well explained.
Feel free to suggest a newer one that i can ask my question in...
Clous87 said:
erm... thought it was pretty well explained.
Feel free to suggest a newer one that i can ask my question in...
Click to expand...
Click to collapse
Just create a new thread...
You don't have to post your problem in another thread...
Clous87 said:
After hours of searching, you have been the first person ive found that has confirmed cyanogen definitely works on the 'D'.
have you had any other problems come up on the phone?have you managed to flash the stable version? im fairly new to this, so trying not to brick my phone on the first go.
i had gotten as far as rooting and cwm, but couldnt get the stable rom to install (status 7 jobbie)
if this does work, is there a step by step guide to change the assert within the rom?
cheers
clous
Click to expand...
Click to collapse
As long as you don't mess up your bootloader and have a working Odin install, it's pretty hard to completely brick an Ace. And yeah, don't necro old threads please.
Clous87 said:
have you had any other problems come up on the phone?have you managed to flash the stable version?
Click to expand...
Click to collapse
All issues I had are now fixed. Cyanogenmod 7.2.0 is working as expected, no problem. Only 3 issues remain open for the Ace:
http ://code.google.com/p/cyanogenmod/issues/list?can=2&q=model=cooper&colspec=ID%20Type%20Status%20Version%20Model%20Network%20Owner%20Summary%20Stars%20Priority
There are some nightly builds but more often then not they are translation fixes. See this url for some sort of changelog:
http ://changelog.bbqdroid.org/#cooper/cm7/next
Clous87 said:
if this does work, is there a step by step guide to change the assert within the rom?
Click to expand...
Click to collapse
The assert does not fail on my S5830D when flashing. I think changing the assert is as simple as extracting the .zip file, editing the META-INF/com/google/android/updater-script (see the top for the assert) and finally re-zip. Note that I haven't tried this so be careful not to brick your phone...
nbigaouette said:
All issues I had are now fixed. Cyanogenmod 7.2.0 is working as expected, no problem. Only 3 issues remain open for the Ace:
http://code.google.com/p/cyanogenmo...on Model Network Owner Summary Stars Priority
There are some nightly builds but more often then not they are translation fixes. See this url for some sort of changelog:
http://changelog.bbqdroid.org/#cooper/cm7/next
The assert does not fail on my S5830D when flashing. I think changing the assert is as simple as extracting the .zip file, editing the META-INF/com/google/android/updater-script (see the top for the assert) and finally re-zip. Note that I haven't tried this so be careful not to brick your phone...
Click to expand...
Click to collapse
There, fixed it for you
Related
Hello, i wannt to Dev the Samsung Galaxy XCover by XDA so i start with a Singl Thread,
How to Root GT-S5690?
Flash this File in recovery!
http://forum.xda-developers.com/attachment.php?attachmentid=2252551&stc=1&d=1378997325
How to get CWM Recovery for GT-S5690?
Flash this File throut ODIN in PDA Section and its working!
http://forum.xda-developers.com/attachment.php?attachmentid=2252549&stc=1&d=1378997296
Some Custom Roms and CWM coming soooooon,....im working at that! :laugh::highfive::laugh::highfive::laugh:
MFG Marion808
it´s working! how did you build that? is there a possibility of ics or jb?
Thanks
marion808 said:
Hello, i wannt to Dev the Samsung Galaxy XCover by XDA so i start with a Singl Thread,
How to Root GT-S5690?
Flash this File in recovery!
http://forum.xda-developers.com/attachment.php?attachmentid=2252551&stc=1&d=1378997325
How to get CWM Recovery for GT-S5690?
Flash this File throut ODIN in PDA Section and its working!
http://forum.xda-developers.com/attachment.php?attachmentid=2252549&stc=1&d=1378997296
Some Custom Roms and CWM coming soooooon,....im working at that! :laugh::highfive::laugh::highfive::laugh:
MFG Marion808
Click to expand...
Click to collapse
Hi,
Your rooting method doesn't seem to work on my phone. I get no error during flash of the zip file but when I reboot, the phone isn't rooted.
FYI I'm using a fresh install of the S5690XXLL1_S5690LUXLL1 Rom.
Am I missing something here ?
Using another method found on a French forum, I can get root to work.
ClockworkMod Recovery installation worked flawlessly and that's great news :good:
Your work is much appreciated and it would be nice of you if you could give us a heads-up on what you're up to.
Thanks a bunch anyway.
Thanks
Thanks. Confirmed this is a working root and CWM recovery method.
Looking forward for custom roms, preferable CM based.
I got my phone rooted but no cvm.. they all gives me error msg..
how's this project doing? I would love to see custom roms for this device
My try with ICS for xcover:
https://github.com/manakeri/android_device_samsung_xcover
manakeri said:
My try with ICS for xcover:
//github.com/manakeri/android_device_samsung_xcover
Click to expand...
Click to collapse
hello to every one!
so how's the work on ICs going for this old phone?
I hope you still active!
maybe i can beta test your ROM?
keep it up!
gt-s5690 cwm test result
root zip is not working, what worked is
http://download.chainfire.eu/376/SuperSU/UPDATE-SuperSU-v1.89.zip
SuperSU from chainfire.
Backup is not working with default settings , you must choose 'tar' format .
Restore is halt on /system restore.
manakeri said:
My try with ICS for xcover:
https://github.com/manakeri/android_device_samsung_xcover
Click to expand...
Click to collapse
Can I BETA test your rom
There isn't that much to test yet, struggling to get the RIL working.
Haven't found any info about marvell's RIL.
And the development has been on a break for couple months now, because I'm so busy with "real life".
Sent from my GT-S5690 using Tapatalk 2
good phone, low memory
Naturely real life is more important.
I have been checking your post about this regularly in the hope of unbloating my xcover because of the little memory the phone has.
I wish i could help. I know computers and some php and stuff, but phones, not a clue.
So we'll wait patiently for you to make our day :victory:
How to build?
manakeri said:
And the development has been on a break for couple months now, because I'm so busy with "real life".
Click to expand...
Click to collapse
Hi manakeri,
thanks for your efforts!
I would like to help doing some low-level (RIL, camerca, GPS etc.) stuff, but I don't really know how to start. There is no build/envsetup.sh, which I could source into my shell. I am used to do Linux development on and for Debian and similar Linux distributions, so working with the Android framework is quite new to me. Could you point me to some howto or give some hints?
Regards,
Benedikt
Are you still working on it?
I would like to participate. My brother has a XCover, but he needs it for daily use, so i am not really able to flash anything right now.
Could you point out how you start everything, and which sources you use?
1+
bwildenhain said:
Hi manakeri,
thanks for your efforts!
I would like to help doing some low-level (RIL, camerca, GPS etc.) stuff, but I don't really know how to start. There is no build/envsetup.sh, which I could source into my shell. I am used to do Linux development on and for Debian and similar Linux distributions, so working with the Android framework is quite new to me. Could you point me to some howto or give some hints?
Regards,
Benedikt
Click to expand...
Click to collapse
dehein said:
Are you still working on it?
I would like to participate. My brother has a XCover, but he needs it for daily use, so i am not really able to flash anything right now.
Could you point out how you start everything, and which sources you use?
Click to expand...
Click to collapse
First you'll need the tools:
http://forum.xda-developers.com/showthread.php?t=2464683
And then something like that:
repo init -u git://github.com/CyanogenMod/android.git -b ics
repo sync
git clone git://github.com/manakeri/android_device_samsung_xcover.git device/samsung/xcover
cd device/samsung/xcover/ && ./extract-files.sh && cd ../../..
cp device/samsung/xcover/armv7-a.mk build/core/combo/arch/arm/
cp device/samsung/xcover/overlay/bootable/recovery/ui.c bootable/recovery/ui.c
cp device/samsung/xcover/overlay/bootable/recovery/ui.c bootable/recovery/ui.c
cp device/samsung/xcover/overlay/development/build/sdk.atree development/build/sdk.atree
rm -rf development/samples
. build/envsetup.h
cd vendor/cm && ./get-prebuilts && cd ../..
brunch cm_xcover-eng
Could be I forgot something, but if you get problems, ask.
I'll try to answer in at least couple of days.
compiling cm9 for s5690
manakeri said:
1+
Could be I forgot something, but if you get problems, ask.
I'll try to answer in at least couple of days.
Click to expand...
Click to collapse
Hi manakeri,
thanks for you instructions
Now I got some zip file:
out/target/product/xcover/cm-9-20140225-UNOFFICIAL-xcover.zip, 134M
I installed CWM, told it to install that file, cleared dalvik cache and even did a factory reset, but always got nothing more than a black screen (with backlight on) when trying to boot and couldn't use logcat as some executable within /system/bin... was missing.
If I had a development board I would simply put my computer onto the serial port and probably see what's going on, but I would like to avoid opening the phones case as I don't believe it would stay waterproof in that case. So how could I get some useful debugging info by using software?
Regards,
Benedikt
If I remember right, you need to format both data and system partition using the CWM.
Sent from my GT-S5690 using Tapatalk 2
bwildenhain said:
Hi manakeri,
thanks for you instructions
Now I got some zip file:
out/target/product/xcover/cm-9-20140225-UNOFFICIAL-xcover.zip, 134M
I installed CWM, told it to install that file, cleared dalvik cache and even did a factory reset, but always got nothing more than a black screen (with backlight on) when trying to boot and couldn't use logcat as some executable within /system/bin... was missing.
If I had a development board I would simply put my computer onto the serial port and probably see what's going on, but I would like to avoid opening the phones case as I don't believe it would stay waterproof in that case. So how could I get some useful debugging info by using software?
Regards,
Benedikt
Click to expand...
Click to collapse
Hello bwildenhain,
Please share with us your xperience, regarding the CM9 ROM built by you.
Thank you.
Have a nice day !
PS Sorry for my English
Hello cbacsro,
cbacsro said:
Please share with us your xperience, regarding the CM9 ROM built by you.
Click to expand...
Click to collapse
unfortunately I wasn't able to get it running yet. I tried to install both cm-9-20140225-UNOFFICIAL-xcover.zip and cm_xcover-ota-eng.$USER.zip, both after doing a factory reset, but could not boot CM.
@manakeri
I installed the new CWM by using device/samsung/xcover/scripts/recovery.sh (and manually executing the last uncommented lines), pushed the cm-zip file to the sdcard and then booted to CWM and there did a factory reset and applied one of the cm-zipfiles. Is there anything I forgot?
Regards,
Benedikt
Are those uart pins?
Hello,
I hope not to be disturbing by bumping such an old thread - also hope this is the right thread since it does not seem that the s5690 has its own subforum. What for an insignificant little device. Anyways we've been active and I am currently trying to find the UART pins of the S5690. I have taken a scan of the circuit board and cropped it a bit to show which pins I think might be UART. However, I'm quite in a bind right now: My BusPirate is not here yet. Just had to order one, and now it's going once around the world. Interestingly enough, it seems the mainboard can be run without having the other modules (like touch or camera) connected.
If anybody has experiance with UART (and has a xcover of which one does not fear to void the warranty or brick it or whatever), it would be nice if it got verified.
These four pins seem to be perfect canidates however: Next to processor, four in a group, and one seems to be GND.
Link to photo file (add together yourself, I'm not gonna spam to get rid of that damn 10 post cap. I'd also advise to visit the image hoster with an adblocker):
i7. imgchili .net/47012/47012110_s5690_uart_info.png
(I created that Image by scanning the circuit board with a common flatbed scanner in high resolution, just if you're wondering - makes it way easier to find stuff. Then found those pins, tested them for GND, cropped the original image and included the info you see in it with GIMP).
ppps: I assume it would be too much to ask somebody to write a pxa95x framebuffer driver for the last linux kernel that supported pxa95x devices...
Edit: Oh, the thread is still active. I should *really* get some sleep.
Edit2: @bwildenhain
This is taken from an Email conversation I had with manakeri:
otezun said:
Hey, just wanted to inform you. I just reflashed the phone to 2.3.6. Then rooted it with KERUK, from k0k0s download stuff. Anyways, after I rooted the phone, I installed CWM as you said, with your recovery image. I made factory reset, wiped cache, wiped dalvik cache, formatted /system and /data. Then installed my compiled Cyanogenmod 9.
Click to expand...
Click to collapse
Hehe, documentation is everything...the fat text are the steps I think where absolutely crucial to get cyanogenmod to work. Not sure though. Also @ getting infos from phone without opening it - I think that is possible if you have the right resistance cable. Like USB Jig cable with other resistor, put it onto power and it boots into UART mode, usually giving some kinda shell if I understand it correctly. However, I think you also need special hardware for that too.
However, do not take usual infos in "Fun with resistors", it does not seem to work with the s5690. Or do and tell us how it worked out. Depends on how far you want to go.
Edit 3:
I allowed myself to add some wiki pages to the github wiki.
The wiki now should contain most relevant information on getting started. Also got a bit of structure into it. However, I cannot guarantee that all of the information is correct. Be wise and use your brain.
Check it out at: https ://github. com/manakeri/android_device_samsung_xcover/wiki
Installing CM
Yesterday I installed CWM and rooted my Xcover. Last night I compiled the Xcover branch of CM9 made by manakeri using Builduntu made by sylentprofet.
I just managed to successfully install CyanogenMod by installing cm_xcover-ota-eng.android.zip (aka cm_xcover-ota-eng.$USER.zip). Before installing I performed a factory reset, wiped cache, formatted /system and formatted /data.
It boots fine, and I will experiment with the coming days! Hopefully development will restart soon!
The usb port in my samsug i747M S3 is not working on any pc and my phone is stuck in a bootloop. I need to know if there is anyway to flash in a custom recovery via the stock recovery or flash in a new zip flashable rom through stock recovery.
I have used cygwin kitchen to put together a flashable zip from a odin rom i downloaded online but i keep getting esignature verification failed. After researching this i found that only samsung signed zips are allowed to be flashed in stock recovery. How can i sign my zips and make them appear as Samsung signed? If possible!!
narell said:
The usb port in my samsug i747M S3 is not working on any pc and my phone is stuck in a bootloop. I need to know if there is anyway to flash in a custom recovery via the stock recovery or flash in a new zip flashable rom through stock recovery.
I have used cygwin kitchen to put together a flashable zip from a odin rom i downloaded online but i keep getting esignature verification failed. After researching this i found that only samsung signed zips are allowed to be flashed in stock recovery. How can i sign my zips and make them appear as Samsung signed? If possible!!
Click to expand...
Click to collapse
Sorry man, that's pretty much the proverbial rock and a hard place... I'm assuming you already tried the factory reset? There really aren't many options when you are in this situation without getting the USB port fixed (which is soldered, so not the easiest thing to do). You can't flash a custom recovery or rom through the stock 3e recovery. At all. Some phones you can, this isn't one of them. This limits your options to 2 things -
Find an OTA update zip that is the same version or the one that is the next in line of updates such as this:
http://www.androidegis.com/how-to/leaked-jelly-bean-ota-update-for-bell-galaxy-s3-i747m-9-mvlali1/ (but this is older and probably won't work and do not even try if you were 4.3 last and is a leak version - this is just for example purposes only)
or you can try this, though since your boatloader is probably fine, not sure if it will work either:
http://forum.xda-developers.com/showthread.php?t=2549068
Other than that, your options are JTAG service or fixing the port, which if you are gonna spend the $ for a JTAG service, it'd make more sense to just put that towards the repair and then it will be very easy to reload the OS once that is fixed.
es0tericcha0s said:
Sorry man, that's pretty much the proverbial rock and a hard place... I'm assuming you already tried the factory reset? There really aren't many options when you are in this situation without getting the USB port fixed (which is soldered, so not the easiest thing to do). You can't flash a custom recovery or rom through the stock 3e recovery. At all. Some phones you can, this isn't one of them. This limits your options to 2 things -
Find an OTA update zip that is the same version or the one that is the next in line of updates such as this:
http://www.androidegis.com/how-to/leaked-jelly-bean-ota-update-for-bell-galaxy-s3-i747m-9-mvlali1/ (but this is older and probably won't work and do not even try if you were 4.3 last and is a leak version - this is just for example purposes only)
or you can try this, though since your boatloader is probably fine, not sure if it will work either:
http://forum.xda-developers.com/showthread.php?t=2549068
Other than that, your options are JTAG service or fixing the port, which if you are gonna spend the $ for a JTAG service, it'd make more sense to just put that towards the repair and then it will be very easy to reload the OS once that is fixed.
Click to expand...
Click to collapse
Thanks alot for your help...i downloaded the rom from the link u sent..the flash woud have been successfull but it was aborted due to this error
E: Error in /tmp/sideload/package.zip (Status 6). Installation aborted.
What does this mean? Is there anyway i can go into the rom package and fix it?
narell said:
Thanks alot for your help...i downloaded the rom from the link u sent..the flash woud have been successfull but it was aborted due to this error
E: Error in /tmp/sideload/package.zip (Status 6). Installation aborted.
What does this mean? Is there anyway i can go into the rom package and fix it?
Click to expand...
Click to collapse
I specifically said that it probably wouldn't work and was only for the idea. That update was a leaked version of 4.1.1. I'm assuming your system is probably newer than that, hence why it wouldn't work. I don't know what update you are on and not sure if there is an OTA that would be helpful even. Just saying in your current situation, there aren't many options.
Every time i try to install any kitkat rom on my Xperia u it give error status 7 and now if i edited updater script not its giving installation failed after updating partition details.... really need help got irritated with this problem...help.HELP
Status 7 Details...
Which ROM were you trying to flash, specifically?
However,
Status error 7 is not only due to a logical error in updater-script, but it can also be caused due to an out dated update-binary. Try using the update binary below and if it does not help, report it to your ROM developer to fix the issue in updater-script.
Happy Flashing...
try this
http://forum.xda-developers.com/showthread.php?t=2522762
it worked for me on xperia P. should work on U either, i guess.
danishsajjad said:
Which ROM were you trying to flash, specifically?
However,
Status error 7 is not only due to a logical error in updater-script, but it can also be caused due to an out dated update-binary. Try using the update binary below and if it does not help, report it to your ROM developer to fix the issue in updater-script.
Happy Flashing...
Click to expand...
Click to collapse
Most error 7 updater errors are due to failed assertions, which re there for a reason. Some kernels/CWM recoveries do not have the right props set so the assertions will fail.
@danaksim, "fixing" the script is not a solution unless you realy know what you are doing and may be a death sentence for the device.
@loveymangal, when you asking such a question provide detailes for what ROM you are trying to install, link, or if you cannot post link at least the exact title and site it's on. Also provide the steps you made, and which ROM/kernel/CWM recovery you are using now.
ChikeD said:
@danaksim, "fixing" the script is not a solution unless you realy know what you are doing and may be a death sentence for the device.
.
Click to expand...
Click to collapse
yeah, you're right. it wasn't too wise to give that advice since i don't know which rom he's trying to flash.
Thanks to all finally fixed the problem
With the help of replies i was finally able to fix the problem by changing the binary and using twrp i was trying to install xperia u Sirius Xperiance Rom http://forum.xda-developers.com/xperia-u/u-development/aosx-z2-sirius-xperience-t2725846 and it worked
Hi developers. ^^ hey just wanna ask if there is anyone who is willing to make a custom rom for my zte blade s7... I prefer resurrection remix or cyanogenmod because of the veriety of customizing.. . Could anyone help? Or maybe some tutorials on how to create my own custom rom.. . I'm just a basic android customizer. I already know how to root, install xposed, reflash, backup, and such... But wanna kick it up a notch and make a custom rom.. . Hehe..
Jo_bell said:
Hi developers. ^^ hey just wanna ask if there is anyone who is willing to make a custom rom for my zte blade s7... I prefer resurrection remix or cyanogenmod because of the veriety of customizing.. . Could anyone help? Or maybe some tutorials on how to create my own custom rom.. . I'm just a basic android customizer. I already know how to root, install xposed, reflash, backup, and such... But wanna kick it up a notch and make a custom rom.. . Hehe..
Click to expand...
Click to collapse
My ports for S7
NFound said:
My ports for S7
Click to expand...
Click to collapse
Hey, you've made ports. Do you know what the difference is between twrp ports? For instance what makes a recovery.img different between phones? Does recovery.img have its own kernel? A rootfilesystem?
peterius said:
Hey, you've made ports. Do you know what the difference is between twrp ports? For instance what makes a recovery.img different between phones? Does recovery.img have its own kernel? A rootfilesystem?
Click to expand...
Click to collapse
Yes. To install TWRP use Google Translator: https://4pda.ru/forum/index.php?s=&showtopic=697227&view=findpost&p=64637653
Preview Oreo: https://4pda.ru/forum/index.php?s=&showtopic=697227&view=findpost&p=64948575
Yes to which? "Translation to secure pages is not supported". I was asking about phones in general, not just the ZTE. I asked in a different thread but there was no response. So I thought you might know, maybe PM would be better, or maybe it's inconvenient for you?
NFound said:
My ports for S7
Click to expand...
Click to collapse
hi i downloaded ur custom roms both cm12.1 and lineage...
but non of them were flashable.. it said tht the rom was for s7.. #something like tht# lucikly i have a backup of my rom to reflash. i researched some threads and found out tht i can flash the rom without the verification by deleting some symbols and words in updater script located inside google folder... but before I do tht.. i just want to make sure.. is the custom rom actually for "ZTE BLADE S7 T920" or is it for the "samsung s7"
http://m.gsmarena.com/zte_blade_s7-7670.php
here are the specs and such about the phone for reference
Jo_bell said:
hi i downloaded ur custom roms both cm12.1 and lineage...
but non of them were flashable.. it said tht the rom was for s7.. #something like tht# lucikly i have a backup of my rom to reflash. i researched some threads and found out tht i can flash the rom without the verification by deleting some symbols and words in updater script located inside google folder... but before I do tht.. i just want to make sure.. is the custom rom actually for "ZTE BLADE S7 T920" or is it for the "samsung s7"
http://m.gsmarena.com/zte_blade_s7-7670.php
here are the specs and such about the phone for reference
Click to expand...
Click to collapse
Yes, ZTE BLADE S7 T920. so you have an old TWRP therefore swearing. establish this TWRP 3.1.1-1 or delete first 2 lines in updater-script
NFound said:
Yes, ZTE BLADE S7 T920. so you have an old TWRP therefore swearing. establish this TWRP 3.1.1-1 or delete first 2 lines in updater-script
Click to expand...
Click to collapse
hi sorry for not replying... i was finding ways to flash the rom with my friend...
i think my phone is outta luck... already flsh the recovery you suggested but still can't install any of the roms... tried editing ro.product.device as s7... still the same with either error 6/7 if i use the edited updater script rom it will show up
Updater Process ended with error : 6
if i use the unedited rom it will show up error : 7
bummer for my phone... is there anymore that i can do?.. hehe.. i really want to experience android nougat and oreo..
but if its a dead end.. bummer...
maybe this could help?
i remember over the days.. i changed the build.prop and edit the model as my name..XD to fool my friends tht i made the device(trick failed.. they saw the logo at the back)XD... but i did'nt change it back.. because.. there was no harm. no error seem to pop up.. so... yeah... busted build.prop
i followed the custom rom... because i saw in some lines in updater script that wrote ro.product.device= s7
still the same with errors... below are the errors..
https://ibb.co/iRpA65
pictures of the log is in this link or in the attachment below... the picture is quite blurry because i used a java phone to snap a photo... hehe
inside the log is
''white colour'' regular process
installing zip file 'filename'
bla bla bla .etc
red colour... first red colour... was when i flash the edited rom(deleted some keywords in updater.script)
red 1
Updater process ended with ERROR : 6
Error installing zip file '/ filename'
the second red colour is flashing with the unedited rom
red 2
Updater process ended with ERROR : 7
Error installing zip file '/ filename'
if nothing can be done.. its okay ill just go with the stock then...
Jo_bell said:
hi sorry for not replying... i was finding ways to flash the rom with my friend...
i think my phone is outta luck... already flsh the recovery you suggested but still can't install any of the roms... tried editing ro.product.device as s7... still the same with either error 6/7 if i use the edited updater script rom it will show up
Updater Process ended with error : 6
if i use the unedited rom it will show up error : 7
bummer for my phone... is there anymore that i can do?.. hehe.. i really want to experience android nougat and oreo..
but if its a dead end.. bummer...
maybe this could help?
i remember over the days.. i changed the build.prop and edit the model as my name..XD to fool my friends tht i made the device(trick failed.. they saw the logo at the back)XD... but i did'nt change it back.. because.. there was no harm. no error seem to pop up.. so... yeah... busted build.prop
i followed the custom rom... because i saw in some lines in updater script that wrote ro.product.device= s7
still the same with errors... below are the errors..
https://ibb.co/iRpA65
pictures of the log is in this link or in the attachment below... the picture is quite blurry because i used a java phone to snap a photo... hehe
inside the log is
''white colour'' regular process
installing zip file 'filename'
bla bla bla .etc
red colour... first red colour... was when i flash the edited rom(deleted some keywords in updater.script)
red 1
Updater process ended with ERROR : 6
Error installing zip file '/ filename'
the second red colour is flashing with the unedited rom
red 2
Updater process ended with ERROR : 7
Error installing zip file '/ filename'
if nothing can be done.. its okay ill just go with the stock then...
Click to expand...
Click to collapse
i just tried the lineageOS 15 rom, and got an error 7, before that there was a line saying "this rom is for "s7" this is a "".
so how can i flash this rom?
Scepterus said:
i just tried the lineageOS 15 rom, and got an error 7, before that there was a line saying "this rom is for "s7" this is a "".
so how can i flash this rom?
Click to expand...
Click to collapse
Hi, I want to share a solution for this as user of ZTE Blade S7 too:
If you want to install any rom via TWRP 3.1.1 you will have to edit updater_script with Notepad ++ because probably these errors are caused by trying to edit with any other Windows text editer.
Please confirm two options in Notepad ++: "Edit/EOL Conversion/Convert to UNIX Format" and "Encoding/Encode in ANSI".
I recommend to erase the first two lines in the script, use "update archive" via WinZip, WinRAR, 7ZIP (not to rezip the files, only update updater_script with the modified one) and you will not encounter the ERROR:7.
This way I manage to install custom roms because the problem is that TWRP 3.1.1 do not recognize our ZTE Blade S7 as "ZTE_T920" so the best solution is to erase this lines of code in all roms that include "ro.product.device" and things like that but in the correct way, just erase correctly and if rom is correct it will install without a problem.
For error:6 if you do this correctly maybe it can be caused by not erasing system. Do not forget to wipe system in advanced settings.
Additionally, I have the latest B20 version from Malaysia in TWRP zip, but I cannot share links so if you want it please message me.
Still unable to flash the lineage 15 Rom and somebody please assist by posting a link for a flashable file. Thanks
Hey Guys,
i got the same Problem here.
I´ve rooted with Kingroot posted by NFound and flashed the TWRP 3.1.1-1.img with Rashr ony my ZTE Blade S7 (T920)
After that i switched into TWRP and wiped everything.
Next i tried to install the lineage os but get error 7, after deleting those 2 lines i still get the error 7 just the "this rom is for "s7" this is a ""." message is missing now.
So i tried the cm-rom, install works like a charm but google play freezes and i cant delete cache of apps because the settings window freezes too when i want to click on apps.... (used open gapps arm 5.1 nano)
So both dont work very well 4 me, maybe u got an idea.
Right now i´m downloading lineage os another time to make sure the rom is not bricked or sth.
Lg Seg
Thanks for updating, i was having problems with the stock rom after installing xposed and magisk and was considering trying the fix for the lineage rom.
I do wonder if anyone here actually managed to get that rom to work. Please update us if you succeed.
4pda
Scepterus said:
Thanks for updating, i was having problems with the stock rom after installing xposed and magisk and was considering trying the fix for the lineage rom.
I do wonder if anyone here actually managed to get that rom to work. Please update us if you succeed.
Click to expand...
Click to collapse
4pda android 8 lineageos 15.0 post 445 theme zte blade s 7
If this is in the wrong place I apologise and please move.
So i have been installing roms for a long time, I know how its done and what i need to avoid. Recently though, every rom i try to install fails with error 7, Even the same zip file i've already installed before so i know it should work fine. I've looked on google but all that comes up is this updater script that should fix it, but i have tried that to no avail.
Anybody had this problem and fixed it?
Thanks
beedle90 said:
If this is in the wrong place I apologise and please move.
So i have been installing roms for a long time, I know how its done and what i need to avoid. Recently though, every rom i try to install fails with error 7, Even the same zip file i've already installed before so i know it should work fine. I've looked on google but all that comes up is this updater script that should fix it, but i have tried that to no avail.
Anybody had this problem and fixed it?
Thanks
Click to expand...
Click to collapse
What's your variant, last firmware, twrp version ?
tech_infinity said:
What's your variant, last firmware, twrp version ?
Click to expand...
Click to collapse
Ah sorry about that forget to mention.
Anyway I figured it out, I had installed a vendor zip and forgot, turns out that was causing the problem.