Need help!!! - Moto G Q&A, Help & Troubleshooting

Hi everyone, I have the boost Mobile moto g running stock 4.4.4. I'm rooted and have twrp on my phone I'm trying to install bliss pop 5.1.1 but keeps giving me a error. Can anyone help me please?

read FAQ and xda rules before posting.

dustiNcyde419 said:
Hi everyone, I have the boost Mobile moto g running stock 4.4.4. I'm rooted and have twrp on my phone I'm trying to install bliss pop 5.1.1 but keeps giving me a error. Can anyone help me please?
Click to expand...
Click to collapse
Remove the assert lines in the updater-script.
Sent from my Moto G using Tapatalk

I'm sorry idk how to do that? I'm new to all this.

dustiNcyde419 said:
I'm sorry idk how to do that? I'm new to all this.
Click to expand...
Click to collapse
1. Open the ROM zip with WinRAR (or similar program).
2, Navigate to the updater-script.
Code:
[I]META-INF [B]>[/B] com [B]>[/B] google [B]>[/B] android [B]>[/B] updater-script[/I]
3. Open updater-script with Notepad++ (or similar program).
4. Remove (delete) all lines that begin with "assert".
Code:
[I][B]assert[/B](getprop("ro.product.device") == "xt1031" || getprop("ro.build.product") == "xt1031" || getprop("ro.product.device") == "xt1032"...[/I]
5. Save, and flash ROM.

ATTACK said:
1. Open the ROM zip with WinRAR (or similar program).
2, Navigate to the updater-script.
Code:
[I]META-INF [B]>[/B] com [B]>[/B] google [B]>[/B] android [B]>[/B] updater-script[/I]
3. Open updater-script with Notepad++ (or similar program).
4. Remove (delete) all lines that begin with "assert".
Code:
[I][B]assert[/B](getprop("ro.product.device") == "xt1031" || getprop("ro.build.product") == "xt1031" || getprop("ro.product.device") == "xt1032"...[/I]
5. Save, and flash ROM.
Click to expand...
Click to collapse
do i need to be on the lollipop bootloader or no?

dustiNcyde419 said:
do i need to be on the lollipop bootloader or no?
Click to expand...
Click to collapse
No. That's why your going to remove the assert lines.
Sent from my XT1031

ATTACK said:
No. That's why your going to remove the assert lines.
Sent from my XT1031
Click to expand...
Click to collapse
I tried it on multiple ROMs and it won't work just get a failed message when I try and install the rom

dustiNcyde419 said:
I tried it on multiple ROMs and it won't work just get a failed message when I try and install the rom
Click to expand...
Click to collapse
Could you please, screenshot or type exactly what it the error states.
Sent from my XT1031

you have to update the bootloader or change some codes in the Rom,else you cant flash lolipop

there is no error message it acts like its going to flash then just says faild

Related

[Q] Galaxy Ace Wont Root, any ideas?

Tried Searching using string - assert failed: getprop("ro.product.device") == "GT-S5830" with no luck so time to create post.
What i have done already.
I have downloaded and installed kies updated firmware to Gingerbread 2.3.6.
I have put ClockWorkMod 4.0.0.9 (forum.xda-developers.com/showthread.php?t=1168417)
Now i try to root fone via recovery following steps E on Hubix Thread (forum.xda-developers.com/showthread.php?p=12874680), downloaded upd_1.zip put on root of SD card searched for it using the "install zip from SD card" option within CWM, when i press to install i get an error
Opening Update Package...
Installing Update...
assert failed: getprop("ro.product.device") == "GT-S5830" || getprop("ro.build.product") == "GT-S5830" || getprop("ro.product.device") == "GT-S5570" || getprop("ro.build.product") == "GT-S5570" || getprop("ro.product.device") == "GT-S5670" || getprop("ro.product.product") == "GT-S5670" || getprop("ro.product.device") == "GT-B7510" || getprop("ro.product.product") == "GT-B7510"
E:Error in /sdcard/upd_1.zip
(status 7)
Installation aborted.
Click to expand...
Click to collapse
My phone details are
Model Number: GT-S5830
Android Version: 2.3.6
Baseband Version: S5830NEKT2
Kernel Version: 2.6.35.7-perf-CL772922 [email protected] #1
Build Number: GINGERBREAD.XWKT5
Click to expand...
Click to collapse
Hope thats enough information, any ideas how to solve the problem?
Thankyou in advance
maybe its a corrupt file or something? I'd download that file again and try again if you haven't already. I know sometimes you have to try installing superuser around 3 times for some phones using CWM so maybe you have to do that also?
PakAttack1994 said:
maybe its a corrupt file or something? I'd download that file again and try again if you haven't already. I know sometimes you have to try installing superuser around 3 times for some phones using CWM so maybe you have to do that also?
Click to expand...
Click to collapse
Tried a few times now even, downloaded gganon's root.zip file (forum.xda-developers.com/showthread.php?t=1282011) with no luck. Ill charge up the laptop and try from there just in case my PC is screwing something up.
Ok so im on laptop now tried downloading the various .zip files and tried installing 5 times per zip and still get the problem that is shown in my first post, any other ideas ?
It mentions that if Step E doesn;t work, try step D. If that doesnt work, try the link below and install "AceGingerRoot.zip" instead of “upd_1.zip”, as described in the link...let me know what happens.
http://acetips.wordpress.com/2011/09/29/root-ace-froyo-gingerbread/
or if that doesnt work, try this....
http://forum.xda-developers.com/showthread.php?t=1282011
PakAttack1994 said:
It mentions that if Step E doesn;t work, try step D. If that doesnt work, try the link below and install "AceGingerRoot.zip" instead of “upd_1.zip”, as described in the link...let me know what happens.
http://acetips.wordpress.com/2011/09/29/root-ace-froyo-gingerbread/
or if that doesnt work, try this....
http://forum.xda-developers.com/showthread.php?t=1282011
Click to expand...
Click to collapse
AceGingerRoot.zip worked perfectly thanks for all your help
------------------------------------------------------------------------------
Edit: Now get same problem when trying to install custom ROM forum.xda-developers.com/showthread.php?t=1360889 any ideas ?
Edit2: Nevermind updated CWM to 5.0.2.6 and install went fine
awesome, glad it worked.
Please reup AceGingerRoot.zip. The one I have found can't root my ace. And all of them are 980kb. But AceGingerRoot.zip that has been posted here is about 1000kb
AceGingerRoot.zip
PakAttack1994 said:
It mentions that if Step E doesn;t work, try step D. If that doesnt work, try the link below and install "AceGingerRoot.zip" instead of “upd_1.zip”, as described in the link...let me know what happens.
Click to expand...
Click to collapse
This file was the key for me- rooting a Galaxy Ace GT-S5830 on 3.2.6- and that after a day or so searching, running, re-running other stuff and wondering WtF was going wr(on)g. I hope an extra endorsement here helps some other android newbie.
The links seem a moving target, but a Google search on the file name eventually found me one that worked.
What a hassle. I've never been accused of being the swiftest pencil in the box, but if anyone's got a quicker way, please post. And thank you, thank you, thank you...
Managed to lose root today. Updated SuperSU and chose to update binary via CWM instead of normal. Didn't work and I've posted about that on its relevant thread here.
As I said in my post there I tried reflashing the update.zip, but got a status 7 error, to which I then tried AceGingerRoot.zip which was apparently successful in changing the binary from v1.27:SUPERSU (0) binary back to the old v2.3.1-ef (0) binary.
The problem is that I've still not got any root access. So the su files are all in the xbin folder, but apparently aren't readable.
TIA for your help/advice.

[Q] Error status 7 while installing CM

Hey everyone,
I just rooted my SE Live with Walkman and wanted to install CM for my device, but there is an error like:
"asser failed: getprop("ro.product.device")== "wt19a" || get.prop("ro.build.product")=="wt19a" || get.prop("ro.product.board")=="wt19a" || getprop("ro.product.device")== "wt19i" || get.prop("ro.build.product")=="wt19i" || get.prop("ro.product.board")=="wt19i" || getprop("ro.product.device")== "coconut" || get.prop("ro.build.product")=="coconut" || get.prop("ro.product.board")=="coconut" || E: Error in /sdcard/update-cm-7.2.0-RC1-coconut-signed.zip error (status 7) ...
What does it mean? What's wrong? What should I do to fix this error?
BTW!!! I have already tried changing properties with Build.prop Editor...
Are you really sure that is a rom for your phone.. ?
TO Resolve :
Unzip the rom
Go TO meta-inf/google/android and open with block note updater-script and delete the string for the assert
Save and rizip everything
And now install
If you have problem tell TO me
Excuse me tor the bad english i m italian
CoolJoseph96 said:
Are you really sure that is a rom for your phone.. ?
TO Resolve :
Unzip the rom
Go TO meta-inf/google/android and open with block note updater-script and delete the string for the assert
Save and rizip everything
And now install
If you have problem tell TO me
Excuse me tor the bad english i m italian
Click to expand...
Click to collapse
Are you sure this is the way to fix this error? Because in my opinion it will just don't show that there's an error, but the installation won't continue.
Edit: I just did what you said and it said that installation is completed, I pressed reboot system now and now it seems that my phone is stuck on booting with "Sony Ericsson" on screen. I haven't unlocked my bootloader, maybe that's the reason???
The rom is not for your device if stuck on logo
You must unlock the bootloader because hybrom do not have a boot image http://www.androidust.com/unlock-bootloader-of-sony-ericsson-android-phones/

[TUTORIAL]CWM Errors and solutions. Post all your CWM recovery related error here.

Hello everyone,
I saw a lot of people facing errors in CWM recovery while installing ROMs, themes, etc. So I decided to make a simple, short and clean thread to post some solutions which might help you in overcoming the errors.
Status 0 Error:
This error occurs due to some error in updater-binary. Replace the updater-binary from some other same type of zip you are flashing and it will work.
Click to expand...
Click to collapse
Status 1 Error:
Well this is one of the most rarest error that a person can get...but with my experience I came to know that this occurs because you dont have correct permissions set. Use correct perms in updater-script and done
Click to expand...
Click to collapse
Status 6 Error:
The status 6 error mostly occurs when we edit an updater-script in windows text editor. This is because the windows text editor at the end of the updater-script creates a windows styled end of line which causes the error. The easiest solution is to write the updater-script in such a way that this error doesn't occurs. Try notepad++, change the end of line to unix style, unix style eol and this error won't occur
Click to expand...
Click to collapse
Status 7 Error:
The most common error that most of the people face is this one.
Following are the reasons for it:
1. Something wrong in updater-script.
2. Corrupt zip.
3. Zip not made for device or couldn't recognize the device.
To overcome the first error, the only solution is to manually edit the updater-script and search for error or post your updater-script to some forum or thread or make new thread specifying your complete error.
To overcome the second error, the only solution is to re-download the whole zip.
To overcome the third error, just delete the first three lines from your updater-script stating something related to your device. Here's the lines related to my device, i.e., Sony Ericsson Xperia Mini Pro, SK17i/a :
Code:
assert(getprop("ro.product.device") == "SK17i" || getprop("ro.build.product") == "SK17i" ||
getprop("ro.product.device") == "SK17a" || getprop("ro.build.product") == "SK17a" ||
getprop("ro.product.device") == "mango" || getprop("ro.build.product") == "mango");
Similar kind would be for your device too. And if not then the zip is simply not meant for your device.
Click to expand...
Click to collapse
Great thread,
Btw in status 6, we have to select eol as unix in npp, not just use it right
Added about status 1 error also
Cheers,
AJ
When there's 0,1 and then 6 and 7. Logic tells that there is 2-5, anybody ever heard of it?
Regards
N
Im etting a error called Cannot copy Meta-inf/google/android/update-binary. I tried replacing the binary file then the zip cannot be installed as it says zip file is bad. How do i solve this??
Please help..
I am trying to port android 4.3 to sony lww.
DarthRecca said:
Im etting a error called Cannot copy Meta-inf/google/android/update-binary. I tried replacing the binary file then the zip cannot be installed as it says zip file is bad. How do i solve this??
Please help..
I am trying to port android 4.3 to sony lww.
Click to expand...
Click to collapse
Make sure you zipped all the folders with meta-inf and not zipped the parent fodder
Cheers,
AJ
To whom got status 1 error
I had this problem(cwm status 1 error) while flashing my xxxxxx.zip ,so i got a twrp ,in its advanced options ,got to the file manager ,head to the / directory (all of the thing where there) ,tapped on select button,and chmod 755. Then with cwm i could flash my zip.
don't mount my ext sd card
I'm install cwm recovery in galaxy s dous 2 s7582 but cwm cannot mount my SD card for selecting any update from storage.................

[Q] Error 7 when trying to install second Rom (TWRP)

Hello!
I am in the process of installing dual boot on my Optimus 3D. I have successfully format my external SD card. However when i try to install a CM10 ROM in TWRP it get an error right in the begining of the process. It says it is "error 7". After that the flashing stops.
Do anyone have a solution for this?
Sincerely Henrik
HenrikSwe said:
Hello!
I am in the process of installing dual boot on my Optimus 3D. I have successfully format my external SD card. However when i try to install a CM10 ROM in TWRP it get an error right in the begining of the process. It says it is "error 7". After that the flashing stops.
Do anyone have a solution for this?
Sincerely Henrik
Click to expand...
Click to collapse
edit the updater-script
ON META-INF/com/google/android/updater-script
with Notepad++
and remove this line
assert(getprop("ro.product.device") == "p920" || getprop("ro.build.product") == "p920");
:good:
zak53 said:
edit the updater-script
ON META-INF/com/google/android/updater-script
with Notepad++
and remove this line
assert(getprop("ro.product.device") == "p920" || getprop("ro.build.product") == "p920");
:good:
Click to expand...
Click to collapse
Thank you!
That took care of the problem.

XT925 Problem to upgrade to CM12.1

Hi guys,
Can you help me please?, I having problems to upgrade my xt925 to CM12.1. The error log says that I have a xt926 and the update process abort.
Please see the attached image. Thanks in advance for your support.
xt925 to cm12.1
rodrigo_ruiz_rr said:
Hi guys,
Can you help me please?, I having problems to upgrade my xt925 to CM12.1. The error log says that I have a xt926 and the update process abort.
Please see the attached image. Thanks in advance for your support.
Click to expand...
Click to collapse
I had a similar problem, but in my case the log said that my device was not a xt925 because i had cm11 for msm8960, the solution was to delete this line:
Code:
[I][B]assert(getprop("ro.product.device") == "xt925" || getprop("ro.build.product") == "xt925" || getprop("ro.product.device") == "vanquish_u" || getprop("ro.build.product") == "vanquish_u" || abort("This package is for device: xt925,vanquish_u; this device is " + getprop("ro.product.device") + "."););
ifelse(is_mounted("/system"), unmount("/system"));
assert(getprop("ro.boot.secure_hardware") == "1" || abort("This package is for devices with 4.4 bootloader"););[/B][/I]
in the updater-script file inside the folder cm-12.1-20150810-NIGHTLY-xt925.zip\META-INF\com\google\android of your zip file, so it won't try to verify your device name and instead will install it as it is
REMEMBER USE THIS UNDER YOUR OWN RISK, DON'T BLAME ME FOR A NICE PAPER WEIGHT
I ALREADY HAD A KITKAT BOOTLOADER FROM A STOCK FIRMWARE and i tried this on a old device, so no harm if bricked, also i was sure that i downloaded the correct cm12.1 version for my mobile and, at last but not least, i knew how to unbrick it in case something went wrong

Categories

Resources