Related
Hi everyone...I'm new here...I have a problem, I flashed as a secondary ROM the deodexed xwlpf ITALIA 4.0.3 *26-05-2012* and I want to flash the Jkay 14.1. When I go to flash I receive a message of error:
assert failed: getprop("ro.build.PDA") == "I9100 XWLPF"
E:Error in /emmc/CM10/ ROM Stock /JKay/ Deodexed (Custom ROMS)/XWLPF_JKay_Deluxe_v14_1_deodexed.zip
(Status 7)
Installation aborted.
What can I do??Thanks...
alemacis said:
Hi everyone...I'm new here...I have a problem, I flashed as a secondary ROM the deodexed xwlpf ITALIA 4.0.3 *26-05-2012* and I want to flash the Jkay 14.1. When I go to flash I receive a message of error:
assert failed: getprop("ro.build.PDA") == "I9100 XWLPF"
E:Error in /emmc/CM10/ ROM Stock /JKay/ Deodexed (Custom ROMS)/XWLPF_JKay_Deluxe_v14_1_deodexed.zip
(Status 7)
Installation aborted.
What can I do??Thanks...
Click to expand...
Click to collapse
try placing the zip file on the root of ur internal sdcard, then reboot to recovery.
go to 'Dual boot options' and there flash the file using the ' install zip to secondrom' and see
ensure that ur on latest siyah kernel v4.1.5
Sun90 said:
try placing the zip file on the root of ur internal sdcard, then reboot to recovery.
go to 'Dual boot options' and there flash the file using the ' install zip to secondrom' and see
ensure that ur on latest siyah kernel v4.1.5
Click to expand...
Click to collapse
I had already did like you suggested and the installation had abort.. Yes I have 4.1.5 because I have CMX as primary ROM...
Sorry for my bad english :angel:
LeWa OS for Lenovo IdeaPhone P700i
I am not developer, and not want to be one..
Just helping somebody who looking for custom rom fore Lenovo P700i phone. All credit goes to original developer and http://lenovo-forums.ru/
Just come across this beautiful Lewa os ROM for my newly purchased Lenovo P700i displayed on http://lenovo-forums.ru/ site. Since the site is in Russian language, I got trouble in understanding and translating, but succeeded installing it my phone very easily.
Original link
http://lenovo-forums.ru/topic/568-custom-rom-lewa-os-для-lenovo-ideaphone-p700i/
Google translated page
http://translate.googleusercontent....p700i/&usg=ALkJrhjnkBZKBYBU-9j6Dh1ar900LgTsiw
https://www.dropbox.com/s/w3dcc369cmgulgm/Screenshot_2013-01-26-19-32-34.png
Requirements:
1. Rooted P700i with P700i_ROW_S106_121001 firmware (they say it must)
2. CWM-based Recovery v6.0.1.5 (preferred)
3. Custom ROM files LeWa_Lenovo_P700i__ROM_12.11.30_70d22_upd1 (from the above original link site)
Steps:
1. Copy firmware files to SD card
2. Go to CMW recovery
3. Backup present system (optional)
4. Installed from sdcard
5. Reboot the system
6. Go to settings and change the language (settings, 2nd tab (all settings) and 15th row of language and input and then first row, select language (only 3 option available)
7. Reboot again (not necessary)
For installing recovery and rooting (yes first install recovery and then superuser flashing), please follow these steps on site..
1. Recovery
Original link and Google translated..
http://lenovo-forums.ru/topic/438-расширенные-recovery-для-p700i/
http://translate.googleusercontent....p700i/&usg=ALkJrhjE3ULDoqR7epvee9FeWWX7bzWY5g
or
http://bm-smartphone-reviews.blogspot.nl/2012/05/mt6575-flashing-tutorial.html
2. Rooting (CWM flashing)
http://download.chainfire.eu/212/SuperSU/CWM-SuperSU-v0.96.zip
Original firmware
http://www.4shared.com/folder/WqcEx6QF/Original_Firmware.html
For lenovo drivers and flashing tools..
http://translate.googleusercontent....p700i/&usg=ALkJrhjlHkEjppP1Sz5tEhY8RKW6785FRA
Special thanks to Cybermaus and his thread..
http://forum.xda-developers.com/showthread.php?p=31863848#post31863606
This ROM contains minimal application...you will have to flash latest Gapps for talk, maps and other apps (only GMAIL and PLAY STORE included)
& Wifi tethering not working..
and yes declaimer...
I have tried on My Lenovo P700i but I will not responsible for any brick or any problem so flash at uour own risk.
error
aimsforu said:
LeWa OS for Lenovo IdeaPhone P700i
I am not developer, and not want to be one..
Just helping somebody who looking for custom rom fore Lenovo P700i phone. All credit goes to original developer and http://lenovo-forums.ru/
Just come across this beautiful Lewa os ROM for my newly purchased Lenovo P700i displayed on http://lenovo-forums.ru/ site. Since the site is in Russian language, I got trouble in understanding and translating, but succeeded installing it my phone very easily.
Original link
http://lenovo-forums.ru/topic/568-custom-rom-lewa-os-для-lenovo-ideaphone-p700i/
Google translated page
http://translate.googleusercontent....p700i/&usg=ALkJrhjnkBZKBYBU-9j6Dh1ar900LgTsiw
https://www.dropbox.com/s/w3dcc369cmgulgm/Screenshot_2013-01-26-19-32-34.png
Requirements:
1. Rooted P700i with P700i_ROW_S106_121001 firmware (they say it must)
2. CWM-based Recovery v6.0.1.5 (preferred)
3. Custom ROM files LeWa_Lenovo_P700i__ROM_12.11.30_70d22_upd1 (from the above original link site)
Steps:
1. Copy firmware files to SD card
2. Go to CMW recovery
3. Backup present system (optional)
4. Installed from sdcard
5. Reboot the system
6. Go to settings and change the language (settings, 2nd tab (all settings) and 15th row of language and input and then first row, select language (only 3 option available)
7. Reboot again (not necessary)
For installing recovery and rooting (yes first install recovery and then superuser flashing), please follow these steps on site..
1. Recovery
Original link and Google translated..
http://lenovo-forums.ru/topic/438-расширенные-recovery-для-p700i/
http://translate.googleusercontent....p700i/&usg=ALkJrhjE3ULDoqR7epvee9FeWWX7bzWY5g
or
http://bm-smartphone-reviews.blogspot.nl/2012/05/mt6575-flashing-tutorial.html
2. Rooting (CWM flashing)
http://download.chainfire.eu/212/SuperSU/CWM-SuperSU-v0.96.zip
Original firmware
http://www.4shared.com/folder/WqcEx6QF/Original_Firmware.html
For lenovo drivers and flashing tools..
http://translate.googleusercontent....p700i/&usg=ALkJrhjlHkEjppP1Sz5tEhY8RKW6785FRA
Special thanks to Cybermaus and his thread..
http://forum.xda-developers.com/showthread.php?p=31863848#post31863606
This ROM contains minimal application...you will have to flash latest Gapps for talk, maps and other apps (only GMAIL and PLAY STORE included)
& Wifi tethering not working..
and yes declaimer...
I have tried on My Lenovo P700i but I will not responsible for any brick or any problem so flash at uour own risk.
Click to expand...
Click to collapse
hi i followed the steps you indicated above, but it seems that i keep on encountering an error:
assert failed: getprop("ro.product.device") == "p700i" ll getprop("ro.build.product") == "p700i"
E: Error in /sdcard/LeWa_Lenovo_p700i__ROM_12.11.30_70d22_upd1.zip
i've tried downloading another file, but i ended up with the same result. hope that you can help me. thanks!
thanx man good job
secludedNERD said:
hi i followed the steps you indicated above, but it seems that i keep on encountering an error:
assert failed: getprop("ro.product.device") == "p700i" ll getprop("ro.build.product") == "p700i"
E: Error in /sdcard/LeWa_Lenovo_p700i__ROM_12.11.30_70d22_upd1.zip
i've tried downloading another file, but i ended up with the same result. hope that you can help me. thanks!
Click to expand...
Click to collapse
seems that you are using wrong CMW recovery. Use P700i_CWM-based_Recovery_v6.0.1.5
aimsforu said:
seems that you are using wrong CMW recovery. Use P700i_CWM-based_Recovery_v6.0.1.5
Click to expand...
Click to collapse
thanks for your help! im now on LeWa, but it seems that my battery drains faster. do you have the same problem?
what version of LeWa are you currently using?
TIA!
secludedNERD said:
thanks for your help! im now on LeWa, but it seems that my battery drains faster. do you have the same problem?
what version of LeWa are you currently using?
TIA!
Click to expand...
Click to collapse
no problem of battery drain here..used update 2, but rom had some non-english words in some of its features..
just shifted to mix mod v1.0 and loving it..
aimsforu said:
no problem of battery drain here..used update 2, but rom had some non-english words in some of its features..
just shifted to mix mod v1.0 and loving it..
Click to expand...
Click to collapse
where can i get mix mod? tia
secludedNERD said:
where can i get mix mod? tia
Click to expand...
Click to collapse
on the same site of lewa os..
here is the link for all custom rom...
http://translate.googleusercontent....p700i/&usg=ALkJrhiW2ZSUNU0ary7iceSNtkIdpxX5qw
cheers.
Lewa is in boot logo.
I installed the Custom ROM LeWa_Lenovo_P700i_ROM_13.02.05_44be7.zip then it is in the boot logo cannot open in the system. How can I fix this? Thanks a lot.
JB
Thanks a lot buddy.
Is there any ROM out there for P700i where the android version is jelly bean or above?
Hii8 said:
Thanks a lot buddy.
Is there any ROM out there for P700i where the android version is jelly bean or above?
Click to expand...
Click to collapse
None!
Thanks for sharing your knowledge about installing lewa os on lenovo p700i
Thank you Very Much
Sent from my Amoi N828 using XDA Premium 4 mobile app
i have lenovo P700i but when i flash with flashtool show error sdram setup failed error 3002
how to solve it?
Hey,
I'm trying to update my One Plus One from CM11 44S(rooted) to CM12 Nightly, I have downloaded the CM12 Nightly file( cm-12-20150124-NIGHTLY-bacon.zip) from the official cyanogenmod page. I have TWRP [v2.8.4.1] recovery installed on my One Plus.
The issue:
I transferred the .zip file and gapps to my root folder and booted my phone into recovery. I performed a Backup of my ROM with the tools available with TWRP, then I wiped Cache,Dalvik Cache,System and Data. Now when I try to flash the .zip file from the Install section I get the following error.
E: Error executing updater binary in zip '/sdcard/Download/cm-12-20150124-NIGHTLY-bacon.zip'
error flashing zip.....Another statement that looks like an error.
Comparing TZ version TZ.BF.2.0-2.0.0109 to TZ.BF.2.0-2.0.0096
assert failed : oppo.verify_trustzone("TZ.BF.2.0-2.0.0109") == "1"Things I have tried :
1) repeated the above procedure two to three times
2) checked md5 checksum of the .zip file ==> it matched the one on the website
Can someone please help me sove this issue? Am I doing something wrong?
It only happened when youre coming from a KK ROM i dont know why. Flash an earlier nightly build e.g. 20150123 build, then flash 20150124 build. This worked for me.
redundant
I have not tried it yet, but don't you think it would be redundant since 20150123 would itself require a previous build.
Thanks for the support though.
sgovindN said:
I have not tried it yet, but don't you think it would be redundant since 20150123 would itself require a previous build.
Thanks for the support though.
Click to expand...
Click to collapse
Tried it didn't work.
Guys please help
Guys please help. I am too facing the same problem. I also even tried installing the previouds update of 23rd but it didn't help. Please help us...
Me too. I'm having the same problem in the same circumstances as @sgovindN. I've already tried CM12 from 23.01, 22.01, 13.01. The same error
Have all you guys updated your firmware?
Transmitted via Bacon
What do mean by updated firware. I am running on cynogenmod 11.0 44s version.
Pady200550 said:
What do mean by updated firware. I am running on cynogenmod 11.0 44s version.
Click to expand...
Click to collapse
In order to run the latest CM12 nightlies you need updated firmware, it's been mentioned countless times in both of the CM12 threads here on XDA.
Transmitted via Bacon
[Fixed]
I fixed this issue. The problem was the Trustzone issue error that popped up. This trustzone version is in the update binary so here is how you fix it.
Step 01 : Open the zip file with WinZip or WinRAR [do not extract]
Step 02 : Navigate to /META-INF/com/google/android
Step 03 : Open the file 'update-script' with Notepad++(recommended) {Traditional Notepad does not indent code so it is harder to find and edit}
Step 04 : On line 02 change
Code:
assert(oppo.verify_trustzone("TZ.BF.2.0-2.0.0109") == "1");
to
Code:
assert(oppo.verify_trustzone("TZ.BF.2.0-2.0.0096") == "1");
Step 05: Save the file
Similarly people facing Status 7 issue can troubleshoot by changing the model name in the 'updater-script' to the same as theirs, on line 01can fix the "Error".
Make sure you check the md5 checksum of the zip file from the official website, using a tool such as Android File Verifier.
sgovindN said:
I fixed this issue. The problem was the Trustzone issue error that popped up. This trustzone version is in the update binary so here is how you fix it.
Step 01 : Open the zip file with WinZip or WinRAR [do not extract]
Step 02 : Navigate to /META-INF/com/google/android
Step 03 : Open the file 'update-script' with Notepad++(recommended) {Traditional Notepad does not indent code so it is harder to find and edit}
Step 04 : On line 02 change
Code:
assert(oppo.verify_trustzone("TZ.BF.2.0-2.0.0109") == "1");
to
Code:
assert(oppo.verify_trustzone("TZ.BF.2.0-2.0.0096") == "1");
Step 05: Save the file
Similarly people facing Status 7 issue can troubleshoot by changing the model name in the 'updater-script' to the same as theirs, on line 01can fix the "Error".
Make sure you check the md5 checksum of the zip file from the official website, using a tool such as Android File Verifier.
Click to expand...
Click to collapse
I'm pretty sure that isn't actually fixing the issue, that's just sidestepping the safeguard that's built into the updater script.
Transmitted via Bacon
sgovindN said:
I fixed this issue. The problem was the Trustzone issue error that popped up. This trustzone version is in the update binary so here is how you fix it.
Step 01 : Open the zip file with WinZip or WinRAR [do not extract]
Step 02 : Navigate to /META-INF/com/google/android
Step 03 : Open the file 'update-script' with Notepad++(recommended) {Traditional Notepad does not indent code so it is harder to find and edit}
Step 04 : On line 02 change
Code:
assert(oppo.verify_trustzone("TZ.BF.2.0-2.0.0109") == "1");
to
Code:
assert(oppo.verify_trustzone("TZ.BF.2.0-2.0.0096") == "1");
Step 05: Save the file
Similarly people facing Status 7 issue can troubleshoot by changing the model name in the 'updater-script' to the same as theirs, on line 01can fix the "Error".
Make sure you check the md5 checksum of the zip file from the official website, using a tool such as Android File Verifier.
Click to expand...
Click to collapse
Thanks for your help. i have now successfully installed CynaodenMod 12 on to my Oneplus One.
Not able to update new rom by cyandelta. Guys help.
Pady200550 said:
Not able to update new rom by cyandelta. Guys help.
Click to expand...
Click to collapse
Which brings me back to my previous question earlier in the thread; have you updated your firmware?
Transmitted via Bacon
Yes now i able to update. I have searched regarding this. You have to download a file bacon firmware update and then u can install cm 12 nigtley
Pady200550 said:
Yes now i able to update. I have searched regarding this. You have to download a file bacon firmware update and then u can install cm 12 nigtley
Click to expand...
Click to collapse
That's right, that'd what you needed to do in the first place. The method posted by @sgovindN is not a solution at all, it just sidesteps the safeguard that's there to ensure that you're on the right firmware.
Transmitted via Bacon
LMAO I can't believe what @sgovindN did there.... TZ assert is there for a reason, and your "fix" is just a bs work around, @Pady200550 recent posts prove that. It would have taken far less effort to do it the proper way instead of coming up with that
If anyone ever find this thread in the future, DO NOT do what @sgovindN posted. Do it the proper way as @timmaaa posted with the updated firmware
Sent From Lollipopified Bacon Goodness!
Firmware Update?/
Pady200550 said:
Yes now i able to update. I have searched regarding this. You have to download a file bacon firmware update and then u can install cm 12 nigtley
Click to expand...
Click to collapse
I am on 4.4.4 custom rom PACman but unable to intall CM12/resurrection remix/Liquidsmooth/Blisspop (All 5.0 based) it gives me error : E: Error executing updater binary in zip '/sdcard/Download/cm-12-20150124-NIGHTLY-bacon.zip'
error flashing zip.....
please explain how did you mange to install CM12 ?
sagar0592 said:
I am on 4.4.4 custom rom PACman but unable to intall CM12/resurrection remix/Liquidsmooth/Blisspop (All 5.0 based) it gives me error : E: Error executing updater binary in zip '/sdcard/Download/cm-12-20150124-NIGHTLY-bacon.zip'
error flashing zip.....
please explain how did you mange to install CM12 ?
Click to expand...
Click to collapse
Are you using multirom? If yes, update to latest it will install blisspop for sure as secondary, I dunno about the rest
Since you're still on KitKat you need to install the cm12 firmware first though. You can find it in blisspop thread
Sent From Lollipopified Bacon Goodness!
I'm with cm11s as a primary in multirom and managed to install Liquidsmooth lollipop. Also managed to install CM12 but it crashes on load, and I get the "E:Error executing updater binary in zip '/tmp/mr_update.zip'" when trying to install Blisspop or tugapower.
From what you guys say, I shouldn't be able to run liquidsmooth as my "basis" is the CM11S firmware, but fact is I can xD
Isn't there a way to flash the updated firmware only over the secondary (lollipop) rom? Or is it possible to run CM11S as a secondary, with CM12 as primary?
I really want to try CM12 (to see the "future" for my OpO), but don't want to lose my fully customized CM11 just yet
Yo people !
With the new Incremental update for YNG1TAS2I3 for CM 12, when i try to update via TWRP i get an error
Package build print not verified as in attachment
Just wanted to confirm from experts
Deleting those lines from the updater-script solves the problem ?
getprop("ro.build.fingerprint") == "oneplus/bacon/A0001:5.0.2/LRX22G/YNG1TAS17L:user/release-keys" ||
getprop("ro.build.fingerprint") == "oneplus/bacon/A0001:5.0.2/LRX22G/YNG1TAS2I3:user/release-keys" ||
abort("Package expects build fingerprint of oneplus/bacon/A0001:5.0.2/LRX22G/YNG1TAS17L:user/release-keys or oneplus/bacon/A0001:5.0.2/LRX22G/YNG1TAS2I3:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
Or a better fix
Will flashing the stock CM12 recovery and flashing the incremental update help me ?
Can any one please upload and link me to the official CM12 recovery.img file
The Official CM recovery link is dead !
PS: Thank you Cynogen & OnePlus for the newest updates !
There was the exact same question asked and answered today....
http://forum.xda-developers.com/showthread.php?t=3137841
Lutzchker said:
that one isn't clear. If you did it succesfully can you help?
Click to expand...
Click to collapse
Either update the full ROM (not the Delta file) or choose a different .zip
Oh, and also the official OTA can not be installed from TWRP, only from Cyanogen recovery.
I'll rom whole build. Thanks again
Why not simply format system and then flash? Always works for me and all the data is there alogn with the settings. All i need to do is change dpi, build new host files by adaway, flash xposed zip and tada! it works as it should! the whole process takes not more than 3 minutes.
Hi there,
I'm just trying to install TWRP and Cyanogenmod 12.1 (cm-12.1-20151230-NIGHTLY-taoshan / open_gapps-arm-5.1-nano-20151225), and having some problems.
Sorry for the long mail, at the end I have put a short summary of the current status of my Xperia L (C3105).
I succeeded to unlock the bootloader, afterwards I installed the stock rom (C2105_15.3.A.1.17_1272-2171 R2B_Generic DE). So far, so good.
However, all attempts to install TWRP and/or Cyanogenmod have failed so far.
At first I tried to install TWRP (latest version) via the app method (TWRP manager app form Google app store). The app reported a successful flash, but somehow I could not get to recovery when I rebooted while rocking the vol up/down buttons. Also the notification light does not any more turn purple when booting up.
Afterwards I flashed the above stock rom again because it was not clear for me whether the phone was stucked in a boot loop. I guess that this also re-installed the stock recovery again? Anyhow, since then and up to now even when I reboot and constantly press the volume buttons (both) while the phone is booting up, it still boots into android and not into the recovery.
So I guess that the recovery is not correctly installed at the moment.
I tried also with the XDA recovery-installer-taoshan-1.3.apk to install another version of TWRP (an older one), but this did not work as well, with a very similar behaviour, but afterwards I was not either to boot anything, neither the recovery nor the android system, but was possible to boot into fastboot mode so that I could re-flash the stock rom.
Now, even when I neglect the recovery and try to install cynogenmod with the command "adb sideload update.zip" (obviously with exact file name instead of update.zip), it always says the following:
ADB server didn't ACK
* failed to start daemon *
adb server is out of date. killing...
*daemon started successfully *
error: closed
I have to say that after flashing the stock rom and connecting the phone to the computer, I denied to re-install the PC companion software, because from my perspective all drivers etc should be installed. But I do not want to exclude that this could also be an issue here.
I just tried to install the universal ADB drivers, seleted repair drivers, but still the ADB connection seems to not work properly.
My device manager reports for the driver "Sony so0103 ADB Interface Driver".
Just to summarize:
- I have rooted the phone successfully (also re-rooted after flashing the stock rom)
- the bootloader is unlocked (confirmed via service menu)
- recovery does not work
- above mentioned stock rom is installed
- stock rom is booting fine
Does anyone have a suggestion of how to solve the problems and what the next steps should be? I would also very much appreciate any hint on what I have possibly done wrong in order to learn from it.
Many thanks in advance and my best regards,
Henning
Just a note:
If I remember well, I'm not sure if the ADB drivers were successfully installed. The last time when I used ADB successfully, it was with linux, and this time I tried with windows, because the flashtool seems to work only with windows (or I just do not know how to operate it in linux on the shell).
Should I just try to re-install TWRP with the app method, and without rebooting flash cyanogenmod using the "adb sideload update.zip" command? Or is there any other command which would be preferred?
I have also busybox and a terminal emulator installed, could also direclty flash it from the phone ...
Thanks in advance!
Cheers,
Henning
While using the app, when it reboots, open the app again and click TWRP again.. it'll work.. or it may be an incomplete download. delete twrp.tar from the internal SD and try again
Hi,
I hope someone could help me quickly:
I again installed TWRP 2.8.7.0 via the TWRP manager app method.
Afterwards I flashed with Flashtool the extracted boot.img from the CM-12.1 zip file.
This time I finally could boot into the recovery!
But now my problem is that the CM zip file will not be installed by TWRP.
Before the install, I wiped cache, dalvik cache, system, data (made a backup also).
Any suggestions? Is my TWRP 2.8.7.0 buggy, or the CM zip file, or is there anything I could have missed?
Many thanks in advance and sorry to bother you again!
Cheers,
Henning
Here is the log that I get from TWRP:
Installing '/sdcard/.....'
Checking for MD5 file ...
Skipping MD5 check: no MD5 file found
This package is for device: C2105,C2104,c2105,c2104,taoshan; this device is .
E:Error executing updater binary in zip '/sdcard......'
Error flashing zip '/sdcard/......'
Updating partition details...
...done
xleng said:
Here is the log that I get from TWRP:
Installing '/sdcard/.....'
Checking for MD5 file ...
Skipping MD5 check: no MD5 file found
This package is for device: C2105,C2104,c2105,c2104,taoshan; this device is .
E:Error executing updater binary in zip '/sdcard......'
Error flashing zip '/sdcard/......'
Updating partition details...
...done
Click to expand...
Click to collapse
obviously twrp manager app is ****ty
either use corphishs app to get my twrp versions or do the following:
1. in twrp go to
advanced->terminal command->ok
there enter :
setprop ro.build.product taoshan
setprop ro.product.name taoshan
2. flash the rom you want
3. get the app and a better twrp ;-P
Sent from my Xperia T using XDA Free mobile app
Many thanks for the quick reply!
I will try in a minute and report the results.
One question, I think that I may have already wiped system before I took the backup in TWRP.
In case I would reboot or switch off now (e.g. in order to put the SDCARD into the computer and put another version of TWRP and/or CM on it), would I be able to boot into the recovery again or would I hard-brick the device then?
I just tried to modify the update file on the computer and re-load it via sideload, but for some reason sideload could not be activated ... I will try now with your suggestion
Thanks in advance!
Still the same error .... (
I also tried to set other variables, like:
setprop ro.product.model taoshan
setprop ro.product.brand taoshan
setprop ro.product.name taoshan
setprop ro.product.device taoshan
setprop ro.product.board taoshan
setprop ro.product.manufacturer taoshan
Does not work ... it seems that the device recognized is still empty / ""
It's really weird. when I execute the shell command "getprop ro.product.name" I get "taoshan", but the updater-script does not recognize this for any reason. Probably it's the TWRP which is faulty as you indicated.
Now i just rebooted the device and connect via flashboot in order to flash the stock FTF again via flashtool.
Now I'm on stock rom again and lucky that the device is not broken (though we still have another xperia L around here from my wife, before she got a windows phone ) - hope that sooner or later I could use one of them as a debugging / experimental device though
Well, it's late for today, I will resume most likely tomorrow evening and would like to thank you once more for your very valuable hints!
Tomorrow i will try to install your version of TWRP - it is this one, correct? :
http://forum.xda-developers.com/xperia-l/development/app-recoveries-recovery-installer-t3187915
I guess this is the TWRP that you've installed as well on your device?
By the way, while I'm getting used to the process of flashing stock roms, rooting, installer recoveries etc, do you have any recommendations on certain custom ROM / GAPPS combination?
May I ask what you're using at the moment?
Just thinking about whether I will continue with CM or might switch to RR or something else ...
Cheers,
Henning
I'm just thinking if the updater-script itself has a bug:
In the first line I have:
Code:
assert(getprop("ro.product.device") == "C2105" || getprop("ro.build.product") == "C2105" || getprop("ro.product.device") == "C2104" || getprop("ro.build.product") == "C2104" || getprop("ro.product.device") == "c2105" || getprop("ro.build.product") == "c2105" || getprop("ro.product.device") == "" || getprop("ro.build.product") == "" || getprop("ro.product.device") == "taoshan" || getprop("ro.build.product") == "taoshan" || abort("This package is for device: C2105,C2104,c2105,c2104,taoshan; this device is " + getprop("ro.product.device") + "."););
I'm just wondering if the problem is because the abort() command is part of the assert() function, but I#m not sure about the syntax.
Cheers,
Henning
xleng said:
I'm just thinking if the updater-script itself has a bug:
In the first line I have:
Code:
assert(getprop("ro.product.device") == "C2105" || getprop("ro.build.product") == "C2105" || getprop("ro.product.device") == "C2104" || getprop("ro.build.product") == "C2104" || getprop("ro.product.device") == "c2105" || getprop("ro.build.product") == "c2105" || getprop("ro.product.device") == "" || getprop("ro.build.product") == "" || getprop("ro.product.device") == "taoshan" || getprop("ro.build.product") == "taoshan" || abort("This package is for device: C2105,C2104,c2105,c2104,taoshan; this device is " + getprop("ro.product.device") + "."););
I'm just wondering if the problem is because the abort() command is part of the assert() function, but I#m not sure about the syntax.
Cheers,
Henning
Click to expand...
Click to collapse
no thats all ok...
i dont know why the terminal command didnt work for you... you must have done it wrong!
yes the twrp is the one from me... and no i dont use it because i have no longer XL since my is broken...
Sent from my Xperia T using XDA Free mobile app
Hi,
I have downloaded and installed your app, as well as the latest CM-12.1 version (2016-01-19) with the corresponding GAPPS nano package.
I applied the following procedure:
1) flashed TWRP
2) rebooted to fastboot mode, extracted and flashed the boot.img from the CM-package
3) rebooted to recovery, then I recognized that probably the boot.img has overwritten the TWRP recovery, since it was the CM recovery that started
4) tried to flash CM-12.1, which failed after the verification, with the message that it can't be installed on top of incompatible data; what I've noticed was that the CM recovery did not allow me to wipe the system, don't know if that could have caused the problem.
Trying further ....
Cheers,
Henning
Hi,
I repeated the same steps just without flashing the boot.img file, when rebooting to recovery TWRP was there, and was able to flash the latest CM-12.1 which is currently booting!
Many thanks to all contributors of this ROM and to SdtBarbarossa for advice!!!
Cheers,
Henning
PS: Probably I will comment on something later ...
I installed both CM and GAPPS directly after each other, e.g. without an intermediate boot into android.
Now I have messages telling me that the google apps have been closed after each start-up.
I think I probably need to re-flash CM, then reboot, and then flash GAPPS again, right?
Even the google app store was not working, and I could also not install the TWRP with the apk file because it didn't recognize the device.
Installing stock rom again for tonight, tomorrow I will flash CM again ...
Even if the app doesn't recognize your device, flash it.. It works 100% .. and after flashing gapps you should try factory resetting .. It might work..
Good point with the favtory Reset! Thanks!
Hi,
CM-12.1 works now very well (I noticed the flashlight bug which I believe has been reported several times already, but that's not really troubling me) ...
Overall, it's really an awesome ROM! Very fast and responsive (much much faster UI feeling than with the initial SONY stock ROM), and really great to see a recent android version running that smoothly on this little device!
Many thanks again to all contributors of this ROM! Really a great piece of work!
Cheers
Henning
xleng said:
Hi,
I have downloaded and installed your app, as well as the latest CM-12.1 version (2016-01-19) with the corresponding GAPPS nano package.
I applied the following procedure:
1) flashed TWRP
2) rebooted to fastboot mode, extracted and flashed the boot.img from the CM-package
3) rebooted to recovery, then I recognized that probably the boot.img has overwritten the TWRP recovery, since it was the CM recovery that started
4) tried to flash CM-12.1, which failed after the verification, with the message that it can't be installed on top of incompatible data; what I've noticed was that the CM recovery did not allow me to wipe the system, don't know if that could have caused the problem.
Trying further ....
Cheers,
Henning
Click to expand...
Click to collapse
I'm facing the same issue not able to flash.
Can you give step by step instructions?
Hi, what is your device status at the moment? What did you do so far?