Hi all
Trying to install the latest nightly has been impossible since June. Have left things as is, the phone works fine with the installed ROM version.
Now I tried to research where the problem lies, but don't have the necessary tech know-how to remedy it.
When trying to install the zip the following messages appear on TWRP:
Updating partition details......
...... done
Full SELinux support is present.
MTP Enabled
Installing zip file '/external_sd/LineageOS/lineage-15.1-20181214-nightly-klte-signed.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Warning: No file_contexts
E3004: This package is for device: klte,klteacg,klteatt,kltecan,kltelra,kltetmo,klteusc,kltevzw,kltexx; this device is .
(now text in red)
E:unknown command[log]
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/LineageOS/lineage-15.1-20181214-nightly-klte-signed.zip'
(text in red ends)
Updating partition details....
...done
Until June, the nightly updating never was a problem.
I am 100% sure my S5 is the klte version
The red line E:unknown command [log] always popped up when updating, but did not interrupt the updating process.
The latest version that worked for updating and that is installed on my phone is: 14.1-20180629-NIGHTLY-klte
Kernel Version
3.4.113-lineageos-g31d25d7
[email protected] #1
Fri Jun 29 14:12:53 CEST 2018
Build Number
lineage_klte_userdebug 7.1.2 NJH47F 6fc3da3341
Hope this info helps to identify, why the nightly does not recognize the klte (see the 9th line, where it says ' this device is . '
My guess is that either some file on my phone is missing or not in the spot where the nightly is looking for it???
How can i repair this so that i can get my S5 up to date?
Appreciate your help!!
Delete the first line in updater script using notepad++
Where is the updater script?META-INF/com/google/android/updater-script
Thank you for your answer. Unzipped the nightly file, but I can not find a script named updater? Do you mean the file I list below:
updater-script ???
The first line reads:
assert(getprop("ro.product.device") == "klte" || getprop("ro.build.product") == "klte" ||
getprop("ro.product.device") == "klteacg" || getprop("ro.build.product") == "klteacg" ||
getprop("ro.product.device") == "klteatt" || getprop("ro.build.product") == "klteatt" ||
getprop("ro.product.device") == "kltecan" || getprop("ro.build.product") == "kltecan" ||
getprop("ro.product.device") == "kltelra" || getprop("ro.build.product") == "kltelra" ||
getprop("ro.product.device") == "kltetmo" || getprop("ro.build.product") == "kltetmo" ||
getprop("ro.product.device") == "klteub" || getprop("ro.build.product") == "klteub" ||
getprop("ro.product.device") == "klteusc" || getprop("ro.build.product") == "klteusc" ||
getprop("ro.product.device") == "kltevzw" || getprop("ro.build.product") == "kltevzw" ||
getprop("ro.product.device") == "kltexx" || getprop("ro.build.product") == "kltexx" || abort("E3004: This package is for device: klte,klteacg,klteatt,kltecan,kltelra,kltetmo,klteub,klteusc,kltevzw,kltexx; this device is " + getprop("ro.product.device") + ".");
If that is correct, please let me know. prefer to be 100% sure before bricking my phone. Thanks for your patience with a newb
unzipping the nightly I see:
folder install/bin with backuptool.functions and backuptool.sh
folder META-INF/com/android with metadata and otacert
folder META-INF/com/google/android with update-binary and updater-script ??? any of these 2????
folder META-INF/org/lineageos with releasekey
folder system with build.prop
and the files
boot.img
file_contents.bin
system.new.dat.br
system-patch.dat
system.transfer.list
Once more: Appreciate your help a lot!
Edit: THIS WORKED JUST FINE! Thank you a million! Using notepad++ makes editing the file a snap, as it does not insist on .txt ending of file. Edited the line above out and saved the file, zipped the lot up again and then did the Install in TWRP. The Install process ran smoothly. Wiped the Davlik and rebooted. System comes up just fine!!!! AD FOX You were a great help!!!!
same problem on lineage 16 any fix yet?
Octaved said:
same problem on lineage 16 any fix yet?
Click to expand...
Click to collapse
Can confirm, same problem, also same solution, as described above:
open the zip, edit META-INF/com/google/android/updater-script
Remove from the start of assert(getprop("ro.product.device") == "klte" || ... untill ...+ getprop("ro.product.device") + ".")
Save, and use this modified zip. I just tried it with no problems. Thanks!
Updater process ended with signal: 11
xananaxx said:
Can confirm, same problem, also same solution, as described above:
open the zip, edit META-INF/com/google/android/updater-script
Remove from the start of assert(getprop("ro.product.device") == "klte" || ... untill ...+ getprop("ro.product.device") + ".")
Save, and use this modified zip. I just tried it with no problems. Thanks!
Click to expand...
Click to collapse
Tried this solution but now get different error Updater process ended with signal: 11
According to the updater-script its failing at this point
block_image_update("/dev/block/platform/msm_sdcc.1/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat") ||
abort("E1001: Failed to update system image.");
The same here. I also got the error 11 message after flashing the modified updater script. My solution: Just flash the next older version of TRWP (e.g. instead of twrp-3.4.0-0-klte.img use twrp-3.3.1-0-klte.img). It worked just fine.
plapic said:
Updater process ended with signal: 11
Tried this solution but now get different error Updater process ended with signal: 11
According to the updater-script its failing at this point
block_image_update("/dev/block/platform/msm_sdcc.1/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat") ||
abort("E1001: Failed to update system image.");
Click to expand...
Click to collapse
If editing the code and removing some open brackets, make sure to also remove the corresponding closing brackets. I.e. I changed line 1 from:
Code:
assert(getprop("ro.product.device") == "grouper" || getprop("ro.build.product") == "grouper" || abort("E3004: This package is for device: grouper; this device is " + getprop("ro.product.device") + "."););
into:
Code:
getprop("ro.product.device") + ".";
When I made this change to line 1 of updater-script it worked fine and the ROM installed.
By the way, if you edit updater-script, you have edited the zip file and so you will need to uncheck TWRP's 'zip signature verification' tickbox.
Related
I have an HTC Magic, and have just managed to downgrade hboot/spl and install a custom recovery.
But now, when i'm trying to install CM 6 (not the RC), i get a verification error..
Starting recovery..
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (320 x 480)
Build : RA-hero-v1.6.2
Fixing execute permissions for /cache
I:Set boot command "boot-recovery"
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=1
ro.ril.ecc.HTC-WWE=999
ro.build.id=CUPCAKE
ro.build.display.id=CUPCAKE.eng.u70000.20090827.103405
ro.build.version.incremental=eng.u70000.20090827.103405
ro.build.version.sdk=3
ro.build.version.release=1.5
ro.build.date=Thu Aug 27 10:35:04 CST 2009
ro.build.date.utc=1251340504
ro.build.type=user
ro.build.user=u70000
ro.build.host=Android-X02
ro.build.tags=test-keys
ro.product.model=HTC Hero
ro.product.brand=htc_wwe
ro.product.name=htc_hero
ro.product.device=hero
ro.product.board=hero
ro.product.manufacturer=HTC
ro.product.locale.language=
ro.product.locale.region=
ro.board.platform=msm7k
ro.build.product=hero
ro.build.description=2.73.405.5 146733 CL#61267 release-keys
ro.build.changelist=61267
ro.product.ua=
ro.build.fingerprint=htc_wwe/htc_hero/hero/hero:1.5/2.73.405.5/61267:user/test-keys
keyguard.no_require_sim=1
rild.libpath=/system/lib/libhtc_ril.so
ro.ril.hep=1
wifi.interface=tiwlan0
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
ro.ril.hsupa.category=5
wifi.supplicant_scan_interval=45
ro.sf.lcd_density=160
ro.com.google.locationfeatures=1
persist.service.mount.playsnd=0
settings.display.autobacklight=1
settings.display.brightness=102
ro.ril.def.agps.mode=2
ro.com.google.networklocation=1
ro.config.ringtone=Innovation.mp3
ro.config.notification_sound=Color.mp3
ro.config.alarm_sound=Light.mp3
ro.config.cal_notification=Vector.mp3
ro.config.msg_notification=Ascend.mp3
ro.setupwizard.mode=DISABLED
ro.com.google.clientidbase=android-htc
ro.config.sync=yes
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.modversion=RA-hero-v1.6.2
ro.factorytest=0
ro.serialno=HT95WKF11405
ro.bootmode=recovery_manual
ro.baseband=6.35.08.29
ro.carrier=HTC-Nor
ro.bootloader=1.76.2007
ro.hardware=sapphire
ro.revision=128
ro.cid=HTC__Y13
init.svc.recovery=running
init.svc.adbd=running
I:Set boot command ""
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)
E:Can't mount SDCARD:
I:Set boot command ""
Enabling USB-MS : ./dev/block/mmcblk0
USB Mass Storage enabled
USB-MS enabled!
Press HOME to disable,
and return to menu
Disabling USB-MS : .USB Mass Storage disabled
USB-MS disabled!
I:Set boot command ""
I:Set boot command ""
Install : SDCARD:update-cm-6.0.0-DS-signed.zip ?
Press HOME to confirm,
any other key to abort.
Install from sdcard...
Finding update package...
I:Update location: SDCARD:update-cm-6.0.0-DS-signed.zip
Opening update package...
I:Update file path: /sdcard/update-cm-6.0.0-DS-signed.zip
Verifying update package...
I:Verified META-INF/CERT.RSA
I:Verified META-INF/MANIFEST.MF
<VERIFIED A LOT OF FILES>
I:Verified system/media/audio/ui/KeypressStandard.ogg
I:Verified system/lib/libGLESv1_CM.so
Installing update...
I:read: ui_print Welcome to CyanogenMod-6.0.0-DS!
Welcome to CyanogenMod-6.0.0-DS!script aborted: assert failed: getprop("ro.product.device") == "trout" || getprop("ro.build.product") == "trout" || getprop("ro.product.board") == "trout" ||
getprop("ro.product.device") == "sapphire" || getprop("ro.build.product") == "sapphire" || getprop("ro.product.board") == "sapphire"
I:read: ui_print
I:read: ui_print assert failed: getprop("ro.product.device") == "trout" || getprop("ro.bassert failed: getprop("ro.product.device") == "trout" || getprop("ro.bI:read: uild.product") == "trout" || getprop("ro.product.board") == "trout" ||
E:unknown command [uild.product")]
I:read: ui_print getprop("ro.product.device") == "sapphire" || getprop("ro.build. getprop("ro.product.device") == "sapphire" || getprop("ro.build.I:read: product") == "sapphire" || getprop("ro.product.board") == "sapphire"
E:unknown command [product")]
I:read: ui_print
E:Error in /sdcard/update-cm-6.0.0-DS-signed.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
I have no idea what to to, as i have never installed CM before.
the fastboot specs are:
SAPPHIRE PVT 32A ENG S-OFF H
HBOOT-1.76.2007 (SAPP10000)
CPLD-12
RADIO-6.35.08.29
Aug 21 2009, 18:19:15
help is much appreciated ^_^
It should not give any errors...
But you could always remove the error giving line from the install script..
Then resign the rom and flash it.
i'm sorry, i am a real noob on this, is it any chance you can do it for me? thanks.
EDIT: i tried once, but it got corrupted
You have to resign it.
Or it will get corrupted as the error gives you...
Or you could flash clockwork recovery instead of amon_ra... and deactivate the signing check.
thanks, i'll try that and report back
okay, now i reflashed the recovery with ROM Manager, pressed install from SD(in rom manager) and selected the CM rom(unmodified). it reboots, runs backup, everything looks good, and then the same error repeats itself until it sends me back to the recovery menu, where it is there for about 5 seconds, and then my phone reboots normally. all data is flashed.
how do i deactivate the signing check? or is there another solution?
EDIT... sorry just found that clockwork recovery does not work with the 6.35 radio...
**** it... i'll do it..
Give me link to the rom you want.
THANK YOU!
http://khsk.uberitz.net/cm/update-cm-6.0.0-DS-signed.zip
that's it. i need an EB1 kernel patch and google apps too(thats what cyanogenmod wiki said), dunno if they need to be changed too ..
link for google apps: http://cyanogenmod-mirror.local.host.name/gapps/gapps-mdpi-tiny-20101020-signed.zip
the EB1, though i dunno if it supports 6.35.x: http://briancrook.ca/android/cm-por...d.zip[/url
thanks SO much for doing this! :D
I found the problem...
You have 1.76.2007 spl...
This rom only works for old spl/radio...
Code:
getprop("ro.bootloader") == "1.33.2005" ||
getprop("ro.bootloader") == "1.33.2003AF" ||
getprop("ro.bootloader") == "1.33.0004" ||
getprop("ro.bootloader") == "1.33.2004" ||
getprop("ro.bootloader") == "1.33.3004" ||
getprop("ro.bootloader") == "1.33.0005" ||
getprop("ro.bootloader") == "1.33.2005" ||
getprop("ro.bootloader") == "1.33.3005" ||
getprop("ro.bootloader") == "1.33.0006" ||
getprop("ro.bootloader") == "1.33.2006" ||
getprop("ro.bootloader") == "1.33.3006" ||
getprop("ro.bootloader") == "1.33.0007" ||
getprop("ro.bootloader") == "1.33.2007" ||
getprop("ro.bootloader") == "1.33.3007" ||
getprop("ro.bootloader") == "1.33.0008" ||
getprop("ro.bootloader") == "1.33.2008" ||
getprop("ro.bootloader") == "1.33.3008" ||
getprop("ro.bootloader") == "1.33.0009" ||
getprop("ro.bootloader") == "1.33.2009" ||
getprop("ro.bootloader") == "1.33.0010" ||
getprop("ro.bootloader") == "1.33.2010" ||
getprop("ro.bootloader") == "1.33.0011" ||
getprop("ro.bootloader") == "1.33.2011" ||
getprop("ro.bootloader") == "1.33.3011" ||
getprop("ro.bootloader") == "1.33.0013" ||
getprop("ro.bootloader") == "1.33.2013" ||
getprop("ro.bootloader") == "1.33.3013");
so i can downgrade via the instructions in this thread, and then install CM as normal?
No... use my tool to downgrade... MUCH EASIER :0)
Find it in my signature... Fastboot commander (magic).
Just find the magic 32A tab... then choose "flash old"...
It will flash a combo... so you also have the right recovery :0)
Then flash the rom, EBI1 and then gapps from recovery.
If you ever want to revert back to new radio.. then just choose "flash new" :0)
thanks, now i just have to make rapidshare stop hating me.. can't you upload to mediafire or something?
Done.............
okay, i just want to make sure about this.. what are the chances that ill brick my phone upgrading the radio? because im not sure if my magic supports the old radio..
I will never suggest to upgrade/downgrade your radio if i'm not sure that you device can support it.
Checking the op, i could see that you have the same device as i have... and i made the tool and tested my self... It will work :0)
ah, good. because i downgraded my SPL from S-ON and hboot 1.76.2009..
but since i did install the engineer spl, i suppose it works
EDIT: it didnt. i got this error:
"hboot" flash FAILURE.
FLASH OF OLD FILES FAILURE - SPL FAILURE.
then tried to flash new again, got this error:
"radio" flash FAILURE.
FLASH OF NEW FILES FAILURE - RADIO FAILURE.
EDIT2: unplugged and restarted into fastboot. it shows:
SAPPHIRE PVT 32A ENG S-OFF H
HBOOT-1.76.2007 (SAPP10000)
CPLD-12
RADIO-3.22.20.17
Aug 21 2009, 18.19.15
trying to boot normally, it gets into a boot loop. i can still get into fastboot and recovery(clockwork works!), so i dont think im bricked.
Easy now... and keep you comments in one thread or i will get confused...
YOU ARE NOT BRICKED!
You can fix this easy.
But lets agree on that you write on the fastboot commander thread where it's relevant.
See my reponse there
Hi,
It seems im in same error as you are.
Can you take a look at my thread.
http://forum.xda-developers.com/showthread.php?t=828300
Im almost done, stuck at flash the last 3 files according to instructions.
------------------------
17. After phone powers off, reboot into recovery by holding Home + Power keys.
.
18. Using the trackball, select "Flash ZIP from SD Card" and flash the following files.
Select the home key to confirm each file
a)update-cm-6.0.0-DS-signed.zip
b)bc-6.0.0-ebi1-signed.zip
c)gapps-mdpi-tiny-20100816-signed.zip
.
19. After the last file has finished flashing reboot the phone normally.
It can take anywhere from 5-15 min for the first boot.
--------------------------
thanks.
I am unable to flash any new roms, be it CM or MIUI. This happens after i flashed the kernel through fastboot. I get the following error.
(STATUS 7) Asserts Failed. I disabled the certifications and tried all sorts of stuff. Right now, I have baseband 64, ROOTED on STOCK SE FIRMWARE.
I searched for this answer a long time but got nothing so I had to actually MAKE AN ACCOUNT just to ask this dumb question. I get this error.
assert(getprop("ro.product.device") == "LT18i" || getprop("ro.build.product") == "LT18i" || getprop("ro.product.board") == "LT18i" ||
getprop("ro.product.device") == "LT18a" || getprop("ro.build.product") == "LT18a" || getprop("ro.product.board") == "LT18a" ||
getprop("ro.product.device") == "LT15i" || getprop("ro.build.product") == "LT15i" || getprop("ro.product.board") == "LT15i" ||
getprop("ro.product.device") == "LT15a" || getprop("ro.build.product") == "LT15a" || getprop("ro.product.board") == "LT15a" ||
getprop("ro.product.device") == "anzu" || getprop("ro.build.product") == "anzu" || getprop("ro.product.board") == "anzu");
package_extract_file
I tried many suggestions as deleting the lines of code from the actual ZIP FILE. That did not work. I want to ore specifically direct my question at DINESH, here
http://forum.xda-developers.com/showthread.php?t=1503527
as for some reason his MIUI ROM is more troublesome than others and SAOSIN'S MIUI GB ROM actually I can flash onto my phone. Please let me know what I can do guys. Thanks and sorry for yet another NOOB QUESTION.
uspeekchaineze said:
I am unable to flash any new roms, be it CM or MIUI. This happens after i flashed the kernel through fastboot. I get the following error.
(STATUS 7) Asserts Failed. I disabled the certifications and tried all sorts of stuff. Right now, I have baseband 64, ROOTED on STOCK SE FIRMWARE.
I searched for this answer a long time but got nothing so I had to actually MAKE AN ACCOUNT just to ask this dumb question. I get this error.
assert(getprop("ro.product.device") == "LT18i" || getprop("ro.build.product") == "LT18i" || getprop("ro.product.board") == "LT18i" ||
getprop("ro.product.device") == "LT18a" || getprop("ro.build.product") == "LT18a" || getprop("ro.product.board") == "LT18a" ||
getprop("ro.product.device") == "LT15i" || getprop("ro.build.product") == "LT15i" || getprop("ro.product.board") == "LT15i" ||
getprop("ro.product.device") == "LT15a" || getprop("ro.build.product") == "LT15a" || getprop("ro.product.board") == "LT15a" ||
getprop("ro.product.device") == "anzu" || getprop("ro.build.product") == "anzu" || getprop("ro.product.board") == "anzu");
package_extract_file
I tried many suggestions as deleting the lines of code from the actual ZIP FILE. That did not work. I want to ore specifically direct my question at DINESH, here
http://forum.xda-developers.com/showthread.php?t=1503527
as for some reason his MIUI ROM is more troublesome than others and SAOSIN'S MIUI GB ROM actually I can flash onto my phone. Please let me know what I can do guys. Thanks and sorry for yet another NOOB QUESTION.
Click to expand...
Click to collapse
install via flashtool the original rom, reflash kernel and rom after. It will work. Try with another kernel if the last one doesn't work.
Wrong selection
From my sexy LT15i
You think if I just flash the kernels and do the roms it will work? Flashing the kernels through CWM though or using fastboot? Well, if you had any experience with them, please let me know. thanks.
u cannot flash kernel with cwm! The only way is via fastboot. I don't know if it works, but for resolve the topic problem u need to flash official rom, reflash a working kernel and after the rom.
in order to save time u should try first to flash a new kernel, with this try to install rom.zip from sd (wiping cache and system data). If it doesn't work, use the method explained above.
I flashed the miuiV4 from saossin and it worked. I think I know why. His rom is made only for the lt15i. The other rooms are made for both the arc and arc s. this is what screws up my phone. So the solution is to flash a rom made only for my phone. I had read somewhere that people had problems with partitions pertaining to this problem. Today I tried to download hosts for adfree and the program told me it could not find a partition to write to. Could this be a problem? Let me know what you think.
uspeekchaineze said:
I flashed the miuiV4 from saossin and it worked. I think I know why. His rom is made only for the lt15i. The other rooms are made for both the arc and arc s. this is what screws up my phone. So the solution is to flash a rom made only for my phone. I had read somewhere that people had problems with partitions pertaining to this problem. Today I tried to download hosts for adfree and the program told me it could not find a partition to write to. Could this be a problem? Let me know what you think.
Click to expand...
Click to collapse
i don't know but i don't think so, the roms designed for arc\arcs can work fully on both devices. I think that something can be corrupt in ur os, kernel or other, so my advice is the same yet. Use flashtool to return ur phone on the original factory rom, by this u can install all.
open the downloaded rom zip file in computer.go to META-INF/com/google/android.
in that open updater-script in notepad.delete the below lines in ur notepad file.save it nd flash now.no installation errors.
assert(getprop("ro.product.device") == "X10i" || getprop("ro.build.product") == "X10i" ||
getprop("ro.product.device") == "X10a" || getprop("ro.build.product") == "X10a" ||
getprop("ro.product.device") == "es209ra" || getprop("ro.build.product") == "es209ra");
Click to expand...
Click to collapse
OK,I have solution
If your previous ROM is Feralab's ROM or orther,you will get the error during installation.
My solution is install other ROM like Achotjan's ROM before you install CM9 or AOKP ROM.You will have error free
Hi All,
I'm trying to flash the latest MIUI 2.11.30 to my Galaxy SIII int without success.
I'd like to not install the chinese stock as requested on the MIUI site so I'm asking if someone was able to flash it from recovery on another rom.
Now I'm on Omega 3.33 with TWRP recovery but I also tried with Paranoid 2.54 and CWM touch without success.
I always get this error message:
Code:
assert failed: getprop("ro.product.device") == "~truncated
getprop("ro.build.product") == "m0" || ge~truncated
E:Error in "zip file path" (status 7)
Error flashing zip "zip file path"
Anyone knows a possible solution?
Thank you very much!
Bye.
Try altering the install script in the zip file to say "galaxys3" instead of "m0".
Sent from my GT-I9300 using Tapatalk 2
Theshawty said:
Try altering the install script in the zip file to say "galaxys3" instead of "m0".
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the advice, no luck with that but I solved it removing this assert statement:
Code:
assert(getprop("ro.product.device") == "m0" ||
getprop("ro.build.product") == "m0" || getprop("ro.product.device") == "m0" || getprop("ro.build.product") == "m0");
from this file inside the zip:
META-INF\com\google\android\updater-script
Thanks again for the advice, I took a look around and I saw that. :good:
Bye!
Now that it's solved, Thread closed.
recently i read it somewhere that flashing a custom rom over lollipop bootloader of R2P miui will give you voLTE in your custom rom
but there whenever i flash rom it gives status 7 error
it is recovery problem or rom problem?
using twrp recovery and mokee lollipop based rom
rajatchawla66 said:
recently i read it somewhere that flashing a custom rom over lollipop bootloader of R2P miui will give you voLTE in your custom rom
but there whenever i flash rom it gives status 7 error
it is recovery problem or rom problem?
using twrp recovery and mokee lollipop based rom
Click to expand...
Click to collapse
Do a clean flash[wipe data+cache+system] and install ROM.
Take a backup your current ROM first.
rajatchawla66 said:
recently i read it somewhere that flashing a custom rom over lollipop bootloader of R2P miui will give you voLTE in your custom rom
but there whenever i flash rom it gives status 7 error
it is recovery problem or rom problem?
using twrp recovery and mokee lollipop based rom
Click to expand...
Click to collapse
You are using wrong recovery. Download and use this one -
http://forum.xda-developers.com/redmi-2/development/recovery-recovery-built-source-inside-t3277621
Instructions for installing recovery can be found here -
http://forum.xda-developers.com/redmi-2/how-to/ultimate-guide-redmi-2-users-rooting-to-t3294212
Hope this helps :good:
Extract the Rom Zip file
Goto Meta-Inf/com/google/android/
Open updater script as a text file and add the following line just after this
assert(
Add this:
getprop("ro.product.device") == "wt88047" || getprop("ro.build.product") == "wt88047" ||
Or delete the following code from updater script:
assert(getprop("ro.product.device") == "HM2014811" || getprop("ro.build.product") == "HM2014811" || getprop("ro.product.device") == "HM2014812" || getprop("ro.build.product") == "HM2014812" || getprop("ro.product.device") == "HM2014813" || getprop("ro.build.product") == "HM2014813" || getprop("ro.product.device") == "HM2014814" || getprop("ro.build.product") == "HM2014814" || getprop("ro.product.device") == "HM2014815" || getprop("ro.build.product") == "HM2014815" || getprop("ro.product.device") == "HM2014816" || getprop("ro.build.product") == "HM2014816" || getprop("ro.product.device") == "HM2014817" || getprop("ro.build.product") == "HM2014817" || getprop("ro.product.device") == "HM2014818" || getprop("ro.build.product") == "HM2014818" || getprop("ro.product.device") == "HM2014819" || getprop("ro.build.product") == "HM2014819" || getprop("ro.product.device") == "HM2014820" || getprop("ro.build.product") == "HM2014820" || getprop("ro.product.device") == "HM2014821" || getprop("ro.build.product") == "HM2014821" || getprop("ro.product.device") == "HM2014112" || getprop("ro.build.product") == "HM2014112" || getprop("ro.product.device") == "wt88047" || getprop("ro.build.product") == "wt88047" || getprop("ro.product.device") == "wt86047" || getprop("ro.build.product") == "wt86047" || abort("This package is for device: HM2014811,HM2014812,HM2014813,HM2014814,HM2014815,HM2014816,HM2014817,HM2014818,HM2014819,HM2014820,HM2014821,HM2014112,wt88047,wt86047; this device is " + getprop("ro.product.device") + ".");
Only do this with the zip files which you know are for this device only. Doing this with zip files of other devices may damage your device beyond recovery...........
aashishdamrait said:
Extract the Rom Zip file
Goto Meta-Inf/com/google/android/
Open updater script as a text file and add the following line just after this
assert(
Add this:
getprop("ro.product.device") == "wt88047" || getprop("ro.build.product") == "wt88047" ||
Or delete the following code from updater script:
assert(getprop("ro.product.device") == "HM2014811" || getprop("ro.build.product") == "HM2014811" || getprop("ro.product.device") == "HM2014812" || getprop("ro.build.product") == "HM2014812" || getprop("ro.product.device") == "HM2014813" || getprop("ro.build.product") == "HM2014813" || getprop("ro.product.device") == "HM2014814" || getprop("ro.build.product") == "HM2014814" || getprop("ro.product.device") == "HM2014815" || getprop("ro.build.product") == "HM2014815" || getprop("ro.product.device") == "HM2014816" || getprop("ro.build.product") == "HM2014816" || getprop("ro.product.device") == "HM2014817" || getprop("ro.build.product") == "HM2014817" || getprop("ro.product.device") == "HM2014818" || getprop("ro.build.product") == "HM2014818" || getprop("ro.product.device") == "HM2014819" || getprop("ro.build.product") == "HM2014819" || getprop("ro.product.device") == "HM2014820" || getprop("ro.build.product") == "HM2014820" || getprop("ro.product.device") == "HM2014821" || getprop("ro.build.product") == "HM2014821" || getprop("ro.product.device") == "HM2014112" || getprop("ro.build.product") == "HM2014112" || getprop("ro.product.device") == "wt88047" || getprop("ro.build.product") == "wt88047" || getprop("ro.product.device") == "wt86047" || getprop("ro.build.product") == "wt86047" || abort("This package is for device: HM2014811,HM2014812,HM2014813,HM2014814,HM2014815,HM2014816,HM2014817,HM2014818,HM2014819,HM2014820,HM2014821,HM2014112,wt88047,wt86047; this device is " + getprop("ro.product.device") + ".");
Only do this with the zip files which you know are for this device only. Doing this with zip files of other devices may damage your device beyond recovery...........
Click to expand...
Click to collapse
i tried this earlier but i get "status 6" error
and i also checked the path,path of system is correct in updater script but still status 6 error
anandmore said:
You are using wrong recovery. Download and use this one -
http://forum.xda-developers.com/redmi-2/development/recovery-recovery-built-source-inside-t3277621
Instructions for installing recovery can be found here -
http://forum.xda-developers.com/redmi-2/how-to/ultimate-guide-redmi-2-users-rooting-to-t3294212
Hope this helps :good:
Click to expand...
Click to collapse
whenever i flash this recovery or boot this recovery by fastboot,it got stuck at mi logo .this is happening with me for a lot of recoveries
raymond_bqg said:
Do a clean flash[wipe data+cache+system] and install ROM.
Take a backup your current ROM first.
Click to expand...
Click to collapse
by this will i get voLTE in the new rom?
rajatchawla66 said:
by this will i get voLTE in the new rom?
Click to expand...
Click to collapse
If the ROM you are flashing supports volte,then YES.
damon_1991 said:
If the ROM you are flashing supports volte,then YES.
Click to expand...
Click to collapse
flashing a rom after a voLTE supported rom(miui 5.1.1 with voLTE) will give voLTE to the flashed custom rom
will it work after wiping system too?
rajatchawla66 said:
flashing a rom after a voLTE supported rom(miui 5.1.1 with voLTE) will give voLTE to the flashed custom rom
will it work after wiping system too?
Click to expand...
Click to collapse
Yes,as it is about bootloader not about system.
Always take backup of ur Current Rom by T.W.R.P before flashing any rom .
damon_1991 said:
Yes,as it is about bootloader not system.
Click to expand...
Click to collapse
flashing right now
hope for the best
thanks a lot for your help