Apologies if this has been asked before but I can't seem to find the answer. I've read this post but it seems more complicated than it needs to be...
I've got an unlocked, rooted xt925.
I'm on CM11 JBBL nightlies (with CWM Recovery) and I want to move to CM12, which I believe means I need to revert from JBBL to KKBL first.
Is that correct?
If so, can I just download the KKBL firmware and flash it? Or do I have to use some other process? I'm on a Mac so I can't use PC-based tools (although I can use adb etc).
And where can I download KBBL from?? And will I lose root?
Thanks...
SamuriHL is the man. He has an updated HoM 4.1 that makes it somewhat easier, but it still involves flashing the FXZ, setting up custom recovery, re-rooting, etc... He has MAC "notes" in the thread, Im not sure if I can link the other forum its on, but f you google house of mot 4.1, it is (or was in my case) the first result
I was on the JBBL and 5.0.2 Validus ROM, but upgraded my BL to KK yesterday and Im running CM 12. So far I am loving it.
updated bootloader
jlang11 said:
SamuriHL is the man. He has an updated HoM 4.1 that makes it somewhat easier, but it still involves flashing the FXZ, setting up custom recovery, re-rooting, etc... He has MAC "notes" in the thread, Im not sure if I can link the other forum its on, but f you google house of mot 4.1, it is (or was in my case) the first result
I was on the JBBL and 5.0.2 Validus ROM, but upgraded my BL to KK yesterday and Im running CM 12. So far I am loving it.
Click to expand...
Click to collapse
Could you please tell me, what KK bootloader you are using now? I'm still not able to get CM 12. "...needs bootloader 4.4..."
xMandy said:
Could you please tell me, what KK bootloader you are using now? I'm still not able to get CM 12. "...needs bootloader 4.4..."
Click to expand...
Click to collapse
What I suggest as it worked for me, find SamuriHL's House of Moto 4.1, follow the directions to a T, as he says read, read, and read again, and use the firmware (FXZ) XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml. The bootloader kernel is 3.4 that was upgraded on our phones with that version of the firmware. Do a google search for House of Moto 4.1 and it should be easy to find.
XT925 or XT926
jlang11 said:
What I suggest as it worked for me, find SamuriHL's House of Moto 4.1, follow the directions to a T, as he says read, read, and read again, and use the firmware (FXZ) XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml. The bootloader kernel is 3.4 that was upgraded on our phones with that version of the firmware. Do a google search for House of Moto 4.1 and it should be easy to find.
Click to expand...
Click to collapse
thanks so far!
But why are you using a XT926-FXZ and not some for the XT925?
Any hint how to find out which one is the one I should use? ADB says "vanquish_u"... :silly:
...still trying...
xMandy said:
thanks so far!
But why are you using a XT926-FXZ and not some for the XT925?
Any hint how to find out which one is the one I should use? ADB says "vanquish_u"... :silly:
...still trying...
Click to expand...
Click to collapse
Because I have the xt926
If you have xt925, then make sure you use the correct firmware for your phone...
Hey guys, i'm trying the same, and i don't get it working.
Phone is an unlocked xt925.
Could upgradeto KKBL but now nothing works to get cm12 working, always get bootloops...
virgin xt925
jlang11 said:
Because I have the xt926
If you have xt925, then make sure you use the correct firmware for your phone...
Click to expand...
Click to collapse
as far as I see, the House of Moto does the same as RSD lite - it brings the RAZR back to "a minty factory fresh state" - means 4.1.2. with JBBL.
After that you did the OTA update to 4.4.2.? Is this the trick to get KKBL? Trying to use twrp didn't work for me (still on 4.1.2), the screen was frozen, no touch, no reaction. . .
Didn't get to 4.4.2 so far or was not able to flash a recovery that supports CM 12. :crying:
It would be great if you will share your secret :fingers-crossed:
thx
xMandy said:
as far as I see, the House of Moto does the same as RSD lite - it brings the RAZR back to "a minty factory fresh state" - means 4.1.2. with JBBL.
After that you did the OTA update to 4.4.2.? Is this the trick to get KKBL? Trying to use twrp didn't work for me (still on 4.1.2), the screen was frozen, no touch, no reaction. . .
Didn't get to 4.4.2 so far or was not able to flash a recovery that supports CM 12. :crying:
It would be great if you will share your secret :fingers-crossed:
thx
Click to expand...
Click to collapse
As far as HoM being the same as RSD lite, it mat very well be similar. If you are familiar with RSD by all means use that utility. SamuriHL wrote the scripts for flashing FXZ's and worked hard at making it easy for "n00bs" like myself to upgrade their phones.
As far as flashing back to "minty factory fresh" state, if you are flashing the correct FXZ, you are not flashing 4.1.2, you would be flashing 4.4.2 (see previous post mentioning XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml) so no you are not OTA to 4.4.2. The 4.4.2 FXZ HAS the KKBL.
All this is assuming you are already UNLOCKED.
I am in NO WAY an expert, and actually I am a n00b myself. Just trying to point you in the right direction. Go back and read the post, then read it again (as SamuriHL states in his post).
xMandy said:
as far as I see, the House of Moto does the same as RSD lite - it brings the RAZR back to "a minty factory fresh state" - means 4.1.2. with JBBL.
After that you did the OTA update to 4.4.2.? Is this the trick to get KKBL? Trying to use twrp didn't work for me (still on 4.1.2), the screen was frozen, no touch, no reaction. . .
Didn't get to 4.4.2 so far or was not able to flash a recovery that supports CM 12. :crying:
It would be great if you will share your secret :fingers-crossed:
thx
Click to expand...
Click to collapse
xMandy said:
thanks so far!
But why are you using a XT926-FXZ and not some for the XT925?
Any hint how to find out which one is the one I should use? ADB says "vanquish_u"... :silly:
...still trying...
Click to expand...
Click to collapse
OK, so here is a little explanation, followed by a link on how to upgrade xt925 or 926 to 4.4.2
So HoM and RSD-Flasher are almost the same as RSD-Lite, they have a little more functions and so on. Everything you might wanna do with RSD-Lite u can do with these two tools.
XMandy: You can find out your version this way: settings -> about phone -> system version. At least on my phone it states xt925
Here is how i upgraded my xt925 to stock 4.4.2 i would recommend to be BL unlocked, but it seems like there are ways to unlock and root 4.4, so that is not that important.
Guide
With everything else from that point on i also got my problems, thats why i'm here in the first place but probably after upgrading you guys can help me too
so far - so bad
esok44 said:
OK, so here is a little explanation, followed by a link on how to upgrade xt925 or 926 to 4.4.2
So HoM and RSD-Flasher are almost the same as RSD-Lite, they have a little more functions and so on. Everything you might wanna do with RSD-Lite u can do with these two tools.
XMandy: You can find out your version this way: settings -> about phone -> system version. At least on my phone it states xt925
Here is how i upgraded my xt925 to stock 4.4.2 i would recommend to be BL unlocked, but it seems like there are ways to unlock and root 4.4, so that is not that important.
Guide
With everything else from that point on i also got my problems, thats why i'm here in the first place but probably after upgrading you guys can help me too
Click to expand...
Click to collapse
I did this several times now. . .
XT 925, VANQUISH_U, unlocked BL:
# Clean install of 4.1.2. with RSD lite and zip-file 9.8.2Q-8-XT925_VQU-22_USERSIGNED_S7_UCAVANQU02NA02F.0R_LSAVNQJBRTFR_P007_A004_CFC.xml
=> works, with result JB 4.1.2
# OTA update
=> restart folowed by bootloader with message:
Device is LOCKED, Status Code: 0
downgraded security version
update gpt_main version vailed
Failed to hab check for gpt_backup: 0x35
failed to load GPT
CID Read Failure
Invalid CID status 0x69
No SP partition found
Fastboot Reason: Invalid GPT
# fastboot flash partition gpt.bin
# fastboot flash tz tz.mbn
# fastboot reboot-bootloader
=> works, with result Device is UNLOCKED, Status Code: 3
# fastboot reboot
=> works, with result KK 4.4.2, version 180.46.117.XT925.CEE-Retail.en.EU
# second OTA update
=> works, with result KK 4.4.2, version 180.46.127.XT925.CEE-Retail.en.EU, build number KDA20.127
==> so far everything is fine
# flashing recovery TWRP-2.8.4.1-xt925.img
=> works, with result recovery boot TWRP is posible and "install from zip" too
# wipe to factory reset
# wipe cache / repair cache
# install zip cm-12-20150217-NIGHTLY-xt925.zip
# install zip gapps-lp-20141220-signed.zip
# reboot to system
==> rebooting and bl warning
==> starting the ignition and looooooop
==> shows the CM 12 logo, is "active" and does this for hours if I won't stop it
So, where's my fault?
Heyho,
The mistake is not on your side. Its what i have stated before:
To not get the bootloop after installing cm12 u must Flash it over cm11. Currently i was not able to find a cm11 Version for kkbl which i could install on the xt925. I Asked i several Threads, regarding this topic and Noone helped/could help me so far
Sorry i thought your mistake was some where else
Sent from my RAZR HD using XDA Free mobile app
getting closer
esok44 said:
Heyho,
The mistake is not on your side. Its what i have stated before:
To not get the bootloop after installing cm12 u must Flash it over cm11. Currently i was not able to find a cm11 Version for kkbl which i could install on the xt925. I Asked i several Threads, regarding this topic and Noone helped/could help me so far
Sorry i thought your mistake was some where else
Sent from my RAZR HD using XDA Free mobile app
Click to expand...
Click to collapse
Sorry to ask again...
Where's the step i have to insert the flash of CM 11?
As far as i know with twrp.2.8.2.1 (KKBL) it's not posible to flash CM 11?
So. . . will this way do it?
# 4.4.2 stock
# flash recovery for jbbl (for example CW6.0.4.4)
# flash CM 11
# flash recovery for kkbl (twrp.2.8.2.1)
# flash CM 12
With some jbbl and CM 11 on the phone i was not able to use the CM 12 update - neither OTA nor recovery flash.
and again a big :good::good::good:
esok44 said:
Heyho,
The mistake is not on your side. Its what i have stated before:
To not get the bootloop after installing cm12 u must Flash it over cm11. Currently i was not able to find a cm11 Version for kkbl which i could install on the xt925. I Asked i several Threads, regarding this topic and Noone helped/could help me so far
Sorry i thought your mistake was some where else
Sent from my RAZR HD using XDA Free mobile app
Click to expand...
Click to collapse
No one posted a logcat of the boot failure yet, afaik.
I can clean flash a cm12 xt925 build just fine.
Unless the logs are provided, it won't get fixed (as long as it's not reproducible by the devs).
kabaldan said:
No one posted a logcat of the boot failure yet, afaik.
I can clean flash a cm12 xt925 build just fine.
Unless the logs are provided, it won't get fixed (as long as it's not reproducible by the devs).
Click to expand...
Click to collapse
I'm having the exact same problem, except on my XT926M.
I was on an unlocked XT926M running 4.1.2 stock Verizon. Yesterday I installed the FXZ 4.4.2 ROM with RSD Lite to upgrade the bootloader to KKBL. It works fine on 4.4.2 (183.46.15.XT926.Verizon.en.us)
Today I tried installing TWRP 2.8.4.2 and installing the latest CM12 nightly (Feb 17). I created a backup with TWRP, factory wiped , and flashed the CM12 image through TWRP. It succeeded flashing, but got stuck on the boot screen. After 20 minutes, I powered it off, tried turning it on again...stuck for another 10. Tried mounting the system partition in TWRP, doing an advanced wipe of system, data (NOT internal storage), and cache, but even that didn't work. Eventually after two hours of reflashing and draining my battery to 75% I decided to restore my TWRP 4.4.2 stock backup so I would have a phone to use again.
I can't post in the actual dev thread where people were talking about this. I would love to help troubleshoot this issue if they would direct me.
kabaldan said:
No one posted a logcat of the boot failure yet, afaik.
I can clean flash a cm12 xt925 build just fine.
Unless the logs are provided, it won't get fixed (as long as it's not reproducible by the devs).
Click to expand...
Click to collapse
Hey Kabaldan,
i wiill provide a logcat later today.
Will just give the most recent cm12 Version a shot.
A logcat will be posted
Thanks for your interest in helping us
I actually found a user on the droidrzr forums who has the same issue in a thread for the Dirty Unicorns Lollipop ROM.
You can see the logs he posted of the window here:
droidrzr.com/topic/56216-romofficialdirty-unicornsv91502moto-msm8960kk-bl21015/page-21#entry491765
This is only a few days old. There's a few others in the thread who were chiming in with the same problem. So far not much progress.
another try
kabaldan said:
No one posted a logcat of the boot failure yet, afaik.
I can clean flash a cm12 xt925 build just fine.
Unless the logs are provided, it won't get fixed (as long as it's not reproducible by the devs).
Click to expand...
Click to collapse
again on-the-fly
XT925, KK 4.4.2 stock, clean, BL unlocked, SuperSu installed, twrp v2.8.4.2 running
# install
# external_sd/#source/+rom und root/cm-12-20150217-NIGHTLY-xt925.zip
# swipe to confirm flash
=> result on screen:
Installing '/external_sd/#source/+rom und root/cm-12-20150217-NIGHTLY-xt925.zip'
Checking for MD5 file. . .
Skipping MD5 check: no MD5 file found
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
script succeeded: result was [0.200000]
Updating partition details. . .
. . .done
# Wipe cache/dalvik
# swipe to wipe
=> result on screen:
Wiping Dalvik Cache Directories. . .
Cleaned: /data/dalvik-cache. . .
- - Dalvik Cache Directories Wipe Complete!
Updating partition details. . .
. . .done
# back
# return
# external_sd/#source/+rom und root/gapps-lp-20141220-signed.zip
# swipe to confirm flash
=> result on screen:
Installing 'external_sd/#source/+rom und root/gapps-lp-20141220-signed.zip'. . .
Checking for MD5 file . . .
Skipping MD5 check: no MD5 file found
*****************************************
Google Apps for Android 4.4.2
*****************************************
Installing files . . .
Cleaning up and setting metadata . . .
Installation complete!
Upddating partition details . . .
. . .done
# Wipe cache/dalvik
# swipe to wpe
=> result on screen:
Cleaned: /data/dalvik-cache. . .
- - Dalvik Cache Directories Wipe Complete!
Updating partition details. . .
. . .done
# Back
# Reboot System
==> result:
BOOTING !
=> first time the phone is booting and installing the apps
=> results on screen:
process " . . . several during the boot . . ." was aborted
System UIDs Inconsistent
UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable
=> result after booting:
some com.google.processes were aborted, for example "com.google.phone"
# reboot in recovery twrp 2.8.4.2
# wipe
# data
# swipe to confirm
# reboot to system
==> result: BOOTLOOOOOOP
Can anyone tell me what's goin' on?
xMandy said:
again on-the-fly
XT925, KK 4.4.2 stock, clean, BL unlocked, SuperSu installed, twrp v2.8.4.2 running
# install
# external_sd/#source/+rom und root/cm-12-20150217-NIGHTLY-xt925.zip
# swipe to confirm flash
=> result on screen:
Installing '/external_sd/#source/+rom und root/cm-12-20150217-NIGHTLY-xt925.zip'
Checking for MD5 file. . .
Skipping MD5 check: no MD5 file found
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
script succeeded: result was [0.200000]
Updating partition details. . .
. . .done
# Wipe cache/dalvik
# swipe to wipe
=> result on screen:
Wiping Dalvik Cache Directories. . .
Cleaned: /data/dalvik-cache. . .
- - Dalvik Cache Directories Wipe Complete!
Updating partition details. . .
. . .done
# back
# return
# external_sd/#source/+rom und root/gapps-lp-20141220-signed.zip
# swipe to confirm flash
=> result on screen:
Installing 'external_sd/#source/+rom und root/gapps-lp-20141220-signed.zip'. . .
Checking for MD5 file . . .
Skipping MD5 check: no MD5 file found
*****************************************
Google Apps for Android 4.4.2
*****************************************
Installing files . . .
Cleaning up and setting metadata . . .
Installation complete!
Upddating partition details . . .
. . .done
# Wipe cache/dalvik
# swipe to wpe
=> result on screen:
Cleaned: /data/dalvik-cache. . .
- - Dalvik Cache Directories Wipe Complete!
Updating partition details. . .
. . .done
# Back
# Reboot System
==> result:
BOOTING !
=> first time the phone is booting and installing the apps
=> results on screen:
process " . . . several during the boot . . ." was aborted
System UIDs Inconsistent
UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable
=> result after booting:
some com.google.processes were aborted, for example "com.google.phone"
# reboot in recovery twrp 2.8.4.2
# wipe
# data
# swipe to confirm
# reboot to system
==> result: BOOTLOOOOOOP
Can anyone tell me what's goin' on?
Click to expand...
Click to collapse
The Problem with the google apps is that u usd the ones for androdi 4.4.2, i guess u need the ones for android 5...
Sorry Mandy, i was wrong, it was not a faulty gapps Version. I dont know The nistake, but i will try to pull a logcat later when i got a little more battery
Sent from my RAZR HD using XDA Free mobile app
Related
Hi ! I tried to update to 4.4.4 when my phone asked me to, but the process failed and my phone was stuck in a booting loop. I managed to delete the file causing the error, but now I don't know how to update to 4.4.4 without having the same error. I understand that because I rooted my phone I must follow a special process, but I don't know exactly what to do. Should I un-root my phone to make the update ?
Thanks for the help !
JayZeus said:
Hi ! I tried to update to 4.4.4 when my phone asked me to, but the process failed and my phone was stuck in a booting loop. I managed to delete the file causing the error, but now I don't know how to update to 4.4.4 without having the same error. I understand that because I rooted my phone I must follow a special process, but I don't know exactly what to do. Should I un-root my phone to make the update ?
Thanks for the help !
Click to expand...
Click to collapse
If you made some modification to the 4.4.2 rom you'll have to restore the stock before upgrading to 4.4.4.
Bootloader can be unlocked, Recovery can be custom but any mod/root to the room will cause the error.
To restore to stock follow this guide: http://forum.xda-developers.com/showthread.php?t=2542219
Thanks a lot, it worked!
By the way is the part where you erase you data mandatory ? In case I have to do this again.
Erase cache and erase userdata delete your stuff so if you want to keep it just do the procedure without those 2 lines and you are good to go (that's what I did and it worked flawlessly I restored without losing any data) :beer:
Sent from my XT1032 using XDA Free mobile app
mr_nooby said:
Erase cache and erase userdata delete your stuff so if you want to keep it just do the procedure without those 2 lines and you are good to go (that's what I did and it worked flawlessly I restored without losing any data) :beer:
Sent from my XT1032 using XDA Free mobile app
Click to expand...
Click to collapse
Good to know ! Thank you.
mr_nooby said:
Erase cache and erase userdata delete your stuff so if you want to keep it just do the procedure without those 2 lines and you are good to go (that's what I did and it worked flawlessly I restored without losing any data) [emoji481]
Sent from my XT1032 using XDA Free mobile app
Click to expand...
Click to collapse
This way I'll keep my installed applications?
Thanks.
4.4.2 > 4.4.4. just rolled out in UK (o2 moto g).
right after i get my phone rooted and started setting it up...
Thanks for this thread.. what's the minimum we have to restore, basically the system partition so it's unrooted?
If we have stock 4.4.2 (rooted) can we flash JUST these 3 files?
system.img_sparsechunk1
system.img_sparsechunk2
system.img_sparsechunk3
and skip the rest? I want to save redo-ing as much as possible..
I got the 4.4.4 OTA today (210.12.40.en.GB) and I have unlocked bootloader + Philz recovery - Philz worked fine for the 4.4.2 OTA update, but when I downloaded the 4.4.4 OTA and rebooted Philz would abort with "a status 7" mismatch error and then the phone would boot to Android, then 20 seconds later shutdown and reboot to Philz again, continuously. After some playing, I did the following:
1. Flashed stock recovery (taken from Mototool AIO's 4.4.2 stock.img) from fastboot - re-downloaded the 4.4.4 OTA but that failed with "Error!"
2. Flashed stock kernel (I was running faux123) - same issue, 4.4.4 OTA failed still.
3. Flashed latest Philz recovery again (philz_touch_6.50.6-falcon.zip) then
4. Flashed stock 4.4.2 GB kernel (to match my OTA version) - kernel from here http://forum.xda-developers.com/showthread.php?t=2649763 - success... OTA downloaded and this time installed.
SO, conclusion is you don't need stock recovery to flash OTA, BUT you do need the correct kernel for your update and having a custom kernel causes the mismatch error.
Hope this helps someone!
So the UPDATE-SuperSU-v1.91.zip in MotoG-Tools.zip still works to root 4.4.4 right?
i found it here
http://www.swedroid.se/forum/showthread.php?t=106595
and this is what i used for 4.4.2
Most of the old guides around no longer worked in 4.4.2, i dunno if they closed any other holes in 4.4.4?
edit: version typo sorry
just for informations, I updated succesfully from 4.4.2 to 4.4.4. Kitkat 176.44.1falcon-retail en.GB with ClockWordMod recovery v6.0.4.7
Everything worked without problems, CWM alerted me about not verified files, and gave me the option to install updates anyway.
I only have to refix the bootloader unlocked warning
JayZeus said:
I managed to delete the file causing the error, but now I don't know how to update to 4.4.4 without having the same error.
Click to expand...
Click to collapse
JayZeus,
How did you manage to delete the file? I'm assuming it's the update.zip file? At this point, I just want to use the phone and not worry about updating to 4.4.4 at this time. Thanks.
agoodhi said:
JayZeus,
How did you manage to delete the file? I'm assuming it's the update.zip file? At this point, I just want to use the phone and not worry about updating to 4.4.4 at this time. Thanks.
Click to expand...
Click to collapse
I figured it out... I simply did a delete cache from CWM recovery and now no more boot loop.
fatechand said:
just for informations, I updated succesfully from 4.4.2 to 4.4.4. Kitkat 176.44.1falcon-retail en.GB with ClockWordMod recovery v6.0.4.7
Everything worked without problems, CWM alerted me about not verified files, and gave me the option to install updates anyway.
I only have to refix the bootloader unlocked warning
Click to expand...
Click to collapse
you just updated with the OTA update (as normal)?
is it possible to do an OTA update with a rooted phone, just delete cache, keep userdata? or you have to go through all the hassle with restoring stock?
more important, is it possible to tell phone not to check for updates? if this bootloop happens with every OTA update in future, then this is not a good idea (to mod/root phone) as a user may do this and break their phone at any time. the phone is prompting regularly to apply the update.
edit: i'm guessing freezing using Titanium, MotorolaOTA 1.0 might stop update notificiations, anyone confirm if this works and is safe?
there's a nice list here but the colours don't make sense http://forum.xda-developers.com/moto-x/moto-x-qa/guide-freezing-moto-x-bloat-titanium-t2432729
Smiff2 said:
you just updated with the OTA update (as normal)?
is it possible to do an OTA update with a rooted phone, just delete cache, keep userdata? or you have to go through all the hassle with restoring stock?
more important, is it possible to tell phone not to check for updates? if this bootloop happens with every OTA update in future, then this is not a good idea (to mod/root phone) as a user may do this and break their phone at any time. the phone is prompting regularly to apply the update.
edit: i'm guessing freezing using Titanium, MotorolaOTA 1.0 might stop update notificiations, anyone confirm if this works and is safe?
there's a nice list here but the colours don't make sense http://forum.xda-developers.com/moto-x/moto-x-qa/guide-freezing-moto-x-bloat-titanium-t2432729
Click to expand...
Click to collapse
I confirm that just updated my rooted motog following Ota update, without deleting any cache or anyrhing else and of course without loosing any data.
fatechand said:
I confirm that just updated my rooted motog following Ota update, without deleting any cache or anyrhing else and of course without loosing any data.
Click to expand...
Click to collapse
Still can't do OTA update with rooted phone and CWM installed. For now, I'm just postponing the OTA each time it pops up. When I get the time, I'll put back stock recovery and try again.
Has anyone been able to OTA update to 4.4.4 with CWM (v6.0.4.6) installed?
---------- Post added at 06:32 AM ---------- Previous post was at 06:14 AM ----------
agoodhi said:
Still can't do OTA update with rooted phone and CWM installed. For now, I'm just postponing the OTA each time it pops up. When I get the time, I'll put back stock recovery and try again.
Has anyone been able to OTA update to 4.4.4 with CWM (v6.0.4.6) installed?
Click to expand...
Click to collapse
CWM message:
E: failed to verify whole-file signature
E: signature verification failed
Installing update...
assert failed: getprop("ro.product.device) == "falcon_cdma" || getprop("ro.build.product") == "falcon_cdma"
E: Error in /cache/Blur_Version.173.44.20.falcon_cdma.Verizon.en.US.zip
(Status 7)
Installation aborted.
Rebooting...
fatechand said he had CWM 6047 installed and OTA update was ok. he just had to re-root? perhaps difference between 6046 and 6047 CWM, or some difference in way you rooted?
I have same recovery, rooted, 4.4.2, so should work... ?
Please note: I know there are other guides here on XDA but none worked for me, so I'm writing this to help other stuck people.
Disclaimer: I tested this on my XT1032, I don't know if or how it will work on other variants. Following this guide you'll lose all data on your phone, make sure to backup important stuff. I'm not responsible for what you do to your phone following this guide (anyway if you're here probably you have not much to lose...)
Introduction
What happened: a couple of weeks ago I wanted to try GPE rom on my XT1032, so I flashed the appropriate rom for my device (4.4.3 KOT49H.M004) and then applied OTA (4.4.3 KOT49H.M004 to 4.4.4 KTU84P.M003). Today I decided to go back to stock, so I rebooted in bootloader mode and tried to flash stock 4.4.3.
Result: a bunch of fastboot errors, ranging from "wrong size partitions", to "preflash validation failed", to ... well I don't remember all of them, as I said they were a lot..
Then I tried older versions, I tried to reflash 4.4.3 GPE, I tried to follow guides, here on XDA and around the vast internet.. All with no luck. Until I found one and, long story short I did it. I'm back to stock 4.4.4 (flashed stock 4.4.3 and applied OTA)
I'm sharing this what I did to recover from the soft-brick, hoping to help someone. This guide is not a temporary workaround while waiting for full 4.4.4 GPE image, this will fully restore your Moto G.
Let's start
- Make sure you have fastboot drivers installed (if you managed to soft-brick it you probably have them already installed, otherwise you can get them here)
- Download and extract this
- Reboot your phone in fastboot mode (keep Volume Down and Power buttons pressed for about 5 seconds then release the power button) and plug it to the PC
- Open the extracted folder and run "GPE_XT1032_KOT49H.M004_CFC.bat". Wait for it to finish (ignore errors, they're normal), then reboot to bootloader again (choose Normal powerup and keep pressed Volume Down until it boots to bootloader again)
- Download and extract this (mirror)
- Open the extracted folder and run THE FILE "fastboot flash recovery recovery.img.bat" (poorly chosen filenames, I know)
- Wait for it to finish, then choose "Recovery" item in bootloader and let it reboot to recovery.
- Go to "mounts and storage" and select "format cache", confirm, then select "format /data and /data/media", confirm.
- Go back to main menu and select "wipe data/factory", confirm.
- Return to the folder and run the file "adb push a.zip sdcard a.zip.bat", let it finish (it will take a couple of minutes, the window will close itself when done).
- From recovery select "install zip", then "choose zip from sd card" and select "a.zip". Let it finish, then go back to main menu and choose "power options", then "reboot to bootloader"
- Download and extract this (mirror)
- Open the extracted folder and run "flashall.bat". You should see no error (I got an error while it was flashing recovery but this is not important, what you should notice is that all the errors you got before are gone). Let it finish, then give it some time to boot.
Enjoy
You're done. Now you should have a stock 4.4.2 retail EU moto g. At this point you can flash the rom you want (for example, I flashed the original retail de, since my phone is german) without getting errors
---------------------------------------------------------------------------------------------------------
More or less I followed this, but I wrote the exact steps I made, I fixed wrong commands and uploaded a more complete version for last file
i have the same problem... i am waiting for thoe missing files... and i will try to go back to stock
EDIT i can't download the filles from mega
and the first download is broken
bannab said:
i have the same problem... i am waiting for thoe missing files... and i will try to go back to stock
EDIT i can't download the filles from mega
and the first download is broken
Click to expand...
Click to collapse
I fixed first link, I'm going to check the one from mega... If you find some other problems please let me know so I'll update
Edit: mega link is working. I suppose you're from Italy (me too), it's a DNS problem (mega has been blocked by AGCOM). you can follow this guide to change dns to google ones (8.8.8.8 and 8.8.4.4). When you downloaded the file you can set them back to auto. If someone can suggest an alternative good host (and possibly a way to directly upload from mega (I have a veeeeery slow upload bandwidth) I'll appreciate
i have already tried that method but no luck..
bannab said:
i have already tried that method but no luck..
Click to expand...
Click to collapse
Try with tor bundle.. It's a version of firefox modified for privacy and security purposes, you should be able to download from mega with it
Or this
nope
again lo luck for me.. flash of stock gives me always the same errors.. i think i will keep gpe with root... and wait for a camera with slow-mo..
bannab said:
again lo luck for me.. flash of stock gives me always the same errors.. i think i will keep gpe with root... and wait for a camera with slow-mo..
Click to expand...
Click to collapse
Did you follow exactly the guide? Did you get errors while wiping or flashing a.zip from recovery?
flashing stock
maybe beacuse i have booted after flashing gpe... i needed to boot it beacuse adb gives me error (device not found)
so i will keep gpe
bannab said:
flashing stock
maybe beacuse i have booted after flashing gpe... i needed to boot it beacuse adb gives me error (device not found)
so i will keep gpe
Click to expand...
Click to collapse
That is due to drivers.. OK, in case you do it again, check recovery messages to be sure it's doing its things
You saved my phone, thank you ! :victory:
JcruzV said:
You saved my phone, thank you ! :victory:
Click to expand...
Click to collapse
You're welcome.. That little heart attack when you see it's not booting and it doesn't flash anything [emoji1]
It worked! Thank you.
doodoo28s said:
It worked! Thank you.
Click to expand...
Click to collapse
Glad I helped
Thank's my Friend ! You have save my phone ! Thank youuuuuuu !!!!!!! <3
Hello.I tried to root my device with superboot and now my phone is not booting up,i tried to reboot but still the same,my screen stays black.Can this fix my phone? thnks
Nicolae-Daniel said:
Hello.I tried to root my device with superboot and now my phone is not booting up,i tried to reboot but still the same,my screen stays black.Can this fix my phone? thnks
Click to expand...
Click to collapse
This is useful if you can't flash anything. If you can, you can just flash stock or custom ROM
i suceed come back to 4.4.2 stock!!! thank you!!!!
finally a fix
thanks for posting this fix and all the others involved. i'm on EU so now i have to get back to my regular 4.4.4 Google Play Edition. this is good till i can get that back. been trying for 2 weeks to unbrick this thing and now i have it. thanks again and to the member JcruzV who linked this post. and not to forget PhilZ. :good:
bootsie35 said:
thanks for posting this fix and all the others involved. i'm on EU so now i have to get back to my regular 4.4.4 Google Play Edition. this is good till i can get that back. been trying for 2 weeks to unbrick this thing and now i have it. thanks again and to the member JcruzV who linked this post. and not to forget PhilZ. :good:
Click to expand...
Click to collapse
Didn't know this was linked in other threads
I hope this will be sticked or something, to avoid being forgotten in a couple of months. When I was searching how to unbrick I read of people who gave up and bought a replacement, wasting money when fortunately there is a solution
It did work!
I used Linux, so had to change a few things in the command files.
There are also two things:
1.
adb push a.zip /sdcard/a.zip - no apsce before the 2nd a.zip
2.
after the 3rd step recovery complains about "new ROM will overwrite recovery" - I have answered Yes.
I have got also another problem. Meanwhile I tried to recover my phone after the downgrade from 4.4.4 GPE to 4.4.2 Motorola ROM (before this thread), I have lost the IMEI... Currently it's still 0.
Anyone have an idea to recover this?
Whats.
I have a problem with my Moto g 2013 XT1038 8 Gb
Namely, the point is that I installed the Brazilian soft on XT1033 and then I did the update to 5.0 When I wanted to go back to the stock rom Retail.eu just comes to me this error flaszuje rest of the files except for those two Motoboot.img and Partition.img. Pominołem result of these two files so that the phone is on Bootloader Unlocked. I tried to install the recovery stockrom (Sideload) system worked but most of the functions and was not such a strange god that vertical line going through the screen and the screen going crazy. Please, Fast Help.
FORUM RULES: 4. Use the English language.
I don't really understand your English, but I guess you updated your bootloader and you're trying to flash an older firmware which has an older bootloader, that's why you're getting that error.
You can't go back to an older bootloader version and the new one will conflict with KitKat kernel giving that graphical glitch (the line that you named), but it disappears after a screen off/on.
So what to do now?
t4n017 said:
I don't really understand your English, but I guess you updated your bootloader and you're trying to flash an older firmware which has an older bootloader, that's why you're getting that error.
You can't go back to an older bootloader version and the new one will conflict with KitKat kernel giving that graphical glitch (the line that you named), but it disappears after a screen off/on.
Click to expand...
Click to collapse
So what to do now?
Mac112 said:
So what to do now?
Click to expand...
Click to collapse
Stay in Lollipop or get used to the bug until some dev find a way to fix it (if possible). That's the price of rushing to Lollipop..
t4n017 said:
Stay in Lollipop or get used to the bug until some dev find a way to fix it (if possible). That's the price of rushing to Lollipop..
Click to expand...
Click to collapse
So I have to wait for StockRom Lolipop ??
Would a CM12 ROM / Kernel stop the 'screen ripple'?
lost101 said:
Would a CM12 ROM / Kernel stop the 'screen ripple'?
Click to expand...
Click to collapse
To install the 12 cm is needed first clean KitKat
In TWRP: (Warning: Wipes internal storage (photos, music etc))
Wipe > Advanced Wipe > Repair or Change File System > (select 'Data') > Change File System > (choose F2FS)
Then sideload CM12.
lost101 said:
In TWRP: (Warning: Wipes internal storage (photos, music etc))
Wipe > Advanced Wipe > Repair or Change File System > (select 'Data') > Change File System > (choose F2FS)
Then sideload CM12.
Click to expand...
Click to collapse
I thought to install CM12 czeba to firstly have 4.4 I was wrong. I read format System: The system works but bugs were so did not do anything. Tematep post is that I would like to go back to 4.4 Orgianl Stock
Hey guys, I decided to go for CM12 since I read about its features. I downloaded the last nightly build (cm-12-20150120-NIGHTLY-falcon.zip) and I booted to recovery mode (clockworkmod 6.0.5.1), then I wiped data/factory reset and flashed the zip. I got these errors:
-- Wiping data . . .
Formatting /data . . .
Formatting /cache . . .
E: unknown volume for path [/sd-ext]
Formatting /sdcard/.android_secure . . .
Data wipe complete.
Dalvik Cache wiped.
-- Wiping cache . . .
Formating /cache . . .
Cache wipe complete.
Formatting /system . . .
Done.
-- Installing: /sdcard/0/cm-12-20150120-NIGHTLY-falcon.zip
Finding update package . . .
Opening update package . . .
Installing update . . . (it took about 10 sec)
E: Error in /data/media/0/cm-12-20150120-NIGHTLY-falcon.zip
(Status 1)
Installation aborted.
Click to expand...
Click to collapse
- I also tried with an unofficial build from a post here on xda. I got the same as above.
- I found the official guide to install cyanogenmod (it doesn't specify which version) but I cannot post links so I'm gonna quote the part which I followed:
. . . 6. Select wipe data/factory reset.
7. You have two options for transferring and installing the installation packages. The sideload method is more universal across devices, whereas the push and install method is more commonly used:
Sideload method: select install zip > install zip from sideload. Follow the on-screen notices to install the package. The installer does not necessarily display an "Install complete." message. You can tell the install is complete if there were no fatal error messages and you have regained control over the menu . . .
Click to expand...
Click to collapse
and it showed this:
Sideload started . . .
Now send the package you want to apply to the device with "adb sideload <filename>" . . .
Restarting adbd . . .
Finding update package . . .
Opening update package . . .
Installing update . . .
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: Invalid argument
unmount of /system failed; no such volume
E: Error in /tmp/update.zip
(Status 1) (again)
Installation aborted.
Click to expand...
Click to collapse
GUYS, I will be very gratefull if you help me to solve this
I'm getting this error too but I have a different phone.
I fixed it
Sunjay140 said:
I'm getting this error too but I have a different phone.
Click to expand...
Click to collapse
Hey, I fixed it. You just have to download CM11 latest build and flash it. At least it worked for me!
Then if you want cm12 just update it from the updater.
I hope it works for u :laugh:
deivideliseo88 said:
Hey, I fixed it. You just have to download CM11 latest build and flash it. At least it worked for me!
Then if you want cm12 just update it from the updater.
I hope it works for u :laugh:
Click to expand...
Click to collapse
+1 Thanks
This is so strange but it worked. I thought of installing CM11 then going to CM12 but I thought that it would have been pointless but it worked after all. I have a S4 Mini so it's probably a bug in CM12. Thanks again.
I am having this same problem, I have 41.18 bootloader, after converting my 1034 to a 1032 gpe. Now I can have 4.44 moto stock, 4.4.4 gpe stock, cm11, but not CM12, have tried all recoveries, to no avail. Same as OP.
However I tried going to CM11, then upgrading, but it never makes it past the boot screen after failing the flash with status 1
Hello friends.
I have the same error.
try to update a lollipop in every possible ways.
I CM11-20150103 since the last CM can not be downloaded from the website.
The RECOVERY I use is the (TWRP 2.8.1).
I would appreciate if someone makes a detailed step by step tutorial or load the last NIGHTLY of CM11.
Thank You!
Download link for cm11
CM's official website does not link to a cm 11 download, please could someone post a download link please
HERE IS YOUR FIX, be careful!!
FIRST THING FIRST, THIS IS DANGEROUS. DO IT AT YOUR OWN RISK.
Myself and one other person have successfully done this. If you have success as well, please post here. What you DO NOT want to flash, and is the cause of bricks is motoboot.img that is older than what you have now. Just dont mess with it.
What you can do, is flash gpt.bin to get the partition tables re-partitioned to get you back to be able to flash roms from CWM, TWRP, Philz, etc.
That being said, this is my PERSONAL experience, and am only sharing because it got me out of GPE lollipop hell, and I was terrified of the bricks, like everyone else. I will attempt to be more clear in my OP.
I have an XT1034 that I converted to GPE to flash 5.0 Lollipop OTA and it gave me the new bootloader 41.18. I couldnt get to CM12 due to Status 7, and I could only flash 4.4.4 stock, lollipop stock, or CM11, any flashing to CM12 always gave errors about Status 7. Others have reported not being able to wipe /data or /system or mount either in any recovery. The problem is the updated partition table and here is the solution:
IF YOU DO NOT FOLLOW THIS DIRECTION YOU WILL HARD BRICK. DO NOT RUN THE BATCH FILE IN THE DOWNLOAD. IT CONTAINS 4.4.2 motoboot.img and YOU WILL BRICK. ONLY RUN THE COMMANDS LISTED BELOW!!!
ALSO DO NOT use an older gpt.bin, it must be 4.4.2 or newer!! Use the link below to get a 4.4.2 XT1034 stock rom.)
I flashed a 4.4.2 GPT.bin from this: US_retail_XT1034_KXB20.9-1.8-1.4_CFC.xml.zip (http://motofirmware.com/files/getdow...-14-cfcxmlzip/)
If you want to try the same thing, you can extract gpt.bin from the zip and run this: (ONLY!!)
Code:
fastboot flash partition gpt.bin
then download philz here: http://fs1.d-h.st/download/00145/DEw...8.7-falcon.img
rename to philz.img
fastboot flash recovery philz.img
Hold vol - and power, to reboot into recovery, then
format /system
format /data
Download the latest nightlies and gapps and push them like this:
adb push cm-10-10-1000.zip /data/media/0
Reboot into recovery, and flash cm12 and gapps.
WOW d33dvb!!!!
You are AWESOME!!!.....
Just came GPE 4.4.4 STOCK I put into my MOTO G.
And then always put CM11. Now I'm sure you indicate that the problem is damaged partition tables.
How do I know the bootloader i have?
Another thing that happens to me and I guess that is the partition table. When I flashed some recovery is automatically deleted after a while.
When I encourage you indicate me do what I notice.
Again thank you very much for your great contribution !!!
Sorry for my bad english My from is Argentina....
At last came the day !!
Today I did what you recommended d33dvb.
It worked all right. Right now I'm enjoying CM12.
I flash the GPT from 4.4.4.
Great HELP!! Thanks!! THANKS VERY MUCH!!
I happy!!!
Hello everyone, I have a Moto G (2013) aka first generation Moto G & I live in India. I had unlocked my bootloader. I even flashed cwm touch via fastboot but it doesn't go to recovery mode at all. I get a black screen. I tried flashing the official TWRP 2.8.4.0 today, but I get a message that reads, "Partition size mismatch" & I'm stuck. The phone is usable & it boots up normally & I use it daily. But it is the recovery that is messed up. I tried updating to lollipop by ota but the device got stuck on a black screen once the ota was downloaded. I tried downloading the KitKat factory image, but the link is dead. Please, somebody help!! Thanks in advance!
Sent from my XT1033 using xda premium
The partition size mismatch error can be ignored, You get that error because the TWRP 2.8.4.0 is for the XT1032 and not the XT1033. To flash the OTA, you have to use the stock recovery only. Your system should not be modified (eg. It shouldn't be rooted, and if it had been rooted previously, you will have to unroot it.) To flash the stock recovery again, download the Asian XT1033 4.4.4 firmware and just flash the "recovery.img" from it. The flash the OTA. The numerous guides regarding this in the general section should help you.
I have a similar question.
I have unlocked bootloader & rooted moto g.
I received official OTA update today but its not installing. Do I need to lock bootloader or do something else to install the official OTA update?
Facing a similar issue. Updated the moto g and was successful. It was used for a couple of days before the error cropped up.
Now, it boots up but goes to a black screen after the boot animation. However, it still connects to the computer and I'm able to see the phone and its files in explorer. Beyond that, I can't interact with the phone because the screen is totally black.
Additionally, I can access the bootloader, but selecting 'factory' or 'recovery' isn't doing anything - just black screens everywhere.
The phone was perfectly fine for a few days after the update. (The phone is unrooted and unmodded and was running stock at lolipop update.)
Another thread suggests that I should
Code:
fastboot erase cache
fastboot erase userdata
Is that a viable course of action? Has anybody been able to recover from this issue?
pr.itdude said:
I have a similar question.
I have unlocked bootloader & rooted moto g.
I received official OTA update today but its not installing. Do I need to lock bootloader or do something else to install the official OTA update?
Click to expand...
Click to collapse
No need to lock. Unroot, reflash stock signed recovery and you should be good to go. Also undo any modifications you made to the filesystem and wiping /cache should help prevent errors.
---------- Post added at 02:42 AM ---------- Previous post was at 02:40 AM ----------
SoberDogs said:
Facing a similar issue. Updated the moto g and was successful. It was used for a couple of days before the error cropped up.
Now, it boots up but goes to a black screen after the boot animation. However, it still connects to the computer and I'm able to see the phone and its files in explorer. Beyond that, I can't interact with the phone because the screen is totally black.
Additionally, I can access the bootloader, but selecting 'factory' or 'recovery' isn't doing anything - just black screens everywhere.
The phone was perfectly fine for a few days after the update. (The phone is unrooted and unmodded and was running stock at lolipop update.)
Another thread suggests that I should
Code:
fastboot erase cache
fastboot erase userdata
Is that a viable course of action? Has anybody been able to recover from this issue?
Click to expand...
Click to collapse
Try fastboot erase cache, it shouldn't delete any of your data and it might be enough to get the device working again. You might want to wipe the dalvik-cache as well. If all else fails, since you can access you filesystem, backup all important files and do a factory reset.
skyguy126 said:
No need to lock. Unroot, reflash stock signed recovery and you should be good to go. Also undo any modifications you made to the filesystem and wiping /cache should help prevent errors.
Click to expand...
Click to collapse
Ok. Few more Q pls:
1. Reflashing stock recovery wipes system data & apps? After this my phone will be rooted or not? Any links where i can read more about it?
2. I have stock ROM but yes I installed xposed framework & few modules. Is it a filesystem modification?
3. Any other alternative to this?
pr.itdude said:
Ok. Few more Q pls:
1. Reflashing stock recovery wipes system data & apps? After this my phone will be rooted or not? Any links where i can read more about it?
2. I have stock ROM but yes I installed xposed framework & few modules. Is it a filesystem modification?
3. Any other alternative to this?
Click to expand...
Click to collapse
1. No it should not. If you had root before you will still have it. Search in the forum for more info.
2. Yes but you can easily uninstall xposed with the click of a button.
3. This is by far the easiest and safest method. I know of one alternative is to flash the ota update zip through custom recovery but you are on your own there.
skyguy126 said:
1. No it should not. If you had root before you will still have it. Search in the forum for more info.
2. Yes but you can easily uninstall xposed with the click of a button.
3. This is by far the easiest and safest method. I know of one alternative is to flash the ota update zip through custom recovery but you are on your own there.
Click to expand...
Click to collapse
ok so Here what i am planning:
1. Uninstall all modules & xposed framework
2. Unroot using supersu
3. Restore/reflash stock recovery (just recovery not whole firmware as I already have stock rom)
4. Install the update either manually via recovery or using auto install.
Am i on right path? Pls help me on step 3, any link or step-t-step guide? I couldn't find one, every post is abt restoring whole firmware.
TIA. Cheers !!
pr.itdude said:
ok so Here what i am planning:
1. Uninstall all modules & xposed framework
2. Unroot using supersu
3. Restore/reflash stock recovery (just recovery not whole firmware as I already have stock rom)
4. Install the update either manually via recovery or using auto install.
Am i on right path? Pls help me on step 3, any link or step-t-step guide? I couldn't find one, every post is abt restoring whole firmware.
TIA. Cheers !!
Click to expand...
Click to collapse
Yep you should be good good luck!!!