Assert failed getprop ro product device как исправить

Sometime when we are installing a new custom ROM, we get  " assert failed: getprop(‘ro.product.dervice’), " and show " status 7 installation aborted" error in

Sometime when we are installing a new custom ROM, we get  ” assert failed: getprop(‘ro.product.dervice’), ” and show ” status 7 installation aborted” error in the CWM recovery or TWRP. This is a result of the “model number” or device ID changes on your android phone or tablet.

Now we can easily fix this issue by just a simple ROM zip file tweak. Personally I face this issue when I’m installing CM10 ROM on my phone. There’s mainly two reasons, format system partition or change the model number.

In my case, few days agao I have changed the my phone modle number to install the new jelly bean camera apk. Then i got this error. Fortunately I remember,  I have changed my phone model number. Therefore I follow this step and it work.

If this method doesn’t work for you, you have to install new firmware. In my situation, I didn’t need to flash the firmware. Apart from that, if you format your system partition, sometime you may receive this error.

Warning!

Before follow this tutorial, make sure that you have downloaded the correct ROM for your device. If you install the wrong device ROM, your phone/tablet can be brick or damage.

Note!

I have tested this method with Winzip (trial version can do this work) and NotePad++ applications. These application make that process easier.

How to fix android custom ROM status 7 installation abort assert failed: getprop(‘ro.product.dervice’) error in Recovery.

  • Download and install the Notepad++ and Winzip (no need to purchse full version, just download trail) computer application on your computer.
  • Copy the downloaded ROM into the desktop, if its not in there.
  • Use a zip file extractor such as  “Winzip”, 7zip or Winrar”. ( I used Winzip)
  • Extract the downloaded ROM to the desktop separate folder. If you have Winzip no need to extract it, you can preview it. So just follow 5th step (next step).
  • Go to the following folder in that ROM.

META-INF/com/google/android

  • Then double click on the “updater-script” file.

  • Now you can see following type open with window, in that window select “Notepad++” and click “OK”.

  • Then you can see the following type window. Remove its first 3 lines which i highlighted in the following screenshot (click on the image for enable it). This line cause this ” assert failed: getprop(‘ro.product.dervice’), status 7 installation aborted” error.

  • Now we can save this updater-script” file. To do that click “Notepad++” application top “Save” button and close the Notepad++.
  • Now make a zip file using that extracted ROM. If you use Winzip, now you can see the zip file update window. Click its “Update zip file with changes” option.
  • Now copy that edited zip file to your phone SD card and install it using your phone/tablet recovery, just normally.
  • Forum
  • LG Android Phones
  • More LG Phones
  • LG Optimus Series
  • Virgin Mobile Optimus V
  • Optimus V Rooting, ROMs, and Hacks

  1. sammyz's Avatar

    You get this error or something similar:

    Code:

    assert failed: getprop("ro.product.device") == "thunderc" || getprop("ro.build.product") == "thunderc"

    You do this with 7-Zip/WinRAR

    Note: DO NOT EXTRACT ROM!
    In the ROM go to:

    /META-INF/com/google/android/updater-script

    1)Open updater-script with a script editor such as notepad/notepad++ (makes things 10x easier), or gedit if you use linux

    2)Delete the first line of code (all the way up to the first semicolon you see) and delete the first semi-colon as well

    Do not go past the first semiclon when deleteing and DO NOT forget to delete the first semicolon.

    Cheers!

    Now please stop posting this problem on everyone’s ICS ROMs…..
    Someone make this a sticky please

    06-22-2012 01:51 PM

  2. ThatGuyLurkin's Avatar

    I don’t understand. Why not just flash another recovery rather than waiting? xD

    Sent from my LG-VM670 using Tapatalk 2

    06-22-2012 02:06 PM

  3. sammyz's Avatar

    Originally Posted by ThatGuyLurkin

    I don’t understand. Why not just flash another recovery rather than waiting? xD

    Sent from my LG-VM670 using Tapatalk 2

    Waiting for what??? This is faster, takes less time, and you don’t have to find a working recovery with these messed up assert scripts……BobZhome deletes them when he remembers to anyways…I delete them on all my ports….it’s better for the dev to just delete them than to have 20 pages of assert fails…so I made this thread.

    06-22-2012 02:12 PM

  4. ThatGuyLurkin's Avatar

    I mean waiting for it to be compatible.

    But this helps me. I don’t understand a thing about update scripts.

    Sent from my LG-VM670 using Tapatalk 2

    06-22-2012 02:57 PM

  5. sammyz's Avatar

    Originally Posted by ThatGuyLurkin

    I mean waiting for it to be compatible.

    But this helps me. I don’t understand a thing about update scripts.

    Sent from my LG-VM670 using Tapatalk 2

    These ROMs are all compatible……it’s just a stupid line in the updater script that I think is completely unnecessary…..

    06-22-2012 03:05 PM

  6. andrewnelson23's Avatar

    What is an assert script?

    06-23-2012 10:09 PM

  7. sammyz's Avatar

    Originally Posted by andrewnelson23

    What is an assert script?

    All it does is check to make sure you are flashing the rom on the correct device…

    Sent from my Optimus M

    06-23-2012 10:47 PM

  8. drewwalton19216801's Avatar

    Originally Posted by sammyz12

    All it does is check to make sure you are flashing the rom on the correct device…

    Sent from my Optimus M

    That’s certainly one of the things you can do with asserts but not the only thing it does.

    Assert evaluates a condition (in this case a command, getprop). If the condition returns true (or returns an expected value) the script carries on. If the condition returns false (or returns an unexpected value) it throws an error.

    For example, I can check to see if the file «/system/etc/dooderbutt» exists (and subsequently create it if it doesn’t) like so:

    Code:

    assert(file_exists("/system/etc/dooderbutt") || create("/system/etc/dooderbutt"))

    If the above assert command is unable to create the file for some reason, the script should throw an error because it was an unexpected result.

    06-23-2012 11:34 PM

  9. gyanos422's Avatar

    any way that I do this from the phone? For some reason my phone won’t show up as usb storage on my laptop. It doesn’t even charge when plugged in.. Now my girls phone (we both have ov’s) works fine and both are rooted, with custom roms installed. Mine charges fine when using a wall charger but I can’t get usb store or debugging to come on when connecting it to a pc.. Anyway, can I edit his file with an app since I can’t transfer it back and forth?

    06-24-2012 09:43 AM

  10. sammyz's Avatar

    Originally Posted by gyanos422

    any way that I do this from the phone? For some reason my phone won’t show up as usb storage on my laptop. It doesn’t even charge when plugged in.. Now my girls phone (we both have ov’s) works fine and both are rooted, with custom roms installed. Mine charges fine when using a wall charger but I can’t get usb store or debugging to come on when connecting it to a pc.. Anyway, can I edit his file with an app since I can’t transfer it back and forth?

    This wouldn’t effect USB problems…..

    Sent from VM670 on MetroPCS

    06-24-2012 12:40 PM

  11. sammyz's Avatar

    Originally Posted by drewwalton19216801

    That’s certainly one of the things you can do with asserts but not the only thing it does.

    Assert evaluates a condition (in this case a command, getprop). If the condition returns true (or returns an expected value) the script carries on. If the condition returns false (or returns an unexpected value) it throws an error.

    For example, I can check to see if the file «/system/etc/dooderbutt» exists (and subsequently create it if it doesn’t) like so:

    Code:

    assert(file_exists("/system/etc/dooderbutt") || create("/system/etc/dooderbutt"))

    If the above assert command is unable to create the file for some reason, the script should throw an error because it was an unexpected result.

    I only meant the first assert line, not all of them

    Sent from VM670 on MetroPCS

    06-24-2012 12:41 PM

  12. DailyRich's Avatar

    I extracted the file, made the edit, re-zipped it, and moved it to my SD card. Now I don’t get the error, but all it does is go:

    Installing update…
    Installation aborted.

    Doesn’t even think about it, just goes right to the error. This is with signature verification and script assertion disabled; either of those on produces their respective invalid errors.

    09-22-2012 10:12 PM

  13. koeylondon's Avatar

    Note: You should NOT unzip the entire package. Use 7Zip or Winrar to extract ONLY the file you need, edit it, and replace it. If you unzip the whole thing, it will corrupt.

    09-23-2012 12:27 AM

  14. sammyz's Avatar

    Originally Posted by koeylondon

    Note: You should NOT unzip the entire package. Use 7Zip or Winrar to extract ONLY the file you need, edit it, and replace it. If you unzip the whole thing, it will corrupt.

    Forgot to add that…OP updated.

    Sent from my Optimus S running VM670ZV5 on MetroPCS.

    09-23-2012 07:59 AM

  15. EarthnFire78's Avatar

    Should also add that try flashing in the recovery first before editing any file. CWM-Blue-Recovery does not need the file edited, as the build.prop was fixed over three months ago.

    09-25-2012 02:23 AM

  16. sammyz's Avatar

    Originally Posted by EarthnFire78

    Should also add that try flashing in the recovery first before editing any file. CWM-Blue-Recovery does not need the file edited, as the build.prop was fixed over three months ago.

    Same with CWM-Green
    I don’t think people want to flash another recovery when the deal of this is just removing one line in a script

    I am not going to add that for the sake that it would endorse one’s recovery over another when both can flash ICS fine.

    The main point of this thread was so people wouldn’t have to flash another recovery, the other point was so that there wouldn’t be over 200 posts of people complaining over a Status 7 assert failed error.

    Sent from my Optimus S running VM670ZV5 on MetroPCS.

    09-25-2012 07:29 AM

  17. Catfish81's Avatar

    This method worked for flashing Paranoid Android 4.1.2 Jelly Bean v1.8 ROM onto a Samsung Galaxy Tab 10.1 3G tablet, online this is known as the P7500 model, and the ROMs are usually named «p4». The assert failure message says it cant ID the device as a p4 device so it quits.

    I tried updating my CWM to the latest and this also failed. Only removing the line from the update script as described above worked.

    Thanks for the fix!

    11-26-2012 02:44 AM

  18. Tony Usi's Avatar

    Thank you so much, I flash camera 4.2 on my nexus s and it brick my phone, try to flash strawberry 4.1.2 but failed..i follow your direction of deleting script to the the last semi colon…..works fine….thank again…

    12-04-2012 02:58 PM

  19. Stvpagn's Avatar

    Originally Posted by sammyz

    You get this error or something similar:

    Code:

    assert failed: getprop("ro.product.device") == "thunderc" || getprop("ro.build.product") == "thunderc"

    You do this with 7-Zip/WinRAR

    Note: DO NOT EXTRACT ROM!
    In the ROM go to:

    /META-INF/com/google/android/updater-script

    1)Open updater-script with a script editor such as notepad/notepad++ (makes things 10x easier), or gedit if you use linux

    2)Delete the first line of code (all the way up to the first semicolon you see) and delete the first semi-colon as well

    Do not go past the first semiclon when deleteing and DO NOT forget to delete the first semicolon.

    Cheers!

    Now please stop posting this problem on everyone’s ICS ROMs…..
    Someone make this a sticky please

    Hi I’m trying to find the updater-script inside my «cm-10-20121215-NIGHTLY-i9300», there isn’t one.
    I’d appreciate some assistance with this as I’m trying to get out of stock 4.1.1 since it keeps giving me a bootloop after applying an update.zip from my titanium back up of all my apps+data.

    12-16-2012 05:58 PM

  20. Cristian Barreto's Avatar

    IT Works!, thank you!, just delete the first line from «assert…» to the semicolon and delete it too «… ;»

    THANK YOU!

    01-03-2013 08:38 AM

  21. Cristian Barreto's Avatar

    is just on /META-INF/com/google/android/updater-script , the file dosent have extension, just open it on a text editor and delete the first line from assert to the semicolon (delete it too).

    01-03-2013 08:40 AM

  22. Unc0ntr0ld's Avatar

    thanks so much, i did exactly that and now running PA v2.55 on my s3 couldnt be happier.

    EDIT: BTW, for windows user, it will ask you to save the file and will automatically save it under txt extention. You won’t see it if you didn’t uncheck «hide extensions for known file types» in the folder options. so make sure you uncheck it. Then delete just .txt from the save file and copy it back to the zip. It will ask if you want to replace that file, say yes. Et voila.

    hope this helps.

    01-14-2013 02:54 AM

  23. Damien Murtagh's Avatar

    Ok. I’m missing something. How do you extract just one file from the zip and then replace it. I’m using 7-Zip and every time I edit the file, or try to replace the script file with the edited one I get an error about duplicate files.

    01-19-2013 11:48 AM

  24. AndyOpie150's Avatar

    Use zipplus by Express Zip File Compression Software Company / NCH Software.
    It allows you to delete, add folders, or add files. When done there is no need to resign zip. It’s only a 14 day trail period. When trial period is done delete all instances of it off computer and download new.

    Sent from my LG-VM670 using Android Central Forums

    01-19-2013 04:50 PM

  25. sammyz's Avatar

    Originally Posted by AndyOpie150

    Use zipplus by Express Zip File Compression Software Company / NCH Software.
    It allows you to delete, add folders, or add files. When done there is no need to resign zip. It’s only a 14 day trail period. When trial period is done delete all instances of it off computer and download new.

    Sent from my LG-VM670 using Android Central Forums

    Or use WinRAR with an annoying pop-up

    01-22-2013 09:44 PM

  • Home
  • Forum
  • LG Android Phones
  • More LG Phones
  • LG Optimus Series
  • Virgin Mobile Optimus V
  • Optimus V Rooting, ROMs, and Hacks
  • [SOLVED] assert failed


LINK TO POST COPIED TO CLIPBOARD

  • #1

Hi
I got an Hongmi WCDMA and I want to update it to stable V5 but without success
I’m able to install or re-install these 2 roms without problems:

miuiandroid_multi_V6W_3.12.13_jb-4.2​

or

miuiandroid_multi_HM2013023_WCDMA_JHBCNAH4.0_jb-4.2​

but not the last stable one:

miuiandroid_multi_HM2013023_WCDMA_JHBCNAL5.0_jb-4.2​

even the official downloaded on the official site

miui_HM2W_JHBCNAL5.0_8197122014_4.2​

I always got an error

assert failed: getprop(«ro.product.device» == «HM2013023» || «ro.build.product» == «HM2013023»

I tried with different recovery and got always the same error
— CWM V5 english WCDMA
— MIUI RECOVERY WCDMA 1.0
— TWRP 2.5.0.0
I also tried CWM V6 english WCDMA (touch) but i got problem with the detection of my SD card
I fully wiped (all the wipes possible with TWRP) many times
Did someone got an idea?

DeepSpace


  • #3

its easy solution.

open the zip file, do not unzip, OPEN IT, and navigate to
META-INF > com > Google > android

— Rename the file updater-script to updater-script.doc
— Double clik to open it and delete this line

du1x.jpg

— after deleting the line, save and close de file.
— Rename the file back to updater-script and close the zip.
— Flash the rom and voilá ;)

  • #4

it shouldn’t happens with twrp cuz ro.product.device is set as HM2013023 in default.prop (as updater script wanna see)
i successfully installed miui_HM2W_JHBCNAL5.0_8197122014_4.2 and miuiandroid_multi_HM2013023_WCDMA_JHBCNAL5.0_jb-4.2 for test using twrp

  • #5

I had that assert issue, I installed the twrp and didn’t solved. The solution I found was as I mentioned above.

  • #6

it shouldn’t happens with twrp cuz ro.product.device is set as HM2013023 in default.prop (as updater script wanna see)
i successfully installed miui_HM2W_JHBCNAL5.0_8197122014_4.2 and miuiandroid_multi_HM2013023_WCDMA_JHBCNAL5.0_jb-4.2 for test using twrp

I think it is checking the property in the default.prop in the TWRP boot image. And that is not HM2013023 as I recall correctly.

Last edited: Feb 1, 2014

  • #7

Didn’t work either with twrp or cwm recoveries until I correct the file as mentioned

  • #8

Okay, Thanks pjovp it works
Just here it’s my step-by-step for my Hongmi WCDMA
1) Install last found developper version to have root

miuiandroid_multi_V6W_3.12.13_jb-4.2
(You may have to do a «wipe all» if you came from stable 4)​

2) Install TWRP 2.5.0.0 recovery (should work with other) with MobileUncle
3) Modified miuiandroid_multi_HM2013023_WCDMA_JHBCNAL5.0_jb-4.2 as proposed in post #3 by pjovp
4) Transfer the modified_miuiandroid_multi_HM2013023_WCDMA_JHBCNAL5.0_jb-4.2 zip file in the phone
5) reboot in TWRP recovery
6) flash the modified_miuiandroid_multi_HM2013023_WCDMA_JHBCNAL5.0_jb-4.2

(uncheck the zip signature control since it’s not the orginal rom anymore)​

7) Reboot and it works :)

Since there is no more signature to secure the file, be sure that you have downloaded your source rom from a secure place (directly from xiaomi.eu for the multi for example)

I still don’t know why it did not work with the official rom but this workaround did the job thanks again pjovp

BR

Christian

  • #9

why you did all this exactly???
don’t tell me that was to try to preserve the root, because there is already a roo.zip that works with the stable versions.
You just have to install the rom and after flash the roo.zip, easy as that lol

Just now I have tried to install the lastest 4.1.24 and I got this error:

E: Error executing updater binary in zip /sdcard/xxxxxx
Error flshing zip /sdcard/xxxxx

Looks like with miuiandroid this is a lotary as up to now every rom has diferent instalation requirements, OMFG.
Who the hell does this things exactly?

Thanks

  • #10

Just now I have tried to install the lastest 4.1.24 and I got this error:

E: Error executing updater binary in zip /sdcard/xxxxxx
Error flshing zip /sdcard/xxxxx

Looks like with miuiandroid this is a lotary as up to now every rom has diferent instalation requirements, OMFG.
Who the hell does this things exactly?

Thanks

Where did you get a 4.1.24 weekly version for HongMi?

Gesendet von meinem MI 2 mit Tapatalk

  • #12

If you think that Xiaomi Hongmi WCDMA — Stable 5.0 Multilang there is 4.1.24, that is not the case.

  • #13

Well, so something changed in the file available for download, because this one I can’t install by any means so I suppose that is just to install with stock recovery

  • #14

why you did all this exactly???
don’t tell me that was to try to preserve the root, because there is already a roo.zip that works with the stable versions.
You just have to install the rom and after flash the roo.zip, easy as that lol

I did a return to a rooted version like 3.12.13 to be able to (re-)install TWRP, Stable4 is not rooted and to change the recovery the root access is needed.
After having flashed Stable5 and verified that it works well, I install the root.zip you proposed in another thread and now I have a Stable5 with root access.

  • #15

Twrp can be installed via stock recovery, I think

  • #16

I think it is checking the property in the default.prop in the TWRP boot image. And that is not HM2013023 as I recall correctly.

yes, in twrp boot image this values are set properly. The only one thing i can assume — WCDMA twrp installed in TD phone, or TD twrp installed in WCDMA phone

  • #18

So to avoid assert problem, use TWRP from here.

I tried to re-install the (original?) TWRP proposed by glsf91 over mine (I boot in recovery and flash the proposed zip file)
and now it works as expected, I can flash directly downloaded rom without modified them.
Definitely an error in my previous proprieties

Thanks for all your help
Christian

I installed Firefox OS (version 1.2) which was downloaded from XDA with ClockworkMod on my Nexus 7 , but i got error messages.

The error messages showed :

Installing update...
assert failed: getprop("ro.product.device") == "flo" ||
               getprop("ro.build.product") == "flo" ||
               getprop("ro.product.device") == "deb" ||
               getprop("ro.build.product") == "deb"

E:Error in /sdcard/0/b2g_flo_1.2_20131011-2.zip
(Status 7)

And I checked the updater-script with Sublime Text 2 :

assert(getprop("ro.product.device") == "flo" || getprop("ro.build.product") == "flo" ||
       getprop("ro.product.device") == "deb" || getprop("ro.build.product") == "deb");

ui_print("FirefoxOS installer");
show_progress(1.00000, 10);

unmount("/system");
format("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "0", "/system");
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");

So i removed the assert part and packed a new zip.
But i still couldn’t install it without any error message.
And console showed :

Opening update package...
Installing update...
Installation aborted.

Can anyone help me to fix this problem ?
That will be a great help !

  1. I have a replacement Verizon Galaxy Nexus (my original Gnex had a small coffee incident) that I’ve successfully unlocked the bootloader and rooted, but I can’t seem to install any custom ROMs. I’ve tried three different ones and I keep the the error message:

    assert failed getprop ro.product.device

    I can install custom kernels though. I’ve tried returning it back to stock and rooting it again. I’ve tried multiple versions of BusyBox.

    Any ideas?


    1. Download the Forums for Android™ app!

      Download

  2. jhawkkw

    Which custom recovery are you using just out of curiosity?

  3. I’ve tried both TWRP and CWM.

  4. jhawkkw

    I know it sounds a little needy, but for diagnostics sake, have you asked the sourcery devs if they could make an odin flashable file for you? The other alternative is to open the zip on a computer, extract only the script file in the zip, delete the asset check that keeps failing, then re-zip the script. Move that modified zip back to your phone and try flashing it then.

  5. Since I have the same problem with JBSourcery, XenonHD and JellyBelly the problem is obviously at my end.

  6. jhawkkw

    Since you do have it rooted, have your taken a look to see what the build.prop actually says? Maybe the previous user modified it?

  7. Rxpert83

    Sounds like the build prop has the wrong model.

    Double check you’re installing ROMs made for your device

  8. teddyearp

  9. Sorry, but you’re over my head. I don’t know if my phone is new or refurbished.

  10. teddyearp

    The «build.prop» is a file in /system. If your phone is rooted, use a root file explorer and navigate to /system. Copy, do not move nor delete the build.prop file to your sdcard. Then plug your phone into your pc and copy or move the copy from from your sdcard to your pc. Find, download, and install the free software notepad++. Using notepad++ open the build.prop file on your pc and report back to us what the first say five to seven lines say.

    good luck

  11. There are also apps in the Market that will display the various property values.

    My Android Root Toolkit’s first option, «Display Root and Mount Status» will display that information in the first line of output (Device info)…I don’t remember what field is what, so I’ll reply back in a bit after I search this.

    Also, you should be able to do an adb shell getprop ro.product.device from your PC (connected to your phone) or just getprop ro.product.device from the Android Terminal Emulator app to see that particular value.

  12. jhawkkw

    I keep forgetting about that terminal emulator app. I haven’t used it in so long, since I always do my commands through an adb shell. Good call scary.
    I think I read in another forum that Ron was able to flash sourcery 4.2 through the use of the Rom Manager app. So it might be a moot point in the end.

  13. Thanks for all the suggestions everyone. I was finally able to successfully flash using ROM Manager. I was getting the shakes being on the stock ROM. :D

  14. That’s true. I don’t like problems that just «disappear» and I would like to know what the actual issue was and how to deal with it.

  15. teddyearp

    I doubt using Rom Manager had anything to do with it. I think something _might_ have gone wrong with the download of the other roms Ron tried.

    Happy sailing Ron!

  16. Nice thought Teddy, but Rom Manager used the same zip file I’d been trying to flash with TWRP.

  • galaxy nexus

Share This Page

When I try to install any of the roms of that page: http://get.cm/?device=urushi I always get this error:

Finding update package… Opening update package… Installing
update… assert failed: getprop(«ro.product.device») == «ST18i»||
getprop(«ro.build.product») == «ST18i»|| getprop(«ro.product.device»)
== «ST18a»|| getprop(«ro.build.product») == «ST18a»|| getprop(«ro.product.device») == «urushi» ||
getprop(«ro.build.product») == «urushi» E:Error in
/sdcard/cm-9.1.0-urushi.zip
(Status 7) Installation aborted.

This sounds to me, that the prop doesen’t get the right string «ST18i» which is strange, cause that’s exactly my model.

Do I have to downgrade or install something else first?

I also tried to install the old image Xperia Ray (ST18i)_4.0.2.A.0.42_CE.zip again, but there is just sais «installation aborted».

Are there different Rescue Menues? I read, someone tried reinstalled his rescue menu with Odin.

I installed my Recovery Mod with the app x-Parts from Google Play that app installs the CWM.

When I try to install any of the roms of that page: http://get.cm/?device=urushi I always get this error:

Finding update package… Opening update package… Installing
update… assert failed: getprop(«ro.product.device») == «ST18i»||
getprop(«ro.build.product») == «ST18i»|| getprop(«ro.product.device»)
== «ST18a»|| getprop(«ro.build.product») == «ST18a»|| getprop(«ro.product.device») == «urushi» ||
getprop(«ro.build.product») == «urushi» E:Error in
/sdcard/cm-9.1.0-urushi.zip
(Status 7) Installation aborted.

This sounds to me, that the prop doesen’t get the right string «ST18i» which is strange, cause that’s exactly my model.

Do I have to downgrade or install something else first?

I also tried to install the old image Xperia Ray (ST18i)_4.0.2.A.0.42_CE.zip again, but there is just sais «installation aborted».

Are there different Rescue Menues? I read, someone tried reinstalled his rescue menu with Odin.

I installed my Recovery Mod with the app x-Parts from Google Play that app installs the CWM.

Понравилась статья? Поделить с друзьями:
  • Assert efi error status invalid parameter
  • Assembly referencing error people playground
  • Assembly csharp dll как изменить
  • Assembler syntax error
  • Assembler error a2206