today i unlocked bootloader and rooted my moto g 2015 phone, i want to remove Bootloader Warning, i tried some online tutorials and downloaded "unlocked_logo.zip" but they are giving Signature Verification Fail error, can anyone give me a good solution...
http://forum.xda-developers.com/2015-moto-g/themes-apps/remove-unlocke-bootloader-message-t3177801
squid2 said:
http://forum.xda-developers.com/2015-moto-g/themes-apps/remove-unlocke-bootloader-message-t3177801
Click to expand...
Click to collapse
i tried it, but giving footer is wrong, signature verification fail, installation aborted error.......
What are you flashing it with? Worked fine for me with TWRP.
squid2 said:
What are you flashing it with? Worked fine for me with TWRP.
Click to expand...
Click to collapse
i tried to install it in recovery mode it didn't works, now i installed it through TWRP
Related
I am trying to install the KK update for Tesco retail bought handsets and for some reason when I try to flash through CWM it says "this package is for falcon_umts devices : this is a xt1034
Yet it is a device I bought directly from tesco....I am at a loss on this one?
Can anyone help me reset the device back to default so it recognises as the correct XT1032?
I am stuck all I want is the KK update and me trying to root the device seems to have caused more problems.
Aye Up said:
I am trying to install the KK update for Tesco retail bought handsets and for some reason when I try to flash through CWM it says "this package is for falcon_umts devices : this is a xt1034
Yet it is a device I bought directly from tesco....I am at a loss on this one?
Can anyone help me reset the device back to default so it recognises as the correct XT1032?
I am stuck all I want is the KK update and me trying to root the device seems to have caused more problems.
Click to expand...
Click to collapse
You could try a data factory reset or flash a stock rom to solve your problem.
This one is easy: your CWM's build.prop identifies itself as an XT1034. Change your CWM, or remove the relevant assert line in the updater-script.
Darkshado said:
This one is easy: your CWM's build.prop identifies itself as an XT1034. Change your CWM, or remove the relevant assert line in the updater-script.
Click to expand...
Click to collapse
Thanks a lot. I never thought about this. I changed the CWM I had with Philz for x1032 and could finally install my OTA updates.
request for help to update CWM
Hi m3adow,
I have moto g UK version which i got from Amazon. I have rooted and installed CWM and xpose Framework. The OTA update fails. I get the same error that you have mentioned in the post - "this package is for falcon_umts devices : this is a xt1034". Can you please let me know how to update the CWM
thanks
You can download PhilZ touch here.
You can flash his cwm using your existing cwm or extract it and flash the img file using fastboot.
Darkshado said:
This one is easy: your CWM's build.prop identifies itself as an XT1034. Change your CWM, or remove the relevant assert line in the updater-script.
Click to expand...
Click to collapse
Mind helping me with that?
I'me having the same issue. Already tried with Phill xt1032 recovery and no go...
Any help will be welcome
Help
m3adow said:
Thanks a lot. I never thought about this. I changed the CWM I had with Philz for x1032 and could finally install my OTA updates.
Click to expand...
Click to collapse
Could you tell me how did you do that please I'm having the same problem as you!!!
Aprecciate it !!!!:fingers-crossed:
Read post 6
Rhazi3l said:
Mind helping me with that?
I'me having the same issue. Already tried with Phill xt1032 recovery and no go...
Any help will be welcome
Click to expand...
Click to collapse
Maybe you need Phil's for Faclon? I have a retail GB Moto G and Phil's for falcon was the only one that worked. The XT1032 failed also.
mdentener said:
Maybe you need Phil's for Faclon? I have a retail GB Moto G and Phil's for falcon was the only one that worked. The XT1032 failed also.
Click to expand...
Click to collapse
Tried with falcon as well and it still doesn't work. This one was bought on amazon UK and when connecting onto the PC it shows as XT1032. I was already looking into the build.prop on the system and it shows XT1032 and falcon_umts. And the update_script on Phil's recovery lists them all in order to be able to install easily on every Moto G model. Not rly sure what else we can try to add / change on build.prop or on recovery to get it to be recognised correctly.
I will try the other recoveries to see if any works.
i solved this problem, by flashing this rom "RETAIL-DE_FALCON_KLB20.9-1.10-1.9.1_cid7_CFC_1FF_v8.xml". It works perfectly, and original recovery is also working fine. You should try out this one here:
https://app.box.com/s/kdey7xefe9kez1phorpi
I have a Moto G (XT1032) and it seems to be stuck somewhat in a bootloop. The reason I say this is because I can get into fastboot, go into recovery, and sometimes it will get to the "M" but nowhere past that. On a normal boot up, it will get to the "BOOTLOADER UNLOCKED" screen (yes I have unlocked bootloader and rooted), and that's it. I believe this happened because I was trying to flash Android 5.0.1 to the device because it wasn't available yet. Thanks in advance for any help, and if you need more information just ask. The last thing I want to do is have to send it in.
HopperPlaysMC said:
I have a Moto G (XT1032) and it seems to be stuck somewhat in a bootloop. The reason I say this is because I can get into fastboot, go into recovery, and sometimes it will get to the "M" but nowhere past that. On a normal boot up, it will get to the "BOOTLOADER UNLOCKED" screen (yes I have unlocked bootloader and rooted), and that's it. I believe this happened because I was trying to flash Android 5.0.1 to the device because it wasn't available yet. Thanks in advance for any help, and if you need more information just ask. The last thing I want to do is have to send it in.
Click to expand...
Click to collapse
What did it say when you tried installing 5.0? Have you tried clearing cache/dalvik?
dustcollector69 said:
What did it say when you tried installing 5.0? Have you tried clearing cache/dalvik?
Click to expand...
Click to collapse
I have tried installing cache/dalvik, and when installing 5.0, it would have an issue installing because of updater-script. On my phone (in recovery mode sideloading from adb) it would say "Installation aborted"
HopperPlaysMC said:
I have tried installing cache/dalvik, and when installing 5.0, it would have an issue installing because of updater-script. On my phone (in recovery mode sideloading from adb) it would say "Installation aborted"
Click to expand...
Click to collapse
Hmm, im not sure why it would say that.. Did you format system before flashing?If you don't mind losing data you could always reflash stock firmware through fastboot in the bootloader
dustcollector69 said:
Hmm, im not sure why it would say that.. Did you format system before flashing?If you don't mind losing data you could always reflash stock firmware through fastboot in the bootloader
Click to expand...
Click to collapse
I formatted before installing. I know it's problem with my phone because the Android 5 is for GPE and I have a falcon version Moto G. I know there is a way to bypass it though. I don't mind losing data either as I had to anyway to unlock the bootloader.
I'm also going to try sideloading 5.0 again after clearing dalvik/cache again.
HopperPlaysMC said:
I formatted before installing. I know it's problem with my phone because the Android 5 is for GPE and I have a falcon version Moto G. I know there is a way to bypass it though. I don't mind losing data either as I had to anyway to unlock the bootloader.
Click to expand...
Click to collapse
oh, if your device isnt converted to a GPE edition then that is probably why because it uses different filesystems. follow this guide to restore your firmware
http://forum.xda-developers.com/showthread.php?t=2542219
dustcollector69 said:
oh, if your device isnt converted to a GPE edition then that is probably why because it uses different filesystems. follow this guide to restore your firmware
http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
Will give it a try, but if not I will tell you what I see after trying to sideload to 5.
dustcollector69 said:
oh, if your device isnt converted to a GPE edition then that is probably why because it uses different filesystems. follow this guide to restore your firmware
http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
Got GPE 4.4.4 running, I shall now try 5.0.1
dustcollector69 said:
oh, if your device isnt converted to a GPE edition then that is probably why because it uses different filesystems. follow this guide to restore your firmware
http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
Ok, so at least my phone is working, but I can't sideload 5 onto my device. Here is what I see on the phone after the CMD reaches 100%:
Code:
Restarting adbd...
status 0
Finding update package...
Opening update package...
E: Can't open /tmp/update.zip
(bad)
Installation aborted.
If you can help me with this, I would be grateful.
HopperPlaysMC said:
Ok, so at least my phone is working, but I can't sideload 5 onto my device. Here is what I see on the phone after the CMD reaches 100%:
Code:
Restarting adbd...
status 0
Finding update package...
Opening update package...
E: Can't open /tmp/update.zip
(bad)
Installation aborted.
If you can help me with this, I would be grateful.
Click to expand...
Click to collapse
thats good you at least got your phone working, can you send me the link to the zip your trying to install? are you sure its not corrupted?
probably its corrupted, try download the ota from settings menu and tell us
esd316 said:
probably its corrupted, try download the ota from settings menu and tell us
Click to expand...
Click to collapse
OTA isn't showing up, but it may be corrupted
dustcollector69 said:
thats good you at least got your phone working, can you send me the link to the zip your trying to install? are you sure its not corrupted?
Click to expand...
Click to collapse
Here's the link: goo.gl/zDJG9q (That'll directly download it)
HopperPlaysMC said:
Here's the link: goo.gl/zDJG9q (That'll directly download it)
Click to expand...
Click to collapse
im downloading now, will check it out in a bit
why dont you flash one of these zips instead and through a custom recovery though?
http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
dustcollector69 said:
im downloading now, will check it out in a bit
why dont you flash one of these zips instead and through a custom recovery though?
http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
Click to expand...
Click to collapse
I have clockwork recovery, I will attempt to flash one of those later.
All of the ROMs for my phone on http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510 are Brazilian.
Yep flash a stock rom for xt1032 (try a optimized) and that should work
esd316 said:
Yep flash a stock rom for xt1032 (try a optimized) and that should work
Click to expand...
Click to collapse
Can you link me one? Or do i just do a Brazilian one?
Tried installing the Brazilian one and... my phone is messed up again and I have no idea how I fixed it. Help again?
The latest update, it seems, can be rooted using the recowvery method. Dirtycow was patched by Google in a Dec. 5 security patch, but it seems LG didn't include that in their latest security update, which was created Dec 1! In any case, my phone is rooted with TWRP, and working just fine. So, for now we can still root with the update! I'd also like to point out, that this means we now have an official KDZ released version of rootable stock to roll-back to with LGUP!
Glad I forced ya to do it huh
How? I've tried multiple times and it would go through but upon booting into recovery i would get a 'no command' error
ahq1216 said:
How? I've tried multiple times and it would go through but upon booting into recovery i would get a 'no command' error
Click to expand...
Click to collapse
What method are you trying?
Follow instructions on this thread https://forum.xda-developers.com/v2...owvery-unlock-v20-root-shell-t3490594/page118
It works as kibmikey stated.
Norcal232001 said:
What method are you trying?
Follow instructions on this thread https://forum.xda-developers.com/v2...owvery-unlock-v20-root-shell-t3490594/page118
It works as kibmikey stated.
Click to expand...
Click to collapse
Ive been using easyrecowvery but ive tried that also. Maybe I messed up somewhere during the command line process thingy. Ill give it another go. Thanks
curious, if I'm currently rooted on H91810d, how can I get to a rooted H91810i? would like to make the move without getting my /data encrypted once root is lost...
dimm0k said:
curious, if I'm currently rooted on H91810d, how can I get to a rooted H91810i? would like to make the move without getting my /data encrypted once root is lost...
Click to expand...
Click to collapse
I was on 10i last week after i got phone back from service. I flashed NotSoStock Rom which said i was on the 10d base. Then flashed Overdrive Rom which put me back to 10i. I didnt have any problems switching basebands within custom roms if that helps.
ahq1216 said:
How? I've tried multiple times and it would go through but upon booting into recovery i would get a 'no command' error
Click to expand...
Click to collapse
I have same error even I tried to enter recovery using "adb reboot recovery"
---- edit ----
Done.
You must do it manually according to the instructions
https://github.com/jcadduono/android_external_dirtycow#running
https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
Note: make sure you rename your TWRP to twrp.img, and put SuperSU file into memory card (your TWRP cannot open internal storage).
how do you unroot and go to full stock
dudeawsome said:
how do you unroot and go to full stock
Click to expand...
Click to collapse
Since I have required 10i kdz and dll, I just flash it with LGUP as upgrade.
mingkee said:
Since I have required 10i kdz and dll, I just flash it with LGUP as upgrade.
Click to expand...
Click to collapse
Wil it remove twrp also and have you tested it
dudeawsome said:
Wil it remove twrp also and have you tested it
Click to expand...
Click to collapse
100% bone stock
Wasn't stable enoung so I had to delet it.
sorry:/
Just note that Magisk doesn't work and so on...
vidra said:
Just note that Magisk doesn't work and so on...
Click to expand...
Click to collapse
I didn't see your post before you changed it, but my phone is unlocked and I had no trouble with either updating to Pie or installing and using Magisk for SU etc.
johnjingle said:
I didn't see your post before you changed it, but my phone is unlocked and I had no trouble with either updating to Pie or installing and using Magisk for SU etc.
Click to expand...
Click to collapse
Can you decrypt it in TWRP?
vidra said:
Can you decrypt it in TWRP?
Click to expand...
Click to collapse
Didn't even try went back to stock 8.1, without rebooting I adb pushed the Pie update and then installed that and rebooted. Then I rebooted to Fastboot and booted into the TWRP and installed Magisk, cleared cache/dalvik, rebooted and everything worked fine.
Did not try to decrypt it.
johnjingle said:
Didn't even try went back to stock 8.1, without rebooting I adb pushed the Pie update and then installed that and rebooted. Then I rebooted to Fastboot and booted into the TWRP and installed Magisk, cleared cache/dalvik, rebooted and everything worked fine.
Did not try to decrypt it.
Click to expand...
Click to collapse
Is it buggy? and which region device you're using?
anas214812 said:
Is it buggy? and which region device you're using?
Click to expand...
Click to collapse
I have had no problems/bugs and I am in the United States on Project Fi with a 1900-1 variant.
johnjingle said:
I have had no problems/bugs and I am in the United States on Project Fi with a 1900-1 variant.
Click to expand...
Click to collapse
Do you get a black line on your blue Moto logo saying DM-Verify is disabled?
vidra said:
Do you get a black line on your blue Moto logo saying DM-Verify is disabled?
Click to expand...
Click to collapse
Yes, verity is disabled, but that is because the bootloader is unlocked. There is nothing you can do about that to my knowledge except to hide the notification.
vidra said:
Do you get a black line on your blue Moto logo saying DM-Verify is disabled?
Click to expand...
Click to collapse
I believe it is because there is no official signed recovery released for moto X4 yet. Since we unlock the bootloader we are unable to relock without official recovery and remove the warning.
Trying to install Lineage (just for fun, as a tester) on an older Samsung phone (Galaxy S3 i9300) but keep getting "Signature Verification Failed". I've tried a few different downloads of the OS zip, confirmed the firmware etc but can't get past this.
Seen posts to "Uncheck TWRP verification" to disable it but can't for the life of me find out how to do that ?
Any help will be appreciated.
Try ADB Sideload method to install LOS.
jwoegerbauer said:
Try ADB Sideload method to install LOS.
Click to expand...
Click to collapse
Tried that and still no luck - maybe the phone is too old ....... I don't know
You Need a custom recovery because your stock one is looking for a signed zip file and that zip is most likely not signed
Woodnome said:
Tried that and still no luck - maybe the phone is too old ....... I don't know
Click to expand...
Click to collapse
Sorry I skimmed read Go into the advanced tab and in one of the tabs it'll sat verify zip files uncheck that and you should be good to go