Related
I get this error while trying to attempt to update to the latest android 5.0 in twrp...
while installing the new zip file it says:
package expects build fingerprint of google/mantaray/manta: 4.4.4/ktu84p/1227136: user/release-keys or google/mantaray/manta:5.0/LRX21P/1570855:user/release-keys; this device has google/mantaray/manta:4.3/JWR66V/737497:user/release-keys
but my nexus 10 is already on 4.4.4
Your build.prop isn't standard, get the original one, or just use the factory image to update.
Rusty! said:
Your build.prop isn't standard, get the original one, or just use the factory image to update.
Click to expand...
Click to collapse
what i need to install to correct his to the correct build.prop of 4.4.4?
ps. my last 4.4.4 was updated directly OTA..
Just download the 5.0 factory image, remove -w from the flash-all script and it will update you. Less dicking around that way.
inspiron41 said:
I get this error while trying to attempt to update to the latest android 5.0 in twrp...
while installing the new zip file it says:
package expects build fingerprint of google/mantaray/manta: 4.4.4/ktu84p/1227136: user/release-keys or google/mantaray/manta:5.0/LRX21P/1570855:user/release-keys; this device has google/mantaray/manta:4.3/JWR66V/737497:user/release-keys
but my nexus 10 is already on 4.4.4
Click to expand...
Click to collapse
Exactly the same here when flashing OTA via TWRP.
The build.prop file hasn't been modified as far as I know.
Where/how to get the file please?
CBers said:
Exactly the same here when flashing OTA via TWRP.
The build.prop file hasn't been modified as far as I know.
Where/how to get the file please?
Click to expand...
Click to collapse
I found the best way around this is to install the factory nexus 10 lollipop version. It's actually quite easy or even easier than the OTA method. Just make sure you delete the -w from the .bat file to keep all your data. It worked perfectly for me.
Sent from my Nexus 5 using XDA Free mobile app
inspiron41 said:
I found the best way around this is to install the factory nexus 10 lollipop version. It's actually quite easy or even easier than the OTA method. Just make sure you delete the -w from the .bat file to keep all your data. It worked perfectly for me.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks inspiron41 - I'll give it a go at the weekend.
Which file is the -w in please?
CBers said:
Thanks inspiron41 - I'll give it a go at the weekend.
Which file is the -w in please?
Click to expand...
Click to collapse
Go to this website:
http://www.androidpolice.com/2013/1...riants-of-nexus-7-2012-and-2013-and-nexus-10/
It has detail instruction and jump down to step 3 regarding to -w
Sent from my Nexus 5 using XDA Free mobile app
I was having the same issue as the OP. So after reading this thread, I've performed the following:
Downloaded Android 5.0 factory image from: https://developers.google.com/android/nexus/images
Followed the instructions at this site, AND MADE SURE TO REMOVE '-w' AS INSTRUCTED, TO PRESERVE DATA: http://www.androidpolice.com/2013/1...riants-of-nexus-7-2012-and-2013-and-nexus-10/
It was pretty easy. I've been waiting about 30 minutes looking at the boot graphic. Hope it turns out OK. But it is easier than playing with the OTA.
After being stuck in a bootloop, I had to factory reset and now all is well.
Sent from my HTC One using Tapatalk
Darnell_Chat_TN said:
After being stuck in a bootloop, I had to factory reset and now all is well.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
...i've been having the same issue since the 5.0.0 update.
I even had to perform a total wipe to get 5.0.0 onto my N10, and even after that I still have a bad signature on my tablet. Now the problem is back installing 5.0.2 OTA, and I do not want to wipe everything again. So please where is that build.prop file, and how do I fix it? or rather, what the eff has gone wrong here, why, and who's responsible for unbreaking it?
[Lemmy] said:
...i've been having the same issue since the 5.0.0 update.
I even had to perform a total wipe to get 5.0.0 onto my N10, and even after that I still have a bad signature on my tablet. Now the problem is back installing 5.0.2 OTA, and I do not want to wipe everything again. So please where is that build.prop file, and how do I fix it? or rather, what the eff has gone wrong here, why, and who's responsible for unbreaking it?
Click to expand...
Click to collapse
Yea, I flashed the 5.0.1 factory image later. Now, I tried to flash the 5.0.2 OTA and it said it saw a 5.0.1 signature and was expecting 5.0.1, or something of that sort. It's basically the same issue all over again... No issues flashing 5.0.2 to my kids' N7s that are 100% stock.
My N10 is unlocked and rooted. There must be something in the customizations that cause this issue.
Darnell_Chat_TN said:
Yea, I flashed the 5.0.1 factory image later. Now, I tried to flash the 5.0.2 OTA and it said it saw a 5.0.1 signature and was expecting 5.0.1, or something of that sort. It's basically the same issue all over again... No issues flashing 5.0.2 to my kids' N7s that are 100% stock.
My N10 is unlocked and rooted. There must be something in the customizations that cause this issue.
Click to expand...
Click to collapse
and again, trying to flash the 5.1 OTA and it says there is a 4.4.2 signature so it wont install... but I have re-flashed the stock image several times by now. I just do not get it.
[Lemmy] said:
and again, trying to flash the 5.1 OTA and it says there is a 4.4.2 signature so it wont install... but I have re-flashed the stock image several times by now. I just do not get it.
Click to expand...
Click to collapse
Why not just update using the 5.1 factory image? I run unlocked stock/rooted on my N10, and that's the method I always use to update. Would also do it this way on my N5 and now N6. Just fastboot flash all the images from the factory image manually (READ: EXCEPT USERDATA). You can also skip flashing the recovery if you run a custom recovery. However, for the sake of completion, I include flashing the stock recovery. Then I let it boot up normally. Then I'll boot back into the bootloader and flash TWRP and flash SuperSU. Updating this way is easier for me since I don't have to worry about the OTA failing due to customizations I may have made to the system (especially now with the new way Android updates after 5.0).
I've already had to upgrade my tablet by flashing stock for the last three upgrades, and every single time I ended up havnig to wipe the tablet clean and install and configure everything from scratch. I'm still hoping that at some point I wouldn't have to do that anymore...
---------- Post added at 08:57 AM ---------- Previous post was at 08:49 AM ----------
could this all be because my tablet is rooted and has CWM recovery installed?
[Lemmy] said:
I've already had to upgrade my tablet by flashing stock for the last three upgrades, and every single time I ended up havnig to wipe the tablet clean and install and configure everything from scratch. I'm still hoping that at some point I wouldn't have to do that anymore...
---------- Post added at 08:57 AM ---------- Previous post was at 08:49 AM ----------
could this all be because my tablet is rooted and has CWM recovery installed?
Click to expand...
Click to collapse
That's weird. I can't remember the last time I had issues using the stock images, and most people seem to be okay doing it. How are you flashing it? I follow Method 2 from this OP: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. I just skip the command that flashes userdata, and it always works. I always flash the new cache image because when I would just erase it, it would be forever stuck in the bootanimation.
Before 5.0, being rooted didn't affect upgrading via OTA. Now, however, any little modification to the system (including being rooted) will cause the OTA to fail everytime. Also using a custom recovery like CWM will cause it to fail. So if you really want to go the OTA route, the least you would have to do is completely unroot (inside the SuperSU app itself) and flash the stock recovery. If you've uninstalled any system apps, you have to reinstall them or it will also fail.
charesa39 said:
That's weird. I can't remember the last time I had issues using the stock images, and most people seem to be okay doing it. How are you flashing it? I follow Method 2 from this OP: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. I just skip the command that flashes userdata, and it always works. I always flash the new cache image because when I would just erase it, it would be forever stuck in the bootanimation.
Before 5.0, being rooted didn't affect upgrading via OTA. Now, however, any little modification to the system (including being rooted) will cause the OTA to fail everytime. Also using a custom recovery like CWM will cause it to fail. So if you really want to go the OTA route, the least you would have to do is completely unroot (inside the SuperSU app itself) and flash the stock recovery. If you've uninstalled any system apps, you have to reinstall them or it will also fail.
Click to expand...
Click to collapse
My N10 is with stock ROM 5.0.1 and stock recovery but rooted with unlocked bootloader (and custom launcher). I have two questions:
1) I can unroot it through SuperSU. Do I have to switch back to the stock launcher before trying the OTA installation of 5.1?
2) I remember last time I could gain root by simply installing SuperSU. After flashing the 5.1 factory image, can I still get root this same way, or do I have to install, for example, TWRP and then flash SuperSU?
Thanks!
mj56gt said:
My N10 is with stock ROM 5.0.1 and stock recovery but rooted with unlocked bootloader (and custom launcher). I have two questions:
1) I can unroot it through SuperSU. Do I have to switch back to the stock launcher before trying the OTA installation of 5.1?
2) I remember last time I could gain root by simply installing SuperSU. After flashing the 5.1 factory image, can I still get root this same way, or do I have to install, for example, TWRP and then flash SuperSU?
Thanks!
Click to expand...
Click to collapse
1) No, you can keep whichever launcher you are using whether it be Trebuchet, Google Now Launcher, Nova, etc. since it's more of just an app and not a system mod.
2) As far as I know (or thought), you've always had to flash SuperSU using a custom recovery unless your ROM already came pre-rooted. In which case, all you would have to do is install SuperSU from the Play Store. But to answer your question, after flashing the factory image, you would have to flash a custom recovery like TWRP and then flash SuperSU using said custom recovery. However, that's not complicated at all. After flashing the factory image, it just takes like another 5 minutes to flash TWRP, boot into it, flash SuperSU, boot into the OS, verify root status, then power off, boot back into the bootloader and flash the stock recovery (if you don't want to keep the custom recovery). While you're at it, after flashing SuperSU, why not flash the Translucent Nav/Status Bar Mod found here: http://forum.xda-developers.com/showthread.php?t=2771708 provided by @hanspampel. He's done a great service for us. It's the easiest and best mod for the stock N10 right now that restores the translucent decor that Google decided to disable on our device. I flashed it on my N10 after upgrading to 5.1 and it works flawlessly. But that's just a suggestion.
charesa39 said:
1) No, you can keep whichever launcher you are using whether it be Trebuchet, Google Now Launcher, Nova, etc. since it's more of just an app and not a system mod.
2) As far as I know (or thought), you've always had to flash SuperSU using a custom recovery unless your ROM already came pre-rooted. In which case, all you would have to do is install SuperSU from the Play Store. But to answer your question, after flashing the factory image, you would have to flash a custom recovery like TWRP and then flash SuperSU using said custom recovery. However, that's not complicated at all. After flashing the factory image, it just takes like another 5 minutes to flash TWRP, boot into it, flash SuperSU, boot into the OS, verify root status, then power off, boot back into the bootloader and flash the stock recovery (if you don't want to keep the custom recovery). While you're at it, after flashing SuperSU, why not flash the Translucent Nav/Status Bar Mod found here: http://forum.xda-developers.com/showthread.php?t=2771708 provided by @hanspampel. He's done a great service for us. It's the easiest and best mod for the stock N10 right now that restores the translucent decor that Google decided to disable on our device. I flashed it on my N10 after upgrading to 5.1 and it works flawlessly. But that's just a suggestion.
Click to expand...
Click to collapse
Thanks a lot for the suggestions! Have a wonderful weekend...
Never mind
So I recieved the notification that the 5.0.2 update was ready to install on my tablet. My tablet is ROOTED but that is all, still stock, I only root to use ad away. I get an error trying to install it OTA. How can I install the update, without having to wipe all my data? Sorry, I am very new to this stuff
viper2ko said:
So I recieved the notification that the 5.0.2 update was ready to install on my tablet. My tablet is ROOTED but that is all, still stock, I only root to use ad away. I get an error trying to install it OTA. How can I install the update, without having to wipe all my data? Sorry, I am very new to this stuff
Click to expand...
Click to collapse
No go on root. Your system partition has to be pristine. (Technically you can add files, but the ones that came with it have to be unchanged) Just undo any changes you have made and unroot and the OTA should work.
So if I get this right, OTA breaks also when recovery is stock, but supersu installed, modified hosts and gps.conf file
jshamlet said:
No go on root. Your system partition has to be pristine. (Technically you can add files, but the ones that came with it have to be unchanged) Just undo any changes you have made and unroot and the OTA should work.
Click to expand...
Click to collapse
Only changed I have made are installing ad away
viper2ko said:
Only changed I have made are installing ad away
Click to expand...
Click to collapse
The HOSTS file came with the stock image. It counts, unfortunately. (I'm also an Adaway user)
Modify /system, you don't OTA. Period.
Just download the Nexus image and flash just system.img, not the batch file.
Can I flash the system.img in TWRP or do I need to flash the stock recovery?
And will this upgrade me from 5.0.1 to 5.0.2 without losing anything except for root?
Thanks!
^You flash the system image with fastboot. Run: fastboot flash system system.img
You'll keep data just have to reflash the su zip in twrp.
yosmokinman said:
^You flash the system image with fastboot. Run: fastboot flash system system.img
You'll keep data just have to reflash the su zip in twrp.
Click to expand...
Click to collapse
Thanks for the info. Just had this problem myself and was trying to figure out what to do. This must be a 5.x problem? I've never had this problem on 4.x as long as I had the stock recovery installed. Just had to re-root after. Guess I'm off to download the factory images since it won't even show an update available after erroring out. It definitely still shows 5.01 as being the version I'm on.
flyinion said:
Thanks for the info. Just had this problem myself and was trying to figure out what to do. This must be a 5.x problem? I've never had this problem on 4.x as long as I had the stock recovery installed. Just had to re-root after. Guess I'm off to download the factory images since it won't even show an update available after erroring out. It definitely still shows 5.01 as being the version I'm on.
Click to expand...
Click to collapse
Just download Scrosler's Factory Stock Rooted Rom 5.0.2 in the Android Development section and install via TWRP over the top of 5.0.1. No need for a fresh install.
magnumlove said:
Just download Scrosler's Factory Stock Rooted Rom 5.0.2 in the Android Development section and install via TWRP over the top of 5.0.1. No need for a fresh install.
Click to expand...
Click to collapse
Oh I wasn't going to do a fresh install (i.e. wiping everything), just flash that system.img or modify the batch file to remove the "-w" flag and just run that. I'm wary of running 3rd party ROMs now after I couldn't play movies through Play Movies that were downloaded to the device instead of streamed. Something to do with copy protection I guess
It isn't a "3rd party ROM," just a flashable version of 5.0.2. If you flash using TWRP, just don't have it wipe anything. I flashed his 5.0.1 flashable ROM over 4.4.4 (after updating my bootloader) and didn't lose anything.
Telyx said:
It isn't a "3rd party ROM," just a flashable version of 5.0.2. If you flash using TWRP, just don't have it wipe anything. I flashed his 5.0.1 flashable ROM over 4.4.4 (after updating my bootloader) and didn't lose anything.
Click to expand...
Click to collapse
Assuming this was in reply to me? I'm not worried about losing anything. I've done the whole back it up and wipe between ROMs a ton on my OG Droid and Galaxy Nexus. In this case it's a worry that Play Movies for instance will detect that it is not a stock ROM/image and will disallow playing downloaded versions of movies in the app. I.e. you can download vs. stream for offline playback. I nearly found out the hard way (night before leaving on a vacation) that I couldn't play downloaded versions (it will download but not play them) when I for instance installed AOKP to my Nexus 7. As best I could tell from a bunch of Googling, it's something to do with copy protection.
It was, but I didn't know your experience level. I guess what I wanted to say is that scrosler's stock rooted ROM is exactly that; once it's on the tablet it isn't any different from rooting the OTA or factory image. It's just flashable via recovery instead of having to use fastboot or flash-all.bat.
Telyx said:
It was, but I didn't know your experience level. I guess what I wanted to say is that scrosler's stock rooted ROM is exactly that; once it's on the tablet it isn't any different from rooting the OTA or factory image. It's just flashable via recovery instead of having to use fastboot or flash-all.bat.
Click to expand...
Click to collapse
Ah ok. Well, I ended up using fastboot to flash the system.img last night and looks like I'm good to go. I tried unrooting (SuperSU remove root function) and changing betterbatterystats to a non-system app first but the OTA still failed. Yeah I learned how to use the basic adb/fastboot stuff when I got my Galaxy Nexus and again with the N7. I figured that way if I totally broke something I'd know how to fix it, and all the fancy tools weren't around when the GNex first came out (at least I don't think they were).
I dirty flashed scrosler's 5.0.1 ROM when I got the 5.0.1 OTA notification, but when the 5.0.2 factory image was posted I fastboot flashed the system.img from that and rerooted. Naturally, less than half a day or so later, scrosler posted his 5.0.2.
So for someone that's not really too experience with fastboot, could someone post a step by step?
Where would I get the system.img?
Check the sticky threads for guides. Read and reread then get started on setting up the Android SDK. Once complete, type in the commands letter for letter.
I was wondering how i can get the new update for the march update. I just unlocked my bootloader and got TWRP. My current OS is the stock android with the february security update.
Im tried flashing the OTA but it keeps failing. Im used to the TWRP on the oneplus two and im confused on how to get the newest update.
Please help me. Thank you
LifeOfNexus said:
I was wondering how i can get the new update for the march update. I just unlocked my bootloader and got TWRP. My current OS is the stock android with the february security update.
Im tried flashing the OTA but it keeps failing. Im used to the TWRP on the oneplus two and im confused on how to get the newest update.
Please help me. Thank you
Click to expand...
Click to collapse
You can't flash an OTA with TWRP. You need to flash the factory images with fastboot, it's all in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Heisenberg said:
You can't flash an OTA with TWRP. You need to flash the factory images with fastboot, it's all in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
but is this going to delete data and applications
sunandoghosh said:
but is this going to delete data and applications
Click to expand...
Click to collapse
No if you read the guide carefully. It states how to flash everything WITHOUT losing any data or applications.
Heisenberg said:
You can't flash an OTA with TWRP. You need to flash the factory images with fastboot, it's all in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
This guy has lots of great advise. I always see him giving great advise all over XDA. fastboot and adb are the icing on the cake for nexus devices. ?
Sent from my Nexus 6P using Tapatalk
sunandoghosh said:
but is this going to delete data and applications
Click to expand...
Click to collapse
No it doesn't, did you read my guide at all? It probably isn't the best idea to be giving out false information.
Has anybody tried to update with this app? https://play.google.com/store/apps/details?id=eu.chainfire.flash&hl=nl I would like know if this works good.
I'm in the same boat as OP
Should I flash MMB29V or MHC19I and do I need to update my twrp ?
I'm on stock MMB29Q with ROOT with twrp 3.0.0.0
Thanks guys any help would be super appreciated
David522d said:
I'm in the same boat as OP
Should I flash MMB29V or MHC19I and do I need to update my twrp ?
I'm on stock MMB29Q with ROOT with twrp 3.0.0.0
Thanks guys any help would be super appreciated
Click to expand...
Click to collapse
Go for the latest, which is MHC19I, you'll need to update to TWRP 3.0.0-1 though.
Heisenberg said:
Go for the latest, which is MHC19I, you'll need to update to TWRP 3.0.0-1 though.
Click to expand...
Click to collapse
Do I flash the newest twrp or does that go thru fastboot as well?
And is there any radio or bootloader that I need to update as well?
Thanks!
David522d said:
Do I flash the newest twrp or does that go thru fastboot as well?
And is there any radio or bootloader that I need to update as well?
Thanks!
Click to expand...
Click to collapse
All through fastboot, the radio and bootloader will be updated when you flash the factory images.
wietse1988 said:
Has anybody tried to update with this app? https://play.google.com/store/apps/details?id=eu.chainfire.flash&hl=nl I would like know if this works good.
Click to expand...
Click to collapse
I used FlashFire to update to March security patch; Only flashed
boot
system
vendor
Worked perfectly.
dratsablive said:
I used FlashFire to update to March security patch; Only flashed
boot
system
vendor
Worked perfectly.
Click to expand...
Click to collapse
Did you update your twrp prior?
I'll probably just do the fastboot method. But if this easier. Easier is always better
David522d said:
Did you update your twrp prior?
I'll probably just do the fastboot method. But if this easier. Easier is always better
Click to expand...
Click to collapse
I had to update TWRP afterwards.
I Flashed twrp and then did the newest factory image and kept my custom recovery and now it started up in a boot-loop
Please someone help me!
Edit
I cleared the cache in recovery and it booted
Why am I getting a "Your Device is Corrupt. It can't be trusted and may not work properly."
I should start this off by saying that i have no idea how to root a device and i am now currently aware of how stupid my actions were.
I've searched the forums for about 2 hours now and i've yet to find a solution to this problem which is stressing me out like you wouldn't believe.
about i year ago i tried to root my Moto X Pure edition but i failed miserably so i returned to stock and lived without. This morning i decided i would try to root again but it isn't going so well.
I followed this guide: http://forum.xda-developers.com/moto-x-style/general/root-moto-x-style-xt1572-br-marshmallow-t3259380 And everything worked fine until i noticed that my wifi wasn't working.
I then decided to flash back to the original boot image which i found from this site: http://androiding.how/systemless-root-moto-x-style-marshmallow-mph24-49-18/ But my wifi still refuses to turn back on
By now I'm a bit stressed out and not thinking straight. I then recalled that device encryption can screw with the rooting process so i decided to factory reset (how stupid can i get.)
So now im sitting at the welcome screen and my XT1575 cant find a wifi network so im going to have to restore my device over cellular data.
What do i do!?!?!?!?!!?!?
EDIT: i just realized the first link i posted was for the XT1572. I feel so stupid. how do i restore original functionality to my device?
I have had this issue before but on a Moto X Style (XT1572). You need to flash the modem again through fastboot/ADB. You first need to download the full stock firmware and extract it on a PC. Reboot your phone into bootloader mode and run the following command through command prompt/terminal:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
You may need to do this twice as it doesn't work always first time. Refer to this post for more information:
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
HTH,
Ooms
dj_ooms said:
I have had this issue before but on a Moto X Style (XT1572). You need to flash the modem again through fastboot/ADB. You first need to download the full stock firmware and extract it on a PC. Reboot your phone into bootloader mode and run the following command through command prompt/terminal:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
You may need to do this twice as it doesn't work always first time. Refer to this post for more information:
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
HTH,
Ooms
Click to expand...
Click to collapse
I've learned a lot in the past two hours. I did try to reflash the modem multiple times with multiple different files without any success. I don't think the method i was following works for XT1575 specifically.
I am currently back on stock with wifi working. I like the idea of a systemless root, but i couldn't find a method that works for the Pure. So i guess i will continue to run stock until i get a new phone (that might be a while.)
UC_Nightmare said:
I've learned a lot in the past two hours. I did try to reflash the modem multiple times with multiple different files without any success. I don't think the method i was following works for XT1575 specifically.
I am currently back on stock with wifi working. I like the idea of a systemless root, but i couldn't find a method that works for the Pure. So i guess i will continue to run stock until i get a new phone (that might be a while.)
Click to expand...
Click to collapse
Glad you managed to sort out your WiFi.
If you are on stock ROM but have tried root, it means you already have an unlocked bootloader. You could always try and flash TWRP and then flash a pre-rooted stock ROM from here:
[ROM] Flashable Stock/Rooted X1575 6.0 MPHS24.49-18-4 (May security update)
This will give you what you are after minus the stock recovery. You could then just reflash the stock recovery using fastboot/ADB:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Just download the full stock of the firmware version you flashed through TWRP and then extract and flash the respective version recovery from here:
[FiRMWARE] XT1575 PuRE FiRMWARE aNd STuFF
You should then be completely stock with root.
I tried systemless root on my XT1572 and didn't get on with it. Kept having issues so just went with full root and am happy with my phone as it is; stock 6.0.1 with full root and a few stock apps removed that I don't use/need.
HTH,
Ooms
dj_ooms said:
Glad you managed to sort out your WiFi.
If you are on stock ROM but have tried root, it means you already have an unlocked bootloader. You could always try and flash TWRP and then flash a pre-rooted stock ROM from here:
[ROM] Flashable Stock/Rooted X1575 6.0 MPHS24.49-18-4 (May security update)
This will give you what you are after minus the stock recovery. You could then just reflash the stock recovery using fastboot/ADB:
Just download the full stock of the firmware version you flashed through TWRP and then extract and flash the respective version recovery from here:
[FiRMWARE] XT1575 PuRE FiRMWARE aNd STuFF
You should then be completely stock with root.
I tried systemless root on my XT1572 and didn't get on with it. Kept having issues so just went with full root and am happy with my phone as it is; stock 6.0.1 with full root and a few stock apps removed that I don't use/need.
HTH,
Ooms
Click to expand...
Click to collapse
Thanks for the suggestion. Before I try rooting again though, is there a way to completely backup my phone to my computer without using twrp? its a pain logging into all my app and setting everything up every time i try to root my phone.
UC_Nightmare said:
Thanks for the suggestion. Before I try rooting again though, is there a way to completely backup my phone to my computer without using twrp? its a pain logging into all my app and setting everything up every time i try to root my phone.
Click to expand...
Click to collapse
The only app I am aware of without root is Helium. I haven't tried it personally but I think you need to have an app running on your PC and the phone connected to it. I personally use TWRP with Nandroid Manager and Titanium Backup. These both need root though. You could always make a backup through TWRP prior to flashing the pre-rooted ROM, then flash the ROM as always recommended. If you run into issues, just restore the backup through TWRP, then flash the stock recovery back through fastboot/ADB to be backup to your original state.
HTH,
Ooms
dj_ooms said:
Glad you managed to sort out your WiFi.
If you are on stock ROM but have tried root, it means you already have an unlocked bootloader. You could always try and flash TWRP and then flash a pre-rooted stock ROM from here:
[ROM] Flashable Stock/Rooted X1575 6.0 MPHS24.49-18-4 (May security update)
This will give you what you are after minus the stock recovery. You could then just reflash the stock recovery using fastboot/ADB:
Just download the full stock of the firmware version you flashed through TWRP and then extract and flash the respective version recovery from here:
[FiRMWARE] XT1575 PuRE FiRMWARE aNd STuFF
You should then be completely stock with root.
I tried systemless root on my XT1572 and didn't get on with it. Kept having issues so just went with full root and am happy with my phone as it is; stock 6.0.1 with full root and a few stock apps removed that I don't use/need.
HTH,
Ooms
Click to expand...
Click to collapse
Maybe i am missing something but why would i want to flash stock recovery after i flash for example "XT1575 Rooted 6.0 Odexed with May security update" from the first link you provided?
UC_Nightmare said:
Maybe i am missing something but why would i want to flash stock recovery after i flash for example "XT1575 Rooted 6.0 Odexed with May security update" from the first link you provided?
Click to expand...
Click to collapse
I think i can answer my own question now. TWRP is a "custom recovery" and after i use TWRP i can flash something over it so that i can be stock. The terminology around these parts is quite confusing
i've gone and ****ed everything up again. I flashed twrp and then tried to install a zip from the first link you provided but my phone refused to unlock
I did a factory reset from within twrp and reinstalled the zip but now my wifi isnt working again.
Is rooting always such a pain in the ass?
UC_Nightmare said:
i've gone and ****ed everything up again. I flashed twrp and then tried to install a zip from the first link you provided but my phone refused to unlock
I did a factory reset from within twrp and reinstalled the zip but now my wifi isnt working again.
Is rooting always such a pain in the ass?
Click to expand...
Click to collapse
When rooting, there is always a risk. I have been flashing phones for over 10 years and it is always a learning experience. Even now i have occasionally done something and thought I've completely mucked up my phone. You just need to make sure you follow exactly what is stated as the procedure and if you run into problems, there is always someone at hand to help in this great forum.
Out of curiosity, did you follow the standard procedure for installing a new ROM? You will lose all data doing the standard procedure but can restore most stuff from your Nandroid backup. The steps I always do is:
1. Make a backup
2. Wipe data, system, dalvik/art and cache partitions
3. Flash your ROM
4. Wipe dalvik/art and cache again
5. Reboot
Click to expand...
Click to collapse
That is the standard recommended procedure for flashing all ROMs in TWRP. I have an EU XT1572 and have successfully used this ROM on my phone. The ROM contains everything you need including the modem. The modem is for the US XT1575 but worked fine on my phone. For sanities sake, I flashed the EU modem after and still had everything working.
Just another point, your phone needs to have been updated to Marshmallow before you can run one of these ROMs. If you are on Lollipop you may run into issues, especially from a radios perspective.
Another thing to point out is that all ROMs are started that you flash at your own risk. Developers will not be held responsible for anything going wrong. As long as you follow the guides and don't flash a ROM for a completely different device, you shouldn't run into any issues and more often then not can bring your phone back to a functional state if you do.
HTH,
Ooms
Flash twrp
Make backup
Flash su 2.62-3
Done.
Or...
1. Flash the factory image
2. Flash TWRP
3. Flash this attachment in TWRP, which will force install SuperSU 2.78 SR-1 systemless-ly. I've shared and posted about it before in this thread.
Nothing's changed with the attached zip here, except it has the latest version of SuperSU included as of this post.
I take no credit for any of this. Monkey saw, monkey did. MAKE SURE YOU FULLY READ THE ORIGINAL POSTS AS THE MONKEY MAY HAVE OMITTED SOMETHING. If you are clueless, not good at following instructions, or apprehensive you might want to pass. If you managed to already get unlocked and TWRPed, I imagine you are good to go. Still, if you break your phone, it's on you.
1. Do a TWRP backup.
2. Flash one of the choices here (READ THE ENTIRE THREAD) :
https://forum.xda-developers.com/moto-x-style/development/rom-marshmallow-6-0-september-2016-t3536120
REBOOT.
I went with the Deodexed one. Check out the Mods too. I added Viper.
3. Get Systemless Root back using using the flash-able Script in Post #8 here (READ ALL 1st):
https://forum.xda-developers.com/moto-x-style/general/systemless-root-info-t3373864
3a. Direct Link here:
https://forum.xda-developers.com/attachment.php?attachmentid=3809946&d=1468261256
REBOOT
I was still stock but Rooted with Xposed and I successfully Dirty Flashed. OP still recommends a CLEAN Install. After running the script, the phone came back looking the same. I did lose my custom Boot Animation and Viper so I re-flashed them. I also flashed the latest SU just to be sure i had the latest. Probably makes no difference.
Build now says MPHS24.49-18-8 and security Patch 09/01/2016.
Be sure and thank the OP's for the flash-able Update and the Systemless script.
THANK YOU OP'S,
Monkey
Except people have to understand... this puts you in a potentially precarious position. Your bootloader, radios, and partition table are all from a previous ROM version, but your system and boot/kernel are from the current release. Meaning your stuck on this or other custom ROMs and cannot go back to "pure" stock, at least until there is official full factory firmware release for the September update.
Not saying this isn't a valid way to do it, but it isn't truly getting the update... not completely, so my advice to others is proceed with caution and know the possible consequences, they may or not matter to you.
acejavelin said:
...Meaning your stuck on this or other custom ROMs and cannot go back to "pure" stock, at least until there is official full factory firmware release for the September update.
Not saying this isn't a valid way to do it, but it isn't truly getting the update... not completely, so my advice to others is proceed with caution and know the possible consequences, they may or not matter to you.
Click to expand...
Click to collapse
When you say "cannot go back" does something get flagged where a TWRP system wipe and restore of a backup would not work?
G_Man18 said:
When you say "cannot go back" does something get flagged where a TWRP system wipe and restore of a backup would not work?
Click to expand...
Click to collapse
No... That's fine. I mean you can't flash the full system image via fastboot.
acejavelin said:
No... That's fine. I mean you can't flash the full system image via fastboot.
Click to expand...
Click to collapse
Thanks for the quick response. I am surprised how many people get in trouble when TWRP backups are easy to do and can get you going when you screw up--which does happen to all of us. I post little but do read quite a bit in these forums; most of my questions have already been answered. You say you will nudge people in the right direction, but from what I have seen, no one on here answers as many questions so meticulously as you. Thanks!
acejavelin said:
Except people have to understand... this puts you in a potentially precarious position. Your bootloader, radios, and partition table are all from a previous ROM version, but your system and boot/kernel are from the current release. Meaning your stuck on this or other custom ROMs and cannot go back to "pure" stock, at least until there is official full factory firmware release for the September update.
Not saying this isn't a valid way to do it, but it isn't truly getting the update... not completely, so my advice to others is proceed with caution and know the possible consequences, they may or not matter to you.
Click to expand...
Click to collapse
I just received the notification for this update, is it okay to take it, or is it going to cause issues. I am unlocked and rooted currently running MPHS24.49-18-4. I would restore back to a non-rooted TWRP backup of the same build, then flash back the original recovery image, clear cache and dalvik, and finally flash the update.
Will this work and is It okay to update to this build? Thanks.
robn30 said:
I just received the notification for this update, is it okay to take it, or is it going to cause issues. I am unlocked and rooted currently running MPHS24.49-18-4. I would restore back to a non-rooted TWRP backup of the same build, then flash back the original recovery image, clear cache and dalvik, and finally flash the update.
Will this work and is It okay to update to this build? Thanks.
Click to expand...
Click to collapse
If you return to stock, meaning the /system and /boot partitions and recovery is stock, it should work... how you get there isn't as important. But you can't just "flash" the OTA zip file, not directly... and I am not positive if the stock recovery supports sideloading official ZIPs or not, but you should be able to accept it and let it apply itself. The lock or unlock state of the bootloader isn't relevant.
So most likely it would work fine... but backup first, just in case something goes wrong.
acejavelin said:
If you return to stock, meaning the /system and /boot partitions and recovery is stock, it should work... how you get there isn't as important. But you can't just "flash" the OTA zip file, not directly... and I am not positive if the stock recovery supports sideloading official ZIPs or not, but you should be able to accept it and let it apply itself. The lock or unlock state of the bootloader isn't relevant.
So most likely it would work fine... but backup first, just in case something goes wrong.
Click to expand...
Click to collapse
Backup is running right now, so that will be good to go. With systemless root can I perform a full unroot using SuperSU or is it better to restore the unrooted TWRP backup? Thanks.
robn30 said:
Backup is running right now, so that will be good to go. With systemless root can I perform a full unroot using SuperSU or is it better to restore the unrooted TWRP backup? Thanks.
Click to expand...
Click to collapse
If you are rooted, it means you did something with root, right? So unless you are going to undo everything root and then unroot, better to restore the pre-root backup
acejavelin said:
If you are rooted, it means you did something with root, right? So unless you are going to undo everything root and then unroot, better to restore the pre-root backup
Click to expand...
Click to collapse
Very good, thanks for the advice. Good thing I made an unrooted backup when I updated to the May Security update. I knew that would come in handy eventually.
robn30 said:
Very good, thanks for the advice. Good thing I made an unrooted backup when I updated to the May Security update. I knew that would come in handy eventually.
Click to expand...
Click to collapse
Update went perfectly smooth by restoring back to an unrooted 24.221.4 TWRP backup, then flashing stock recovery, and finally taking the update to 24.221.8. I did perform a wipe off cache and dalvik at least twice during the process.
Sent from my XT1575 using Tapatalk
robn30 said:
Update went perfectly smooth by restoring back to an unrooted 24.221.4 TWRP backup, then flashing stock recovery, and finally taking the update to 24.221.8. I did perform a wipe off cache and dalvik at least twice during the process.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Just to be sure. I ran TWRP from Fastboot in ADB as soon as Unlocked and turned the phone on. So you have confirmed I can then flash Stock recovery and take the "full" Update. Mind providing the link to Stock recovery?
Thanks.
schneid said:
Just to be sure. I ran TWRP from Fastboot in ADB as soon as Unlocked and turned the phone on. So you have confirmed I can then flash Stock recovery and take the "full" Update. Mind providing the link to Stock recovery?
Thanks.
Click to expand...
Click to collapse
Pretty sure there is a post in here somewhere that has a link to the 24.221.4 recovery, but I just used the one in this full firmware download. Just extracted the recovery.img file only and flash it using fastboot. Here is the link.
https://forum.xda-developers.com/showpost.php?p=69103575&postcount=243