Stock with unlocked bootloader warning removed
Motorola 4G 4.4.4 Kitkat for EUROPE/AUSTRALIA aka XT1039
This is for unlocked bootloader only
Update brings:
Android 4.4.4 Kitkat
SD Card Fixes
Instructions:
FLASH CWM
WIPE DATA/FACTORY RESET
FLASH ROM
FLASH Super SU (if you want to root)
WIPE DALVIK.
ENJOY!
Only tested with CWM
Dowload:
Mega
Google Drive
If you want another filehost just ask and if the zip does not work tell me we will look into it :highfive:
OMG!!!
About root procedure... Did anyone know about it?
Flash this Super SU
Ps: Is my update working ?
I didn't try it yet. I prefer TWRP, so I was going to test if it's working with it. But I just got the XT1039 last week, so I set it up to my liking, then I unlocked bootloader to root it, so second setup, and then I messed up deleting some files (don't really know what happened), so I had to set it up for the 3rd time just yesterday. I'm not in the mood of wiping it again just yet!
But i will
EDIT: Just installed it, with TWRP and wiping only cache. Works like a charm!
I did the update with the file above without any wipe (except cache)
Envoyé de mon XT1039 en utilisant Tapatalk
It works perfectly, thank you!
I was having some trouble updating to 4.4.4 using OTA as I changed a lot in the stock rom. After spending hours reverting changes, I still couldn't get it to work (without flashing stock and starting all over again, which I didn't want to do really).
Was thinking of starting all over again, flashing stock image, OTA to 4.4.4 and changing everything after that, when I came across your thread.
You saved me from spending hours having to start from scratch! Top job!
I only flashed your file from my OTG drive in TWRP , over my heavily changed system, and it works like a dream.
See this screenshot I took right after flashing and reboot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So, yes man, you did it! Thanks again! [emoji106]
Verstuurd vanaf mijn XT1039 met Tapatalk
Nice work Darius.
Also had probs with 4.4.4 OTA due to custom recovery/rooting.
This was easiest way to 4.4.4 happiness....
I want to try this one, but I want to know how can I verify that bootloader is locked or not, and how can I unlock it.
Any threat talking about this?
PD: Could be unlocked from adb typing "fastboot oem unlock"?
Will this work for the XT1039 from Great Britain? Build numbers are the same but instead of EU there is a GB. I bought mine from Amazon and it is the unlocked version.
Awesome!
Hi,
Just installed on my 4.4.3, wiping only the cache partition as you said. As far as I can see everythying works perfectly.
Thank you man !
guijarrelson said:
I want to try this one, but I want to know how can I verify that bootloader is locked or not, and how can I unlock it.
Any threat talking about this?
PD: Could be unlocked from adb typing "fastboot oem unlock"?
Click to expand...
Click to collapse
The bootloader is proprietary so you need to ask Motorola for an unlock code. "Fastboot oem unlock" won't work. There are a lot of threads about this in Q&A and General.
I just finished updating my GB version to this EU version and it worked great! No issues to report. Installed CWM recovery, then EU 4.4.4., wiped cache then installed superuser. Fantastic work with no lost data. My 32GB sdcard works too!!!! AMAZING
I tried using a Sandisk 32 Gb sd card (bought in 2011, and still working perfectly in my old HTC Desire) that didn't work in this phone before the update, but it still doesn't. Have seen other reports about the same issue, so I guess not every sd card problem is solved with the 4.4.4 update.
The card mounts normally, I can see the files on it in any explorer, but it's not possible to read from or write onto the card.
Phone can't format the card, and a check with a Windows pc doesn't show anything wrong with the card.
Strange huh? Any ideas?
I've flashed this and all is working but I can not enable ART can someone else let me know if they can or can't please?
mhisani said:
I've flashed this and all is working but I can not enable ART can someone else let me know if they can or can't please?
Click to expand...
Click to collapse
Do you have xposed framework installed? Art doesnt work with it so...
Second, do you have enough internal memory free?
jkoetsier said:
Do you have xposed framework installed? Art doesnt work with it so...
Second, do you have enough internal memory free?
Click to expand...
Click to collapse
I factory reset the device and still I could not. I flashed the rom via recovery and that seemed to solve it.. perhaps xposed changed something that was not cleared on wipining
mhisani said:
I factory reset the device and still I could not. I flashed the rom via recovery and that seemed to solve it.. perhaps xposed changed something that was not cleared on wipining
Click to expand...
Click to collapse
Factory Reset does not touch your system partition. Only wipes your data.
Xposed would have modified your system partition to prevent ART. Flashing a new rom would restore your system partition to how it was.
Next time, either disable xposed before uninstalling. Or if that doesn't work, either fastboot flash the system.img chunks found in the stock firmware OR flash the same firmware in a custom recovery (if zip available). This will refresh your system partition and restore any changes without affecting your data.
Edit: ignore
Wait so will this work on the XT1045?
I have flashed this ROM and my SD card (Sandisk 16 GB) is still not recognized by the phone. Any advices ?
Related
Hi there!
I received my HTC One two days ago and I am unable to install any PAID apps on the phone. I am able to install free apps without an issue though.
I have searched all over the internet and found two possible solutions, which don't work. These solutions were:
Unmount the SD card. Install app, remount the SD card. This won't work as the HTC One does not have an SD card
In the secure/asec folder, find and delete "smdl2tmp1.asec". Although I found the folder, it was empty and therefore I was unable to delete the file.
I have also completely wiped my phone twice already. I checked the Kernel and Firmware version and it's all up to date. Below are screenshots of the device info.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Finally, I also realized, only after I paid for the device, it's a Dev device. I don't know if this makes any difference though.
The bootloader is unlocked and the device has been rooted. I have full access over the file system.
Make a nandroid and flash another rom to see if that fixes it.
You're using an old custom ROM! Flash any new ROM of your choice from the dev section and it should fix the problem. The issue is within the kernel.
StephanBotha said:
Hi there!
I received my HTC One two days ago and I am unable to install any PAID apps on the phone. I am able to install free apps without an issue though.
I have searched all over the internet and found two possible solutions, which don't work. These solutions were:
Unmount the SD card. Install app, remount the SD card. This won't work as the HTC One does not have an SD card
In the secure/asec folder, find and delete "smdl2tmp1.asec". Although I found the folder, it was empty and therefore I was unable to delete the file.
I have also completely wiped my phone twice already. I checked the Kernel and Firmware version and it's all up to date. Below are screenshots of the device info.
Finally, I also realized, only after I paid for the device, it's a Dev device. I don't know if this makes any difference though.
The bootloader is unlocked and the device has been rooted. I have full access over the file system.
Click to expand...
Click to collapse
Hi,
I'm having a similar problem to the OP. I have a GPE HTC One which is rooted and S-Off. I just updated the software from 4.4 to 4.4.2, at which point the inability to update or install paid apps appeared. As in the original post, I can't find the smdl2tmp1.asec. In fact, my entire mnt/secure folder is empty, as is mnt/asec. I also don't have a .android_secure folder, as has been mentioned in other posts. If I restore to a previous backup running 4.4, everything works fine. The issue is only with installs or updates from the Play Store, because I am able to install the apps from my Titanium backups just fine, but when I do, I get the same error message when I try to update them.
Thanks
roman1984 said:
Hi,
I'm having a similar problem to the OP. I have a GPE HTC One which is rooted and S-Off. I just updated the software from 4.4 to 4.4.2, at which point the inability to update or install paid apps appeared. As in the original post, I can't find the smdl2tmp1.asec. In fact, my entire mnt/secure folder is empty, as is mnt/asec. I also don't have a .android_secure folder, as has been mentioned in other posts. If I restore to a previous backup running 4.4, everything works fine. The issue is only with installs or updates from the Play Store, because I am able to install the apps from my Titanium backups just fine, but when I do, I get the same error message when I try to update them.
Thanks
Click to expand...
Click to collapse
Hi,
I have this exact same issue. Nothing in secure folder etc. From 4.4 to 4.4.2 via OTA.
roman1984 said:
Hi,
I'm having a similar problem to the OP. I have a GPE HTC One which is rooted and S-Off. I just updated the software from 4.4 to 4.4.2, at which point the inability to update or install paid apps appeared. As in the original post, I can't find the smdl2tmp1.asec. In fact, my entire mnt/secure folder is empty, as is mnt/asec. I also don't have a .android_secure folder, as has been mentioned in other posts. If I restore to a previous backup running 4.4, everything works fine. The issue is only with installs or updates from the Play Store, because I am able to install the apps from my Titanium backups just fine, but when I do, I get the same error message when I try to update them.
Thanks
Click to expand...
Click to collapse
The only fix for this is to install Android Revolution ROM. At least, that's the only way I could fix mine :crying:
You should always use stock recovery for OTA updates. This problem is probably due to applying the OTA with a custom recovery.
BenPope said:
You should always use stock recovery for OTA updates. This problem is probably due to applying the OTA with a custom recovery.
Click to expand...
Click to collapse
That's unfortunate, since I like twrp. To reinstall stock recovery, do I just flash the image like I did with twrp?
Yes. You can put TWRP back on after the OTA is on.
BenPope said:
Yes. You can put TWRP back on after the OTA is on.
Click to expand...
Click to collapse
Thanks, that did the trick. Going back and forth between recoveries like that is a little annoying, but fortunately it's relatively quick, so it's not horrible.
roman1984 said:
Thanks, that did the trick. Going back and forth between recoveries like that is a little annoying, but fortunately it's relatively quick, so it's not horrible.
Click to expand...
Click to collapse
Did you have to go back to TWRP and reinstall the GPe ROM? Or did you just have to flash TWRP and it started working again?
DyingBlade said:
Did you have to go back to TWRP and reinstall the GPe ROM? Or did you just have to flash TWRP and it started working again?
Click to expand...
Click to collapse
Once I was able to update using the stock recovery, all I had to do was flash TWRP and everything worked fine (no need to reinstall the GPE ROM since that was already running).
Hey guys, I have an XT1064 US GSM Moto G.
I followed the tutorial here and flashed the appropriate image to restore the phone to stock: http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
Now, my wifi no longer works no matter what I do.
I have tried deleting the wpa_supplicant.conf file, flashing a different kernel, rebooting without the sim, and wifi will not turn on no matter what. As soon as I slide it on the button snaps back to the off position
Some help would be very much appreciated!! Thanks!
EDIT: Also, every line of flashing has returned [OKAY], and I've run the phone with stock recovery, CWM, and TWRP and no difference
Is it possible I have to relock my bootloader? I don't see how that would affect it but im not an expert
I have the exact same problem... But my device is a XT1069.
Still waiting for a solution... :/
Bl00dyMurd3r said:
Hey guys, I have an XT1064 US GSM Moto G.
I followed the tutorial here and flashed the appropriate image to restore the phone to stock: http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
Now, my wifi no longer works no matter what I do.
I have tried deleting the wpa_supplicant.conf file, flashing a different kernel, rebooting without the sim, and wifi will not turn on no matter what. As soon as I slide it on the button snaps back to the off position
Some help would be very much appreciated!! Thanks!
EDIT: Also, every line of flashing has returned [OKAY], and I've run the phone with stock recovery, CWM, and TWRP and no difference
Is it possible I have to relock my bootloader? I don't see how that would affect it but im not an expert
Click to expand...
Click to collapse
Did you download your XT1064 firmware from here:
http://sbf.droid-developers.org/phone.php?device=36
We are not supposed to install XT1069 firmware on XT1064
rafaelbrunner said:
I have the exact same problem... But my device is a XT1069.
Still waiting for a solution... :/
Click to expand...
Click to collapse
me too xt1068
Thanks for the link, but i did not flash XT1069 firmware, I followed the guide steps to flash "Blur_Version.21.11.17.titan_retuaws.retuaws.en.US" as I have the US gsm model
This will only happen if you updated the phone with latest OTA, you can't downgrade the bootloader, if you apply the latest OTA the problem should be solved.
MiguelPT said:
This will only happen if you updated the phone with latest OTA, you can't downgrade the bootloader, if you apply the latest OTA the problem should be solved.
Click to expand...
Click to collapse
I tried applying the update from this thread from the stock recovery: http://forum.xda-developers.com/moto-g-2014/general/ota-update-t2880432
The recovery starts to verify the package and then I get "Installation aborted."
It does this with both locked and unlocked bootloader
Any other help would be great, thanks!
Bl00dyMurd3r said:
I tried applying the update from this thread from the stock recovery: http://forum.xda-developers.com/moto-g-2014/general/ota-update-t2880432
The recovery starts to verify the package and then I get "Installation aborted."
It does this with both locked and unlocked bootloader
Any other help would be great, thanks!
Click to expand...
Click to collapse
According to Q18 from this page you need to select full unroot option from the Super Su:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then follow the "[Restore to Stock][XT1068][All Dual Sim Model][4.4.4][Lock Bootloader]" and use XT1064 firmware just to see if your wifi works or not.
pleomaxell said:
According to Q18 from this page you need to select full unroot option from the Super Su:
Then follow the "[Restore to Stock][XT1068][All Dual Sim Model][4.4.4][Lock Bootloader]" and use XT1064 firmware just to see if your wifi works or not.
Click to expand...
Click to collapse
Thanks, I'll give it a shot!
Well, tried that and no luck. This is my 3rd android device and I've never heard of Wifi being borked like this
Bl00dyMurd3r said:
Well, tried that and no luck. This is my 3rd android device and I've never heard of Wifi being borked like this
Click to expand...
Click to collapse
Sorry, I don't know what to suggest, it looks like another user was facing a similar problem and no one could provide a solution to him too.
Can't you return the phone and get it replaced?
pleomaxell said:
Sorry, I don't know what to suggest, it looks like another user was facing a similar problem and no one could provide a solution to him too.
Can't you return the phone and get it replaced?
Click to expand...
Click to collapse
It looks like I'll have to. Amazon customer service is top notch, but I'll have to flash over the unlocked bootloader warning and then relock it, hopefully all bases will be covered
Bl00dyMurd3r said:
It looks like I'll have to. Amazon customer service is top notch, but I'll have to flash over the unlocked bootloader warning and then relock it, hopefully all bases will be covered
Click to expand...
Click to collapse
I had no success in re-locking my device's bootloader...
Did you have any luck with that?
rafaelbrunner said:
I had no success in re-locking my device's bootloader...
Did you have any luck with that?
Click to expand...
Click to collapse
Yes, on my 1064 i issued these commands while on the bootloader:
mfastboot.exe oem lock begin
mfastboot.exe oem lock
It returned a [FAILED] in cmd, but after reboot the bootloader reported it was indeed locked. The unlocked bootloader warning still appeared however, but the logo fix could probably be applied prior to re-locking
Bl00dyMurd3r said:
Yes, on my 1064 i issued these commands while on the bootloader:
mfastboot.exe oem lock begin
mfastboot.exe oem lock
It returned a [FAILED] in cmd, but after reboot the bootloader reported it was indeed locked. The unlocked bootloader warning still appeared however, but the logo fix could probably be applied prior to re-locking
Click to expand...
Click to collapse
me the saame....i think there isnt solution.....:crying:
WIFI fix
Hi Guys,
Cause of problem: I formated partition /persist on my moto G. I am stupid, I know. Unfortunately this partition is untouched by any flashes you will do, so you you can flash any Roms or factory images, Wifi will not work.
Here's how to fix it (you MUST be rooted):
1. ROOT your phone
2. download this http://forum.xda-developers.com/attachment.php?attachmentid=2531514&d=1390364984
3. download Root explorer from play store
4. download Rar archiver from play store
5. then unrar downloaded file
6. copy the unrared file from /storage/sdcard0/download to /persist with root explorer
7. reboot and your WiFi should work.
Simple thanks is enough
linasmit said:
Hi Guys,
Cause of problem: I formated partition /persist on my moto G. I am stupid, I know. Unfortunately this partition is untouched by any flashes you will do, so you you can flash any Roms or factory images, Wifi will not work.
Here's how to fix it (you MUST be rooted):
1. ROOT your phone
2. download this http://forum.xda-developers.com/attachment.php?attachmentid=2531514&d=1390364984
3. download Root explorer from play store
4. download Rar archiver from play store
5. then unrar downloaded file
6. copy the unrared file from /storage/sdcard0/download to /persist with root explorer
7. reboot and your WiFi should work.
Simple thanks is enough
Click to expand...
Click to collapse
IT WORKS!!! Tested here on XT1069!
Thank you once is not enough... Thanks a MILLION, brother! :good:
linasmit said:
Hi Guys,
Cause of problem: I formated partition /persist on my moto G. I am stupid, I know. Unfortunately this partition is untouched by any flashes you will do, so you you can flash any Roms or factory images, Wifi will not work.
Here's how to fix it (you MUST be rooted):
1. ROOT your phone
2. download this http://forum.xda-developers.com/attachment.php?attachmentid=2531514&d=1390364984
3. download Root explorer from play store
4. download Rar archiver from play store
5. then unrar downloaded file
6. copy the unrared file from /storage/sdcard0/download to /persist with root explorer
7. reboot and your WiFi should work.
Simple thanks is enough
Click to expand...
Click to collapse
Oh my god thank you so much!! My phone is back to life!! :laugh:
I am glad that all of you found a solution to this problem.
in case anyone lands here from google...
I successfully upgraded to 5.02 and WiFi was working initially.
but then i had to change the custom recovery and superSU, and changed the logo.bin, now the WiFi is no longer working.
--- EDIT ---
after careful examination, found out it was caused by xt1064_lollipop_boot.img
in the end I flashed back to the stock boot.img from 5.02
and then flashed twrp-2.8.6.0-titan.img
now everything is great!
Hi guys,
As I wrote in the title, my Verizon Nexus 6 will not update. When I get a notification for the software update, I see that it downloads and is ready to restart the phone so it will install the update...
but when I do, it will display the android icon with the word "error" above it. No error number or details about why it did not work.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Things I tried already are:
formatting the phone (both through the settings menu as well as the stock bootloader)
deleting data and cache in Google Services Framework (via settings/apps/all apps)
I have more than enough space in my storage; more than 2/3rds of my storage is free space, so I really am having trouble wrapping my head around why this software update is failing to install. And since all the threads and help things I find are for rooted phones, I am having trouble finding something that would offer an answer. I was hoping to keep this phone stock as long as possible, which is an oddity for me because I usually want to root my phone immediately. I guess I just really like this phone as stock. And other than this update that fails to load, the phone has no other issues, other than a few emojis that fail to show, but I feel like that's from the software not being able to update for the 6 months that I've been trying to update it.
Any help with this would be greatly appreciated! Thank you!!
Is your device unlocked? Have you tried to sideload the update?
If your device is unlocked you can use NRT to update without loosing any data.
PickelledEggs said:
Hi guys,
As I wrote in the title, my Verizon Nexus 6 will not update. When I get a notification for the software update, I see that it downloads and is ready to restart the phone so it will install the update...
but when I do, it will display the android icon with the word "error" above it. No error number or details about why it did not work.
Things I tried already are:
formatting the phone (both through the settings menu as well as the stock bootloader)
deleting data and cache in Google Services Framework (via settings/apps/all apps)
I have more than enough space in my storage; more than 2/3rds of my storage is free space, so I really am having trouble wrapping my head around why this software update is failing to install. And since all the threads and help things I find are for rooted phones, I am having trouble finding something that would offer an answer. I was hoping to keep this phone stock as long as possible, which is an oddity for me because I usually want to root my phone immediately. I guess I just really like this phone as stock. And other than this update that fails to load, the phone has no other issues, other than a few emojis that fail to show, but I feel like that's from the software not being able to update for the 6 months that I've been trying to update it.
Any help with this would be greatly appreciated! Thank you!!
Click to expand...
Click to collapse
You might try clearing the cache partition in recovery and reboot. Maybe the next OTA will be install without issues.
lol!
if you made any kind of changes, chances are that any ota will not work. but that's alright, all you have to do is flash the factory image. it would've been updated already if you did that instead of writing out your post. you can grab it here https://developers.google.com/android/nexus/images
simms22 said:
lol!
if you made any kind of changes, chances are that any ota will not work. but that's alright, all you have to do is flash the factory image. it would've been updated already if you did that instead of writing out your post. you can grab it here https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
I don't think you read my post at all... I didn't make any changes. My phone is fully stock. No root at all. No unlock. No modifications whatsoever The ota Software update just will not work.
gee2012 said:
You might try clearing the cache partition in recovery and reboot. Maybe the next OTA will be install without issues.
Click to expand...
Click to collapse
I tried going in to recovery mode, but when I do, it gives me the same android error icon, but instead of "error" it says "no command"
Timza said:
Is your device unlocked? Have you tried to sideload the update?
If your device is unlocked you can use NRT to update without loosing any data.
Click to expand...
Click to collapse
Nope. Not unlocked. No modification whatsoever
PickelledEggs said:
Nope. Not unlocked. No modification whatsoever
Click to expand...
Click to collapse
If you nothing else works, I would try to sideload the update by downloading the image from Google's Factory Images for Nexus Devices page.
PickelledEggs said:
Nope. Not unlocked. No modification whatsoever
Click to expand...
Click to collapse
Best is to enable OEM UNLOCKING and usb debugging in developer options, reboot into fastboot and unlock the bootloader and after the reboot flash the latest MMB29S firmware as @simms22 allready stated. Flash the img`s seperately in fastboot, all i would flash personaly is the system and boot img.
Timza said:
If you nothing else works, I would try to sideload the update by downloading the image from Google's Factory Images for Nexus Devices page.
Click to expand...
Click to collapse
gee2012 said:
Best is to enable OEM UNLOCKING and usb debugging in developer options, reboot into recovery and unlock the bootloader and after the reboot flash the latest MMB29S firmware as @simms22 allready stated. Flash the img`s seperately in fastboot, all i would flash personaly is the system and boot img.
Click to expand...
Click to collapse
Oh ok, I must have misinterpereted what SImmz was saying, then. I got in to recovery mode and wiped cache finally, so I will see if that works, otherwise I'll try your guys' other suggestions
PickelledEggs said:
Oh ok, I must have misinterpereted what SImmz was saying, then. I got in to recovery mode and wiped cache finally, so I will see if that works, otherwise I'll try your guys' other suggestions
Click to expand...
Click to collapse
I had this issue with my Nexus 7 (stock) - wiped the cache partition in recovery, and waited for OTA to appear again - and it worked.
BTW, you don't need root to make certain changes(I don't know what changes, but I know many don't get ota because of). or google just made it to sensitive.
Timza said:
If you nothing else works, I would try to sideload the update by downloading the image from Google's Factory Images for Nexus Devices page.
Click to expand...
Click to collapse
You can only sideload OTA`s in stock recovery afaik, not complete images.
gee2012 said:
You can only sideload OTA`s in stock recovery afaik, not complete images.
Click to expand...
Click to collapse
Ah, my mistake. I (wrongly) assumed OTAs were included on that download page.
is using nexus root tool kit let you flash with su 2.5.2 or it using the lastest 2.66? or that makes no difference when flashing stock image?
MikePancake6 said:
is using nexus root tool kit let you flash with su 2.5.2 or it using the lastest 2.66? or that makes no difference when flashing stock image?
Click to expand...
Click to collapse
The latest version of NRT (v2.1.4) uses SuperSU 2.6.6.
Timza said:
The latest version of NRT (v2.1.4) uses SuperSU 2.6.6.
Click to expand...
Click to collapse
is there any way to use 2.5.2, or flashing a custom rom will system root or will it be systemless root anyhow?
MikePancake6 said:
is there any way to use 2.5.2, or flashing a custom rom will system root or will it be systemless root anyhow?
Click to expand...
Click to collapse
After you flash with TWRP (a step with NRT). When you opt to reboot system, you will get a message asking if you would like to install SuperSU. If you swipe to install you will have a "system root". If you opt to not install, you will have a systemless root.
Personally, I have a "system root", and it seems to be working fine, whereas before, I was having an issue with the systemless root.
Timza said:
After you flash with TWRP (a step with NRT). When you opt to reboot system, you will get a message asking if you would like to install SuperSU. If you swipe to install you will have a "system root". If you opt to not install, you will have a systemless root.
Personally, I have a "system root", and it seems to be working fine, whereas before, I was having an issue with the systemless root.
Click to expand...
Click to collapse
ok, thank you for all the help. i already unlocked the bootloader using the tool kit.
tonight i will root it and try a custom rom. maybe chrome or pure nexus project, those seem to be stock with extra options and rro customize.
Thanks guys. I just got around to sideloading the update last night and it's working like a dream.
I'll probably root it soon now. I've been feeling the itch recently... Lol
This (so far) is probably my favorite stock phone though. I might keep it stock for a bit longer
Sent from my Nexus 6 using Tapatalk
I'm creating this thread since we're not allowed to discuss a kernel patch for LOS 14.1 to make Android Pay work on the official thread. From my understanding the biggest issue right now is that Android Pay does not work on LOS because it cannot pass SafetyNet because of unlocked bootloader. We cannot lock the bootloader because we risk hard-bricking the device.
Some (most?) banking apps can still work by flashing Magisk 10.2 and then using Magisk Hide on the banking app, however Android Pay cannot.
Anyone who has any work-in-progress on a kernel patch feel free to post or let us know of any updates. Thank you.
edit: SOLUTION: https://forum.xda-developers.com/showpost.php?p=70831797&postcount=3665
Was just looking for someone to pose the same question, I'm eagerly waiting to see if anyone has had any luck
Please try this patch
https://review.lineageos.org/#/c/152083/
josephjdrew said:
Was just looking for someone to pose the same question, I'm eagerly waiting to see if anyone has had any luck
Click to expand...
Click to collapse
deathscythemeng said:
Please try this patch
https://review.lineageos.org/#/c/152083/
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=70831797&postcount=3665
AfouToPatisa said:
https://forum.xda-developers.com/showpost.php?p=70831797&postcount=3665
Click to expand...
Click to collapse
Following the directions in that post I:
Flashed the Lineage addonsu-remove package because I was rooted the Lineage way
reboot
Flash the gemini-safetynetpass package
Reboot
That didn't work (Android Pay still rejected my device).
So I wiped System, Cache, Dalvik, then reinstalled latest LOS.
Reboot and reinstall the gemini-safetynet pass zip.
Still Android Pay won't work.
What is going wrong?
My final intention is to root the device with Magisk. If I install it now, will it help at all?
The patch is working for me. SafetyNet passed.
Please check SafetyNet at first.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my MI 5 using Tapatalk
p8pepe said:
The patch is working for me. SafetyNet passed.
Please check SafetyNet at first.
Click to expand...
Click to collapse
SafetyNet fails... "CTS profile mismatch"
I'll try again with a fully clean install tomorrow - unless I can get a better suggestion before then.
AaronWhiting said:
SafetyNet fails... "CTS profile mismatch"
I'll try again with a fully clean install tomorrow - unless I can get a better suggestion before then.
Click to expand...
Click to collapse
I pass SafetyNet too now. Are you sure you removed root completely? Maybe run a root checker or something. Did you flash the kernel patch with "install zip" option on twrp? Which twrp version are you on? I'm on 3.0.3, it has a small bug for me (takes long time to start) but it's quite good and stable.
AfouToPatisa said:
I pass SafetyNet too now. Are you sure you removed root completely? Maybe run a root checker or something. Did you flash the kernel patch with "install zip" option on twrp? Which twrp version are you on? I'm on 3.0.3, it has a small bug for me (takes long time to start) but it's quite good and stable.
Click to expand...
Click to collapse
Yes, I did all that. Root definitely not enabled. Installed zips using TWRP 3.0.3.
AaronWhiting said:
Yes, I did all that. Root definitely not enabled. Installed zips using TWRP 3.0.3.
Click to expand...
Click to collapse
It's very weird. Seems like you do everything right. I'm very new to this, so maybe wait for an advanced user to answer. If I was you, I might try to play with the developer options (disable debugging, enable oem unlock etc) or reflash the patch zip or flash magisk zip (and then open magisk app and enable magisk hide).
AaronWhiting said:
Yes, I did all that. Root definitely not enabled. Installed zips using TWRP 3.0.3.
Click to expand...
Click to collapse
Please try to downgrage TWRP to official 3.0.2-3 and install Lineage once again. Maybe that will help.
BTW, I've made first payment today on Mi 5 and it works flawlessly, so many thanks for the patch! [emoji1]
Sent from my MI 5 using Tapatalk
So, completely clean flash today. I wiped everything, including formatting my entire data partition.
Still failing... still trying...
You must do something wrong, but I don't know what exactly. Did you try to downgrade your TWRP version to official? Can you upload screenshot from TWRP after applying the patch?
Sent from my MI 5 using Tapatalk
p8pepe said:
You must do something wrong, but I don't know what exactly. Did you try to downgrade your TWRP version to official? Can you upload screenshot from TWRP after applying the patch?
Sent from my MI 5 using Tapatalk
Click to expand...
Click to collapse
No. The only users I know who have it working are using TWRP 3.0.3 as well. I don't want to downgrade it.
My patch install dialogue all looks good, but nevermind. I wasted a day on this. Can't afford any more time, so I've restored my backup.
Maybe I'll try another time.
I have TWRP 3.0.2-3 and Android Pay is working fine. I've advised you to temporarily downgrade to official, because 3.0.3 is not perfect yet. Personally I had major problem with booting on encrypted device so I had to do that. You can upgrade again to 3.0.3 at any time, but it's your choice.
Regards!
Sent from my MI 5 using Tapatalk
AaronWhiting said:
So, completely clean flash today. I wiped everything, including formatting my entire data partition.
Still failing... still trying...
Click to expand...
Click to collapse
I've heard stories of people who had root left after a factory reset. Maybe try to re-flash SU uninstall zip? And if you ever installed magisk then flash magisk uninstall zip too... Just to make sure 100% there is no traces of root left.
Btw you are flashing the whole safetynetpass zip not just the .img right?
I'm running out of ideas...
AfouToPatisa said:
I've heard stories of people who had root left after a factory reset. Maybe try to re-flash SU uninstall zip? And if you ever installed magisk then flash magisk uninstall zip too... Just to make sure 100% there is no traces of root left.
Btw you are flashing the whole safetynetpass zip not just the .img right?
I'm running out of ideas...
Click to expand...
Click to collapse
Its ok. I'm over it.
I definitely didn't have root. I'm sure that wasn't the problem.
I even tried it with super clean install. No gapps, no other apps restored, just one to check safety net.
Thanks anyway. I'd still rather carry a credit card than go back to MIUI or waste more time trying.
Me too...
I tried that patch on my Mi5 32GB running RR v5.8.1 after unrooting it and found the device in a bootloop. Just like @AaronWhiting, I'm also flashing from TWRP v3.0.3 stable (but unofficial). Now that would be an entirely new case in itself (since he didn't have any bootloop), but I don't think RR could be an issue since it is also LOS-based, and in fact, I used the 'addonsu-remove-arm64-signed.zip' from LOS extras section to unroot the ROM (RR has built-in root enabled by default) and it worked. Just wanted to ask you guys @p8pepe and @AfouToPatisa , what setup did you have to get a positive result, like say the LOS/other ROM version on which you flashed the safetynetpass zip, device encryption state, and of course the TWRP version as well? Though I understand that you @AaronWhiting have stopped trying to get this thing working, I request you to post your device state as well.
As for me, I am presently on RR v5.8.1 official, GApps micro, no encryption and TWRP 3.0.3. Please add any other important parameter that I may have missed. Let us see if we can solve this out...:fingers-crossed:
Hey,
I have official TWRP 3.0.2-3, LOS 20170131 (clean install - no experimental migration used), opengapps nano. The device is encrypted.
I also had bootloops on TWRP 3.0.3 (probably due to encryption), so downgraded to official.
Sent from my MI 5 using Tapatalk
I'm also using TWRP 3.0.3 & LOS 20170131. Ext partitions all around. Nothing encrypted.
I have been with CM and now LOS since early days of Mi5. Used experimental migration to LOS originally, but went straight to latest version when I did the recent clean flash.
I suspect it's something to do with Bootloader / boot partition but don't have the know-how to troubleshoot further.
I sent @kyasu a PM asking him to check out this thread and help if he can since its his mod were talking about and he'll have the expertise, but haven't heard back yet.
---------- Post added at 11:36 AM ---------- Previous post was at 11:33 AM ----------
Also, I'm surprised about your troubles with encryption on 3.0.3 @p8pepe since it was specifically meant to FIX those issues.
Hi everyone, proud new owner of a Blu R1 HD here. I've been loving the phone ever since I got it. I flashed TWRP, installed the latest version of systemless root and xposed and was a happy camper. But I stupidly wanted more and started messing around with Magisk and trying to get that to work. I didn't back up my stock boot.img like I was supposed to, so after some failed attempts at installing Magisk (and its new MagiskSU) and some bad attempts at uninstalling SuperSU I just flashed the stock boot.img to the device over via fastboot. I then reflashed the latest versions of SuperSU and Xposed, but for whatever reason, my 4G data won't connect at all. I didn't touch any of the settings and I definitely know it isn't a carrier or plan issue. Does flashing the stock boot.img mess with stuff like this? I'm not all that acquainted with this stuff aside from basic flashing and Rom stuff, so I don't really know what could be going on. Literally everything is working just fine except my data... Any ideas? Thanks in advance!
tiduscrying said:
Hi everyone, proud new owner of a Blu R1 HD here. I've been loving the phone ever since I got it. I flashed TWRP, installed the latest version of systemless root and xposed and was a happy camper. But I stupidly wanted more and started messing around with Magisk and trying to get that to work. I didn't back up my stock boot.img like I was supposed to, so after some failed attempts at installing Magisk (and its new MagiskSU) and some bad attempts at uninstalling SuperSU I just flashed the stock boot.img to the device over via fastboot. I then reflashed the latest versions of SuperSU and Xposed, but for whatever reason, my 4G data won't connect at all. I didn't touch any of the settings and I definitely know it isn't a carrier or plan issue. Does flashing the stock boot.img mess with stuff like this? I'm not all that acquainted with this stuff aside from basic flashing and Rom stuff, so I don't really know what could be going on. Literally everything is working just fine except my data... Any ideas? Thanks in advance!
Click to expand...
Click to collapse
What boot.img did you flash? You didn't back up yours.
Amazon version and oem should have been the same ,(blu only released one version of source) but v7.4.2 and v17 both updated the configuration to include band 12 and volte. So if you are on older version of rom and flashed newer boot , maybe thats the reason.
mrmazak said:
What boot.img did you flash? You didn't back up yours.
Amazon version and oem should have been the same ,(blu only released one version of source) but v7.4.2 and v17 both updated the configuration to include band 12 and volte. So if you are on older version of rom and flashed newer boot , maybe thats the reason.
Click to expand...
Click to collapse
My phone came out of the box with version 6.1, so i was able to flash the modified stock update from here that updates the phone from 6.1 all the way to 7.4.2. I took the boot.img from the vanilla 6.1 prime update and flashed it, so that is probably what the issue is. I assume the next step would be to flash the boot.img from the 7.4.2 version, but I can't seem to find a normal version of the v.7.4.2 update that I can just take the boot.img from (unless I can take it from one of these flashable zips?). If it helps, here is a screenshot of my system info which has all the version numbers and whatnot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EDIT: Okay, so I flashed the boot.img from a slightly modified zip of the 7.4.2 update (from here) and thankfully, everything is working fine now. 4G LTE is working swimmingly and I feel like a moron. Lesson learned. Kids, make your backups!
Well, now here is another weird issue. The 4G LTE data is working perfectly fine and speedy as ever, but MMS messages are not being received or sent for whatever reason now. I've already manually entered the correct APN settings and reset them as well to no avail. Any suggestions on this? I've also tried some other SMS apps (such as Pulse) and cleared Messenger's cache and data settings, but that all seems like it did nothing.
Edit: Well, I just flashed the modified 7.4.2 rom that's from the Rom's section of the Blu R1 HD board and MMS is working again. Looks like something other than the boot.img was messed up or something. I did a dirty flash so luckily my roms are in tact.
Edit 2: Sigh, I have no idea what's happening. MMS keeps getting screwey whenever I even start playing around with Xposed (more specifically, Gravity Box). I have no idea why this is happening now all of the sudden. A few days ago before I messed with Magisk, Gravity Box wasn't messing with my MMS messages (at least... I don't think it was...).