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?
Hey Guys,
whenever I want to install the new OTA-Update (XNPH38R) it restarts my phone immediately and starts on the "CyanogenMod Simple Recovery" and says this
Code:
"E:unknown volume for path [/storage/emulated/0/Android/data/com.cyngn.fota/cache/cm-bacon-3628510d76-to-ac1ccf7921-singed.zip
E:Can't mount /storage/emulated/0/Android/data/com.cyngn.fota/cache/cm-bacon-3628510d76-to-ac1ccf7921-singed.zip
Installation aborted."
After that i've tried to manually browse the update and install it. Then its like this
Code:
Installing update...
assert failed: apply_patch_check ("/ system / app-priv / Velvet.apk," ... ")
E: Installation error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
I can confirm i haven't messed up with any velvet.apk file. I've checked manually in the file system and that file does exists. But the folder name in my system folder is "PRIV-APP". I did not rename that folder either (if it was app-priv).
How do i do this update? Any help would be highly appreciated.
Thanks in Advance
-topgam3r
My apologies for bumping thread as there was no reply i m trying to get some help. Thanks
Hard to say without being there with the phone myself.
Someone may suggest an easier fix, but backing up and reformatting your partitions should be a surefire fix (there's a 38R image zip you can use to flash 38R directly and cleanly).
topgam3r said:
My apologies for bumping thread as there was no reply i m trying to get some help. Thanks
Click to expand...
Click to collapse
I had the exact same problem, and resolved it thus:
1. downloaded the 33R complete update from here: http://forum.xda-developers.com/oneplus-one/general/cm11s-official-untouched-image-t2857110)
2. copy the zip to my oneplus.
3. reboot to recovery (stock CM recovery) and manually flash the 33R zip. No data wipe done. I flashed this over my existing 33R with the hope of fixing the velvet.apk issue.
4. reboot after update success and wait for 38R OTA notification.
5. After notification of OTA, proceed with download and install, phone will reboot and you'll get the first error.
6. just find the OTA update in the fota folder as you've attempted earlier and proceed with installation.
Done!
by the way, i'm not sure if this will work for you. my phone is on 38R and working well, no abnormal hiccup. credits to the OnePlus forumers at the LowYat forum Malaysia for their help. Hope this would help.
my JIRA report on this: https://jira.cyanogenmod.org/browse/BACON-1684?jql=project = BACON
dhanajay said:
I had the exact same problem, and resolved it thus:
1. downloaded the 33R complete update from here: http://forum.xda-developers.com/oneplus-one/general/cm11s-official-untouched-image-t2857110)
2. copy the zip to my oneplus.
3. reboot to recovery (stock CM recovery) and manually flash the 33R zip. No data wipe done. I flashed this over my existing 33R with the hope of fixing the velvet.apk issue.
4. reboot after update success and wait for 38R OTA notification.
5. After notification of OTA, proceed with download and install, phone will reboot and you'll get the first error.
6. just find the OTA update in the fota folder as you've attempted earlier and proceed with installation.
Done!
by the way, i'm not sure if this will work for you. my phone is on 38R and working well, no abnormal hiccup. credits to the OnePlus forumers at the LowYat forum Malaysia for their help. Hope this would help.
my JIRA report on this: https://jira.cyanogenmod.org/browse/BACON-1684?jql=project = BACON
Click to expand...
Click to collapse
Wow. Much thanks. This one solved it. Very easy and clear steps. Thank you so much
dhanajay said:
I had the exact same problem, and resolved it thus:
1. downloaded the 33R complete update from here: http://forum.xda-developers.com/oneplus-one/general/cm11s-official-untouched-image-t2857110)
2. copy the zip to my oneplus.
3. reboot to recovery (stock CM recovery) and manually flash the 33R zip. No data wipe done. I flashed this over my existing 33R with the hope of fixing the velvet.apk issue.
4. reboot after update success and wait for 38R OTA notification.
5. After notification of OTA, proceed with download and install, phone will reboot and you'll get the first error.
6. just find the OTA update in the fota folder as you've attempted earlier and proceed with installation.
Done!
by the way, i'm not sure if this will work for you. my phone is on 38R and working well, no abnormal hiccup. credits to the OnePlus forumers at the LowYat forum Malaysia for their help. Hope this would help.
my JIRA report on this: https://jira.cyanogenmod.org/browse/BACON-1684?jql=project = BACON
Click to expand...
Click to collapse
Amazing! That did it for me – thanks dhanajay
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
Hello, I am trying to flash and install custom rom into my Xperia L for the last two days and I am getting really desperate and tired now. I get boot loop almost after everything and can't get it running, so at the end I end up flashing it again to OFW with flashtool to try it again.
I had Xperia X8 before and I wanted to get my new phone rooted too because it was slow and boring.
Phone is Sony Xperia L C2105, I have tried those builds:
15.0.A.1.36
15.0.A.2.17
15.3.A.0.26
15.3.A.1.14
I have boot loop unlocked and I have tried Thunderzap 4.14 kernel and also new Phantom kernel to get my phone rooted. Only way to get it rooted was using Extended stock kernel which I also found on this thread.. both ThunderZap and Phantom was stuck in bootloop, I could only get to the recovery (wiping phone or flashing kernel didn't help). I flashed the boot.img found in Extended stock with flash tool, than went to recovery and installed super user zip. This has Rooted my phone.
But now.. every time I try to flash new kernel trough recovery, it get installed but stuck in bootloop again. But actually I through that at this point I should be able to flash custom ROMs with recovery am I right? So there are two ROMs I tried. First was CM12 and the second was Resurrection Remix. But When I start installing its zip through recovery, at both times I got stuck at the second paragraph.
This is my recovery:
- - Installing: /storage/sd.............NIGHTLY-taoshan.zip
Finding update package...
Opening update package...
Installing update...
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/userdata
At the background there is green android in animation so it isn't frozen, but it is stuck in the last line I wrote for like 20 minutes now and nothing is happening. So. . . . . . I have to put battery out again, flash it into stock, probably into 4.2.2 and try it again and hope I will find something. But it is like the twentieth time I am flashing this phone with flashtool to stock and I don't really know what to do anymore. I found so much tutorials in there but the boot loop is there most of the time without access to recovery.
Also I am working on Mac OSX and I don't have windows, I was trying it on borrowed windows notebook yesterday but with same results, but most of the programs and scripts didnt work because I have read something like in my phone is different driver than in pc and I need whole SDK for changing that, so it has written something like bad server or something and that it is killing it, so every proces was much much longer.
Please, please someone help me do something with my phone, thank you very much
nrksrs said:
Hello, I am trying to flash and install custom rom into my Xperia L for the last two days and I am getting really desperate and tired now. I get boot loop almost after everything and can't get it running, so at the end I end up flashing it again to OFW with flashtool to try it again.
I had Xperia X8 before and I wanted to get my new phone rooted too because it was slow and boring.
Phone is Sony Xperia L C2105, I have tried those builds:
15.0.A.1.36
15.0.A.2.17
15.3.A.0.26
15.3.A.1.14
I have boot loop unlocked and I have tried Thunderzap 4.14 kernel and also new Phantom kernel to get my phone rooted. Only way to get it rooted was using Extended stock kernel which I also found on this thread.. both ThunderZap and Phantom was stuck in bootloop, I could only get to the recovery (wiping phone or flashing kernel didn't help). I flashed the boot.img found in Extended stock with flash tool, than went to recovery and installed super user zip. This has Rooted my phone.
But now.. every time I try to flash new kernel trough recovery, it get installed but stuck in bootloop again. But actually I through that at this point I should be able to flash custom ROMs with recovery am I right? So there are two ROMs I tried. First was CM12 and the second was Resurrection Remix. But When I start installing its zip through recovery, at both times I got stuck at the second paragraph.
This is my recovery:
- - Installing: /storage/sd.............NIGHTLY-taoshan.zip
Finding update package...
Opening update package...
Installing update...
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/userdata
At the background there is green android in animation so it isn't frozen, but it is stuck in the last line I wrote for like 20 minutes now and nothing is happening. So. . . . . . I have to put battery out again, flash it into stock, probably into 4.2.2 and try it again and hope I will find something. But it is like the twentieth time I am flashing this phone with flashtool to stock and I don't really know what to do anymore. I found so much tutorials in there but the boot loop is there most of the time without access to recovery.
Also I am working on Mac OSX and I don't have windows, I was trying it on borrowed windows notebook yesterday but with same results, but most of the programs and scripts didnt work because I have read something like in my phone is different driver than in pc and I need whole SDK for changing that, so it has written something like bad server or something and that it is killing it, so every proces was much much longer.
Please, please someone help me do something with my phone, thank you very much
Click to expand...
Click to collapse
omfg NEVER pull out battery while flashing oO
you will need stock 15.3.A.?.17 to flash custom roms.... also you will need to do a factory reset before flash....
and a "bootloop" after fresh rom....you know it needs 30min to boot up?(rewriting cache)
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
omfg NEVER pull out battery while flashing oO
you will need stock 15.3.A.?.17 to flash custom roms.... also you will need to do a factory reset before flash....
and a "bootloop" after fresh rom....you know it needs 30min to boot up?(rewriting cache)
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
Hey thanks for answer, right now i am at 15.3.A.1.14 rooted and on Extended stock kernel found there: http://forum.xda-developers.com/xperia-l/development/kernel-extended-stock-kernel-v6-t2321550
I just wanted to try flashing Glade ROM, should I try it?
Also, At most kernels and roms there is not said which build I should use so I really dont know why it should be ?.17.. but what should I do with it when its stuck? Yesterday I went to sleep and left the Xperia installing CM12, I woke up after several hours and it was still on the second line.. I didnt ever said i have bootloop after successful fresh rom installing because I have never successfully flashed any rom because i got stuck.
But thank you wery much, I will try it on different build
nrksrs said:
Hey thanks for answer, right now i am at 15.3.A.1.14 rooted and on Extended stock kernel found there: http://forum.xda-developers.com/xperia-l/development/kernel-extended-stock-kernel-v6-t2321550
I just wanted to try flashing Glade ROM, should I try it?
Also, At most kernels and roms there is not said which build I should use so I really dont know why it should be ?.17.. but what should I do with it when its stuck? Yesterday I went to sleep and left the Xperia installing CM12, I woke up after several hours and it was still on the second line.. I didnt ever said i have bootloop after successful fresh rom installing because I have never successfully flashed any rom because i got stuck.
But thank you wery much, I will try it on different build
Click to expand...
Click to collapse
? was because i didnt remember the number....i guess its one ahead of your version (so ? = 1 ) you will DEFINITLY need LATEST stock to get a lollipop rom running without errors
SdtBarbarossa said:
? was because i didnt remember the number....i guess its one ahead of your version (so ? = 1 ) you will DEFINITLY need LATEST stock to get a lollipop rom running without errors
Click to expand...
Click to collapse
Ok, I will now download and flash 15.3.A.1.17, than flash kernel to get root and than I will try to flash Glade through recovery with instructions in its thread, thanks you so far, it will take me some time to download it and do everything but after that i will reply how I ended, really thank you
nrksrs said:
Ok, I will now download and flash 15.3.A.1.17, than flash kernel to get root and than I will try to flash Glade through recovery with instructions in its thread, thanks you so far, it will take me some time to download it and do everything but after that i will reply how I ended, really thank you
Click to expand...
Click to collapse
ok good luck bro....maybe i will be Glad(e) on you x)
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
ok good luck bro....maybe i will be Glad(e) on you x)
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
ok so I am on the newest build right now, rebooting into recovery
choosing wipe data/factory reset, wipe cache partition, wipe dalvik cache
now going to install Glade zip.. after confirmation this is the script:
Finding update package...
Opening update package...
Installing update...
Patching system image unconditionally...
Flashing SuperSU...
unmout of /system failed; no such volume
script succeeded: result was [ ]
Install from sdcard complete.
What the hell? I stayed in recovery, i am not sure if I can go out or what, how to properly flash it? What is Wrong?
nrksrs said:
ok so I am on the newest build right now, rebooting into recovery
choosing wipe data/factory reset, wipe cache partition, wipe dalvik cache
now going to install Glade zip.. after confirmation this is the script:
Finding update package...
Opening update package...
Installing update...
Patching system image unconditionally...
Flashing SuperSU...
unmout of /system failed; no such volume
script succeeded: result was [ ]
Install from sdcard complete.
What the hell? I stayed in recovery, i am not sure if I can go out or what, how to properly flash it? What is Wrong?
Click to expand...
Click to collapse
looks like the recovery you use is way to old...try to boot
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
looks like the recovery you use is way to old...try to boot
Click to expand...
Click to collapse
it said root access possibly lost and if I want to root again, I choose I want to and it started rebooting, now after sony logo there is animated green Glade logo going again and again, I will se if it will start, I will give it some time
EDIT: i have that app on card that can install recovery directly from system, if it wont strat i will propably have to flash to stock again and try the app
nrksrs said:
it said root access possibly lost and if I want to root again, I choose I want to and it started rebooting, now after sony logo there is animated green Glade logo going again and again, I will se if it will start, I will give it some time
EDIT: i have that app on card that can install recovery directly from system, if it wont strat i will propably have to flash to stock again and try the app
Click to expand...
Click to collapse
if it dont start....
download thunderzap4.14 from varuns site
then extract the boot.img from the zip...
and flash that boot.img...
then you will have a good recovery... factory reset...
flash glade
that should work
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
if it dont start....
download thunderzap4.14 from varuns site
then extract the boot.img from the zip...
and flash that boot.img...
then you will have a good recovery... factory reset...
flash glade
that should work
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
Did it. The first time phone got stuck at thunderzap logo, second time I got into recovery, fastory reset + wipe cache, than flashed rom and got exactly the same script as before.. I am really starting to give up, any ideas?
nrksrs said:
Did it. The first time phone got stuck at thunderzap logo, second time I got into recovery, fastory reset + wipe cache, than flashed rom and got exactly the same script as before.. I am really starting to give up, any ideas?
Click to expand...
Click to collapse
ok....try another rom...maybe its the rom or your download
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
ok....try another rom...maybe its the rom or your download
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
will try that, buti am just wondering, when I wipe something I can see at most of the scripts this line:
E:unknown volume for path [/sd-ext] ..this is the only error i am getting but every other thing is all right, does it mean something?
EDIT: tried to flash cm12 after wiping and I got stuck at the same line again:
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/userdata
android in background is animated but I dont think it will get somewhere
nrksrs said:
will try that, buti am just wondering, when I wipe something I can see at most of the scripts this line:
E:unknown volume for path [/sd-ext] ..this is the only error i am getting but every other thing is all right, does it mean something?
Click to expand...
Click to collapse
lol that is the error you will get if you dont have a micro-sd (sd-ext) in phone
if you have no sd-ext....thats logic you can ignore
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
lol that is the error you will get if you dont have a micro-sd (sd-ext) in phone
if you have no sd-ext....thats logic you can ignore
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
but everything i am intalling is on my sd card so i have card inside, that doesn't make sense
also I have to put the battery out again during the rom instalation to abort
EDIT: Maybe different kernel could fix it but every other kernel I have found will bootloop it. Is there a way to exit boot loop after installing thunderzap or something?
nrksrs said:
but everything i am intalling is on my sd card so i have card inside, that doesn't make sense
also I have to put the battery out again during the rom instalation to abort
Click to expand...
Click to collapse
important: tested just on CM.
You must be on the latest stock firmware.
I want you to go to this link " http://forum.xda-developers.com/xperia-l/help/how-to-recover-xperia-l-t3129724/page5 " .
And to replay number #46 and download the attached file.
Extract the the file in your computer and open the cmd in the folder by pressing shift+LMB and write the code:
Code:
fastboot flash boot boot.img
important:connect your phone to the computer in fastboot before holding the vol+ and connect it.
Now you can press entre you have now CWM recovery .
Boot to recovery and flash CM12 then make a factory reset and boot to system .
If you want to flash the gapps don't flash directly after flashing CM12 just wait until your phone boot and contact me and I will guide you.
n78 shadow said:
important: tested just on CM.
You must be on the latest stock firmware.
I want you to go to this link " http://forum.xda-developers.com/xperia-l/help/how-to-recover-xperia-l-t3129724/page5 " .
And to replay number #46 and download the attached file.
Extract the the file in your computer and open the cmd in the folder by pressing shift+LMB and write the code:
Code:
fastboot flash boot boot.img
important:connect your phone to the computer in fastboot before holding the vol+ and connect it.
Now you can press entre you have now CWM recovery .
Boot to recovery and flash CM12 then make a factory reset and boot to system .
If you want to flash the gapps don't flash directly after flashing CM12 just wait until your phone boot and contact me and I will guide you.
Click to expand...
Click to collapse
As I have said in the very first post, I am on mac and cant do it in windows, but still i should be able to do it, I will just edit the code, will the boot.img root this phone? because if I am starting with stock firmwere do you mean rooted stock?
nrksrs said:
As I have said in the very first post, I am on mac and cant do it in windows, but still i should be able to do it, I will just edit the code, will the boot.img root this phone? because if I am starting with stock firmwere do you mean rooted stock?
Click to expand...
Click to collapse
No it will not just reboot to recovery after you flash it there's no need to boot to system becuse if you reboot to stock the WiFi will not work so just flash CM12 directly after flashing the boot.img .
That how I install CM12 in my phone and the WiFi and everything works fine.
And about the root: if you installed CM12 you can have a root in the developers option
Good luck bro.
n78 shadow said:
No it will not just reboot to recovery after you flash it there's no need to boot to system becuse if you reboot to stock the WiFi will not work so just flash CM12 directly after flashing the boot.img .
That how I install CM12 in my phone and the WiFi and everything works fine.
And about the root: if you installed CM12 you can have a root in the developers option
Good luck bro.
Click to expand...
Click to collapse
This is really weird, in a second I got stuck at the same line as before but it than continued and finished. As I chodes reboot to system it said it will root the phone or something, now there is blue robot head (probably cm12 animation), now it really looks like it will work,
I will say later if it booted into system, also good to say, for this one try I switched the sd card from which I were installing before, maybe it was card
wait, now there are some optimalisations or upgrades
nrksrs said:
This is really weird, in a second I got stuck at the same line as before but it than continued and finished. As I chodes reboot to system it said it will root the phone or something, now there is blue robot head (probably cm12 animation), now it really looks like it will work,
I will say later if it booted into system, also good to say, for this one try I switched the sd card from which I were installing before, maybe it was card
wait, now there are some optimalisations or upgrades
Click to expand...
Click to collapse
What for it .
It would take some time
It says " upgrading android apps " right???