Marsmallow 6.0 XT1092 reteu variant -Twrp backup variant - X 2014 General

Unzip the file https://mega.nz/#!GIgwXKIL!fnuIUY7ETilk-758lv8qguUe3QxC7UwJ4rkRmXk0kMs and put the folder to the TWRP backup then restore.This is the clean sistem,no rooted!For root use and flash this zip : SuperSU-v2.52 http://forum.xda-developers.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105

Download the zip once, shows its corrupted. Downloading again.
Sent from my XT1095 using Tapatalk

Thnx. Is this only system and boot? Or something more in it?
Cheers

Only system and boot,nothing more!

likurik said:
Only system and boot,nothing more!
Click to expand...
Click to collapse
When looking in the zip i also saw efs and data backed up?

Boot
System
Data
Cache
Efs
ALL this!

Do you get future OTA's with this?

Yes of course! For the future update just i will be flash stock recovery image and update via OTA,.This is the stock marsmallow backup ,nothing touch it

It this a soak test backup or the final one?
Sent from my XT1092 using Tapatalk

Using this method, I get an RPC error once Google Play updates to 6.0.2 that prevents me from downloading any more apps at all. It's quite annoying. Even the 'fix' for it (uninstalling updates, clearing cache, rebooting to recovery & clearing dalvik/cache from there) doesn't fix it permanently

For RPC error the fix is easy!
Go to settings >application > Play Store >storage>Clear Data & Clear Cache.
Go to accounts >Google >Remove account.
Reboot device.
Again Settings>Account >Google >Log In

likurik said:
For RPC error the fix is easy!
Go to settings >application > Play Store >storage>Clear Data & Clear Cache.
Go to accounts >Google >Remove account.
Reboot device.
Again Settings>Account >Google >Log In
Click to expand...
Click to collapse
unfnknblvbl said:
Even the 'fix' for it (uninstalling updates, clearing cache, rebooting to recovery & clearing dalvik/cache from there) doesn't fix it permanently
Click to expand...
Click to collapse
Anyway, I managed to fix it (and very nearly bricked my phone in the process). I originally restored System only, in an attempt to keep my existing data. It didn't work (kept getting an Unknown Play Services error). Then I restored Data in a separate session, and I kept getting the RPC error which would not go away once Play Store updated to 6.0.2 or whatever.
I then did some things which nearly bricked my phone, and just restored the whole archive in one session, which seems to have fixed the issue. Touch wood.

likurik said:
Unzip the file https://mega.nz/#!GIgwXKIL!fnuIUY7ETilk-758lv8qguUe3QxC7UwJ4rkRmXk0kMs and put the folder to the TWRP backup then restore.This is the clean sistem,no rooted!For root use and flash this zip : SuperSU-v2.62-3-20151211162651.zip
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Click to expand...
Click to collapse
is it factory image?

unfnknblvbl said:
Anyway, I managed to fix it
Click to expand...
Click to collapse
No such luck. This is quite annoying, since you can't just go ahead and downgrade back to 5.1 once you've done this
---------- Post added at 10:09 PM ---------- Previous post was at 09:56 PM ----------
reyon6 said:
is it factory image?
Click to expand...
Click to collapse
No it's not. It's a recovery image that somebody (I assume the OP) made of their own install.

[dupe]

Can I flash this? I have an xt1092 and chnaged it to the brazilian model so that I could have the 6.0 update. If I flash this via twrp, will it brick my phone?

Download Link is Broken pls Reupp

Sleeperxr said:
Download Link is Broken pls Reupp
Click to expand...
Click to collapse
https://mega.nz/#!HN4QjJSK!fnuIUY7ETilk-758lv8qguUe3QxC7UwJ4rkRmXk0kMs

likurik said:
https://mega.nz/#!HN4QjJSK!fnuIUY7ETilk-758lv8qguUe3QxC7UwJ4rkRmXk0kMs
Click to expand...
Click to collapse
UK XT1092, flashed this by just
Code:
fastboot boot twrp
and phone signal. Probably caused by me having the US XT1095 modem installed so I flash an old UK modem and after rebooting I have 4G signal.
Booted twrp again and flashed BETA-SuperSU-v2.67-20160121175247.zip and got stuck on bootloader.
Booted twrp again and flash BETA-SuperSU-v2.52.zip and root-boot-6.0-xt1092.zip from http://forum.xda-developers.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105
Seems to be working.

Related

Nexus 4 Won't Update to CM 11 M9

So I saw CM11 M9 was available and tried to update to it but going through the updater failed. So I downloaded the .zip file and them tried to flash it through recovery. This also failed and it said something like "failed to install... factory reset" or something, can't really remember. So then, I created a backup using ROM Manager and then factory reset the phone. It did update to M9, but then I restored my data and it just went back to M8.
Anybody else having the same issue? Is there a fix to this?
Thanks
Nizi123 said:
So I saw CM11 M9 was available and tried to update to it but going through the updater failed. So I downloaded the .zip file and them tried to flash it through recovery. This also failed and it said something like "failed to install... factory reset" or something, can't really remember. So then, I created a backup using ROM Manager and then factory reset the phone. It did update to M9, but then I restored my data and it just went back to M8.
Anybody else having the same issue? Is there a fix to this?
Thanks
Click to expand...
Click to collapse
It could just be a bad download, check the md5 or redownload it! Let me know if it worked
vinc10 said:
It could just be a bad download, check the md5 or redownload it! Let me know if it worked
Click to expand...
Click to collapse
Hi, just tried again after checking md5 (they were the same). Still didn't work. What it said was, "Can't install on top of incompatible data....check package or reset phone data" and then it said "error in.. (status 7)" and showed the location of the .zip file.
Nizi123 said:
Hi, just tried again after checking md5 (they were the same). Still didn't work. What it said was, "Can't install on top of incompatible data....check package or reset phone data" and then it said "error in.. (status 7)" and showed the location of the .zip file.
Click to expand...
Click to collapse
Update your recovery. Or change to twrp. You'll never have errors in twrp Let me know if it works!
vinc10 said:
Update your recovery. Or change to twrp. You'll never have errors in twrp Let me know if it works!
Click to expand...
Click to collapse
I updated CWM through ROM Manager and tried again, didn't work. I also tried updating the script, that led to a Status 6, Installation Aborted.
So I think I will try TWRP now. What would be the best/easiest way to install it over my current CWM recovery?
Nizi123 said:
I updated CWM through ROM Manager and tried again, didn't work. I also tried updating the script, that led to a Status 6, Installation Aborted.
So I think I will try TWRP now. What would be the best/easiest way to install it over my current CWM recovery?
Click to expand...
Click to collapse
Use flashify to download and install. Super easy.
Hit thanks if I helped you
vinc10 said:
Use flashify to download and install. Super easy.
Hit thanks if I helped you
Click to expand...
Click to collapse
Installed TWRP. Still won't flash the zip. Said the same thing as before but adds "Error executing updater binary in zip 'LOCATION OF ZIP'
'Error flashing zip 'LOCATION OF ZIP'
Double check that you don't mount system in twrp. If it still doesn't work Go to CMs website and download the rom again, check md5 and flash. Remember : backup.
vinc10 said:
Double check that you don't mount system in twrp. If it still doesn't work Go to CMs website and download the rom again, check md5 and flash. Rember : backup.
Click to expand...
Click to collapse
Deleted all previous downloads. Re-downloaded CM 11 M9 for mako.
Md5: 100% same
System Mount: NOT checked
Data backed up
Install: FAILED
Factory reset the phone.
Update to M9 through the updater: Success
Restore through recovery: Restored but freaking REVERTED BACK TO M8.....whaa??
Am I doing something wrong? There must be somthing on my phone that is not letting it update since it works after a factory reset. Are there any know apps or other things that do that?
Open cyanogenmod update and select stable relasee
Nizi123 said:
Deleted all previous downloads. Re-downloaded CM 11 M9 for mako.
Md5: 100% same
System Mount: NOT checked
Data backed up
Install: FAILED
Factory reset the phone.
Update to M9 through the updater: Success
Restore through recovery: Restored but freaking REVERTED BACK TO M8.....whaa??
Am I doing something wrong? There must be somthing on my phone that is not letting it update since it works after a factory reset. Are there any know apps or other things that do that?
Click to expand...
Click to collapse
Backup using titanium backup and clean flash m9. Or perhaps a cache clean could do it.
post full recovery log..............
vinc10 said:
Backup using titanium backup and clean flash m9. Or perhaps a cache clean could do it.
Click to expand...
Click to collapse
cache clean didn't work. I tried Titanium backup but I can't figure out a way to quickly restore all the apps and data. It does it one by one and I have to press install for each one. Is there a easier way to restore? I have the backup files on my computer.
opssemnik said:
post full recovery log..............
Click to expand...
Click to collapse
I have attached it. That is the correct file right?
The log is filled with AmazonMP3 stuff. Why is that?
Nizi123 said:
cache clean didn't work. I tried Titanium backup but I can't figure out a way to quickly restore all the apps and data. It does it one by one and I have to press install for each one. Is there a easier way to restore? I have the backup files on my computer.
Click to expand...
Click to collapse
In the TiBu app, go to batch actions>recovery mode>create update.zip. It will create a .zip file with your backups to be flashed from recovery.
Then do a factory reset, reflash your rom, and flash the update.zip to restore your apps.
From my mako
meatboy371 said:
In the TiBu app, go to batch actions>recovery mode>create update.zip. It will create a .zip file with your backups to be flashed from recovery.
Then do a factory reset, reflash your rom, and flash the update.zip to restore your apps.
From my mako
Click to expand...
Click to collapse
Unfortunately I don;t have the pro version of Titanium Backup which is required to make a .zip file. I ended up just restoring the apps through google and then restoring the system data from Ti Backup. Not as good as restoring but I got tired of wiping and restoring and flashing. Thanks for the suggestions.
Everytime I opened Titanium Backup, it said my binary might not work reliably with some apps (screenshot attached) So I installed SuperSu and it prompted me to update my binary, to which I said yes and then clicked "Normal". Then it took a few seconds and said installation failed and reboot and try again. After I reboot, the pop-up that says I need to update never shows up again.
Nizi123 said:
Unfortunately I don;t have the pro version of Titanium Backup which is required to make a .zip file. I ended up just restoring the apps through google and then restoring the system data from Ti Backup. Not as good as restoring but I got tired of wiping and restoring and flashing. Thanks for the suggestions.
Everytime I opened Titanium Backup, it said my binary might not work reliably with some apps (screenshot attached) So I installed SuperSu and it prompted me to update my binary, to which I said yes and then clicked "Normal". Then it took a few seconds and said installation failed and reboot and try again. After I reboot, the pop-up that says I need to update never shows up again.
Click to expand...
Click to collapse
Try to clean install m9 and restore only the data from your backup - should work but i'm not sure.
Ignore the popup.
the recovery log is at /tmp, however it deletes when you reboot, so you should
install zip
wait untill it fails
then pull /tmp/recovery.log
(using aroma fm, or adb or whatever you can use)
vinc10 said:
Try to clean install m9 and restore only the data from your backup - should work but i'm not sure.
Ignore the popup.
Click to expand...
Click to collapse
I restored the system data with TB and my apps were restored automatically so it's pretty much back to normal now. I just have to rearrange my home screen.

[TWRP Backup ]Android 5.1 Brazil soak test [222.21.15] [12-05]

Hi,
This is the latest soak test backup of Android 5.1 Lollipop. verison 222.21.15.
Download:
https://goo.gl/GGx27V
Download latest TWRP for ghost (Moto X)
https://dl.twrp.me/ghost/twrp-2.8.6.0-ghost.img.html
how to restore,
- copy backup folder to your twrp backup folder
- restore backup (system & boot) via twrp
- wipe data, cache & dalvik cache
- reboot
this is a backup file of system and boot partition. can only be restored with TWRP Recovery. it will not touch your modem, bootloader or any other partition of your phone. backup your current system before resotre this twrp backup. if you have any question, just ask here in thread, xda community will response you..
Click to expand...
Click to collapse
backup made for protect you mess your bootloader or modem with installing brazil firmware to your phone.
testet on xt1052 should work with most moto x variants.
Need more help ? look at this thread.
http://forum.xda-developers.com/moto-x/general/how-to-install-5-1-lollipop-moto-x-t3089594
reserved
Is the last update?
I was waiting for this! Thank you very much, @proxuser!
Restored on my xt1053 over the top of the previous build and kept my data intact. Thanks
Did this fix the speakerphone bug?
Stock recovery
Original recovery from 222.12.15 included? I've updated to 222.12.15 from 222.12.7, but the recovery didn't changed, again :/
scht said:
Original recovery from 222.12.15 included? I've updated to 222.12.15 from 222.12.7, but the recovery didn't changed, again :/
Click to expand...
Click to collapse
It's a TWRP backup so no, it isn't included.
How do I root after restoring the backup? I didn't get the option to install SuperSU after the restore.
Nope
athulele said:
Did this fix the speakerphone bug?
Click to expand...
Click to collapse
I installed and the speakerphone bug is still present. Tried clearing app data for Phone and Dialler apps to no avail.
Side note:
Tried restoring from stock firmware in TWRP. Did not work twice. Got stuck on the Moto Blue Water logo. Third time, it worked inexplicably!
Any infos on what is changed?
Improval of battery life would be most interesting to me.
ron_gangte said:
How do I root after restoring the backup? I didn't get the option to install SuperSU after the restore.
Click to expand...
Click to collapse
There is already a su file in the backup but that didn't work for me too. You have to delete the su file at /system/xbin/ manually via twrp file manager. If you reboot twrp will ask you to root again.
Kiristiba said:
There is already a su file in the backup but that didn't work for me too. You have to delete the su file at /system/xbin/ manually via twrp file manager. If you reboot twrp will ask you to root again.
Click to expand...
Click to collapse
Can't find that folder in twrp
Hi, I rebooted my device and it is not switching on any more. Gets stuck at the Blue Water Moto logo. Waited for more than 10 minutes. Tried restore followed by wipe for cache and data again. But still stuck on blue logo. Any help?
johnrangoo said:
Can't find that folder in twrp
Click to expand...
Click to collapse
Did you mount the system partition?
Kiristiba said:
There is already a su file in the backup but that didn't work for me too. You have to delete the su file at /system/xbin/ manually via twrp file manager. If you reboot twrp will ask you to root again.
Click to expand...
Click to collapse
Thanks!
I found an alternate solution. I flashed the SuperSU zip, and it rooted the phone with no hassle. [emoji2]
I tried to restore it on my xt1052, it keeps saying that No partitions selected for restore. What should I do?
In your TWRP backup directory, there should be a folder with the date (2015-05-12--16-05-56_LPA23.12-15), make sure the image files are in this directory.
When I extracted the rar, it was 2015-05-12--16-05-56_LPA23.12-15\2015-05-12--16-05-56_LPA23.12-15\<image files>
it should be 2015-05-12--16-05-56_LPA23.12-15\<image files>
Can I install this from 4.4.4?
Test it. The proximity sensor also not work for active display.
So I back to 4.4.4 again.

TM-535 Stocks on Samsung Logo / Loading Apps after Boot / Important DATA / TWRP Insta

Hi there, i've got a big problem. I flashed recently my sisters school tab with custom recovery (TWRP) to delete the forgotten password, worked well. But afterwards, the school write her an email, that the tab is rooted (Was not rooted, but SU App appears) so i decided to flash the stock recovery back. This also works well on first boot but after cleaning cache, its stocks on Samsung logo. Now i flashed TWRP back and cleaned dalvik cache/cache, on first boot is passes the samsung logo and Andriod os loading apps appears and stucks (i let it run over the night.). So how can i fix this without any data lose, app lose? I cant do a factory reset because of her school config...I dont know which android version is installed.
sabankuru said:
Hi there, i've got a big problem. I flashed recently my sisters school tab with custom recovery (TWRP) to delete the forgotten password, worked well. But afterwards, the school write her an email, that the tab is rooted (Was not rooted, but SU App appears) so i decided to flash the stock recovery back. This also works well on first boot but after cleaning cache, its stocks on Samsung logo. Now i flashed TWRP back and cleaned dalvik cache/cache, on first boot is passes the samsung logo and Andriod os loading apps appears and stucks (i let it run over the night.). So how can i fix this without any data lose, app lose? I cant do a factory reset because of her school config...I dont know which android version is installed.
Click to expand...
Click to collapse
Why do not you just removed Su application?
Maybe better to ask the school you have to do?
yes thats right, but now i cant boot anymore. "Android is Starting" "Optimizing App x of xxx and hang at the end. will official firmware flash with odin erase all the data?
sabankuru said:
yes thats right, but now i cant boot anymore. "Android is Starting" "Optimizing App x of xxx and hang at the end. will official firmware flash with odin erase all the data?
Click to expand...
Click to collapse
No . Ordinary stock firmware without wipe not erase data . It update system files , not data . This called dirty installation . But maybe some bugs with installed apps .
---------- Post added at 11:46 AM ---------- Previous post was at 11:41 AM ----------
You need to do copy your internal memory to PC and to do reflash firmware with all wipes
repey6 said:
No . Ordinary stock firmware without wipe not erase data . It update system files , not data . This called dirty installation . But maybe some bugs with installed apps .
---------- Post added at 11:46 AM ---------- Previous post was at 11:41 AM ----------
You need to do copy your internal memory to PC and to do reflash firmware with all wipes
Click to expand...
Click to collapse
how to restore after clean install all the data and apps? ive done a backup in twrp recovery, can i just restore ond /data after clean install and all the apps and settings will restore? Thx!
sabankuru said:
how to restore after clean install all the data and apps? ive done a backup in twrp recovery, can i just restore ond /data after clean install and all the apps and settings will restore? Thx!
Click to expand...
Click to collapse
Yes! You need flash TWRP again after clean installation and restore your backup . Then to try delete SU-apps and superSU , if it exist
Ok i will let you know...
I installed 4.4.2 with odin, afterwards there was a process error (google play) so i upgraded to 5.0.2 without data lose. Thx!

Just got RMA, can't disable force encryption

Just got my RMA, so of course I instantly unlock, root, and go to disable forced encryption and i keep getting a password error, my only pin i've ever used won't work, so I flashed factory, reset it up, made sure i didn't use a pin or anything, tried again, still asks for a password and won't accept mine. Am I missing something or is the fact they sent me a remanufactured phone screwing me because of the previous users pin?
kickenwing13 said:
Just got my RMA, so of course I instantly unlock, root, and go to disable forced encryption and i keep getting a password error, my only pin i've ever used won't work, so I flashed factory, reset it up, made sure i didn't use a pin or anything, tried again, still asks for a password and won't accept mine. Am I missing something or is the fact they sent me a remanufactured phone screwing me because of the previous users pin?
Click to expand...
Click to collapse
What TWRP version are you using? Are you on the newest 3.03? If not that's more than likely your problem.
murphyjasonc said:
What TWRP version are you using? Are you on the newest 3.03? If not that's more than likely your problem.
Click to expand...
Click to collapse
OMG I'm confident it's 3.02. So I need to update that before I try the decrypting thing. I need to go root, twrp 3.3 then unencrypt ?
Thanks man I wouldn't ahve thought of that .
kickenwing13 said:
OMG I'm confident it's 3.02. So I need to update that before I try the decrypting thing. I need to go root, twrp 3.3 then unencrypt ?
Thanks man I wouldn't ahve thought of that .
Click to expand...
Click to collapse
Just download the updated TWRP from this link. Boot back into recovery and choose flash IMG instead of zip. Install to recovery partition and then reboot. You should be good to go.
http://dl.twrp.me/angler/
murphyjasonc said:
Just download the updated TWRP from this link. Boot back into recovery and choose flash IMG instead of zip. Install to recovery partition and then reboot. You should be good to go.
http://dl.twrp.me/angler/
Click to expand...
Click to collapse
same nonsense. Went from clean, rooted, flashed TWRP 3.03, tried to flash noencrypt kernel and it's asking me for a password I don't have ... . should I try making my own password next time I reflash stock and see if it like overwrites it ?
found something on a N6 thread that says wipe user data and it should work .
kickenwing13 said:
found something on a N6 thread that says wipe user data and it should work .
Click to expand...
Click to collapse
Yeah that will work and shouldn't be an issue backing up everything with a new phone. TWRP should be able to read an encrypted device though as long as you gave it permissions to change system. No kernel will decrypt a device but most do not force encrypt.
---------- Post added at 11:38 PM ---------- Previous post was at 11:37 PM ----------
kickenwing13 said:
same nonsense. Went from clean, rooted, flashed TWRP 3.03, tried to flash noencrypt kernel and it's asking me for a password I don't have ... . should I try making my own password next time I reflash stock and see if it like overwrites it ?
Click to expand...
Click to collapse
Are you by chance trying to restore a backup on your RMA?
kickenwing13 said:
same nonsense. Went from clean, rooted, flashed TWRP 3.03, tried to flash noencrypt kernel and it's asking me for a password I don't have ... . should I try making my own password next time I reflash stock and see if it like overwrites it ?
Click to expand...
Click to collapse
I had a similar problem with TWRP 3.0.3-0 when I tried to restore a backup. It asked for a password, which has never happened before. I couldn't access my backup or any of my data or boot up. I had to restore stock. Clearing user data did nothing.
murphyjasonc said:
Yeah that will work and shouldn't be an issue backing up everything with a new phone. TWRP should be able to read an encrypted device though as long as you gave it permissions to change system. No kernel will decrypt a device but most do not force encrypt.
---------- Post added at 11:38 PM ---------- Previous post was at 11:37 PM ----------
Are you by chance trying to restore a backup on your RMA?
Click to expand...
Click to collapse
I was not . Just trying to disable force encrypt root and get PN back on it . Wiping worked for me. Also on 3.03, but that alone didn't solve, had to wipe . May be because I was using WUGS instead of manually doing it . Not sure, but it worked .
kickenwing13 said:
I was not . Just trying to disable force encrypt root and get PN back on it . Wiping worked for me. Also on 3.03, but that alone didn't solve, had to wipe . May be because I was using WUGS instead of manually doing it . Not sure, but it worked .
Click to expand...
Click to collapse
Hey, I'm running into the same problem after an RMA. I'm currently on stock unrooted 7.1.1 and want to flash custom rom but want to disable encryption beforehand. Can you advise proper wipe steps, or is this correct?
- unlock bootloader
- restart phone, enable developer options for USB debugging
- fastboot twrp-3.0.3-0-angler.img
- factory reset
- wipe everything (all checkboxes) including internal? (will this format with no encryption?)
- wipe system, data, cache
- push ROM (PN), Gapps, SuperSU-v2.79-201612051815.zip to phone via ADB in TWRP
- flash ROM (PN), Gapps, SuperSU-v2.79-201612051815.zip
- restart
Or is there another way to decrypt data or is it not an issue when clean wiping a new ROM?
Thanks and appreciate any help.
martinomac said:
Hey, I'm running into the same problem after an RMA. I'm currently on stock unrooted 7.1.1 and want to flash custom rom but want to disable encryption beforehand. Can you advise proper wipe steps, or is this correct?
- unlock bootloader
- restart phone, enable developer options for USB debugging
- fastboot twrp-3.0.3-0-angler.img
- factory reset
- wipe everything (all checkboxes) including internal? (will this format with no encryption?)
- wipe system, data, cache
- push ROM (PN), Gapps, SuperSU-v2.79-201612051815.zip to phone via ADB in TWRP
- flash ROM (PN), Gapps, SuperSU-v2.79-201612051815.zip
- restart
Or is there another way to decrypt data or is it not an issue when clean wiping a new ROM?
Thanks and appreciate any help.
Click to expand...
Click to collapse
You need to Format Data, Not Wipe to decrypt. It WILL wipe EVERYTHING so make sure anything in internal storage you want is backed up.
CyberpodS2 said:
You need to Format Data, Not Wipe to decrypt. It WILL wipe EVERYTHING so make sure anything in internal storage you want is backed up.
Click to expand...
Click to collapse
Thanks for confirming, I wasn't aware that there's a difference between Format Data and Wipe Data. After formatting data, I should be able to sideload the ROM, gapps, etc back via TWRP right?
I always try to keep an emergency folder on the PC with the minimum needed to copy back to the phone through recovery. In my case I keep a copy of pure nexus, dynamic gapps, supersu and elementalx. That combination never fails to boot and I know it well enough to get back in business in short order if it all went to hell. Do what's best for you.
Sent from my Nexus 6 using XDA-Developers Legacy app

Flash 8.0 using FlashFire

Can you/has anyone flashed 8.0 using FlashFire? Full image and just flashing Boot, System, and Vendor from 7.1.2? The reason I ask, I have never had luck doing just downloading the OTA, and flashing that with FlashFire
Thanks
idbl_fanatic said:
Can you/has anyone flashed 8.0 using FlashFire? Full image and just flashing Boot, System, and Vendor from 7.1.2? The reason I ask, I have never had luck doing just downloading the OTA, and flashing that with FlashFire
Thanks
Click to expand...
Click to collapse
Update, flashing the OTA zip file does not work, I ended up flashing the full system and only selecting Boot, System, and Vendor, so fare so good
Did you grab the factory image? I noticed that it reads Not for TMO/USCC/Fi
Bangincrazy said:
Did you grab the factory image? I noticed that it reads Not for TMO/USCC/Fi
Click to expand...
Click to collapse
Yes, Factory image, I am on AT&T
idbl_fanatic said:
Yes, Factory image, I am on AT&T
Click to expand...
Click to collapse
Now all you need to do is manually flash the bootloader and modem via fastboot.
v12xke said:
Now all you need to do is manually flash the bootloader and modem via fastboot.
Click to expand...
Click to collapse
you can always ran the flash-all.bat file after editing the file and removing the -w from it.
If you want to keep your system decrypted simply boot to bootloader/recoery and flash any moded kernel. either way, using flashboot is simple enough so you don't have to use flashfire.
idbl_fanatic said:
Update, flashing the OTA zip file does not work, I ended up flashing the full system and only selecting Boot, System, and Vendor, so fare so good
Click to expand...
Click to collapse
This worked for me, except that it erased TWRP even when I selected to option to back up recovery. At the end it wouldn't boot up and had to perform a factory reset, so in the end, I got a clean, stock 8.0, unrooted.
patriot76 said:
This worked for me, except that it erased TWRP even when I selected to option to back up recovery. At the end it wouldn't boot up and had to perform a factory reset, so in the end, I got a clean, stock 8.0, unrooted.
Click to expand...
Click to collapse
I wonder why it did that, I had no issues, I have had it do that before on 7.1.2 however.
I downloaded the full ota file from Google site, and flashed it like a normal ota + root afterwards with flashfire.
Been 3 days since, Android o works like a charm!
ixayman said:
I downloaded the full ota file from Google site, and flashed it like a normal ota + root afterwards with flashfire.
Been 3 days since, Android o works like a charm!
Click to expand...
Click to collapse
Wow that's good news, what phone & What carrier are you using? Did FlashFire read it the way it does with a Nougat OTA update
fiverings said:
Wow that's good news, what phone & What carrier are you using? Did FlashFire read it the way it does with a Nougat OTA update
Click to expand...
Click to collapse
my phone is 6p 64g, for my carrier I'm using a local one here in israel so idk if it's relevant to the issues you guys get :C.
in terms of flashing i flashed it like any normal monthly security patch lol, just went on google ota page, downloaded the ~1gb file.. then on flashfire i chose ota, selected said file + inject superSu afterwards, for wiping i chose cache and dalvik only. and done.
ixayman said:
my phone is 6p 64g, for my carrier I'm using a local one here in israel so idk if it's relevant to the issues you guys get :C.
in terms of flashing i flashed it like any normal monthly security patch lol, just went on google ota page, downloaded the ~1gb file.. then on flashfire i chose ota, selected said file + inject superSu afterwards, for wiping i chose cache and dalvik only. and done.
Click to expand...
Click to collapse
I have 6p 64gb also. We're you on the August build 7.1.2. and you only wiped dalvik and Cache and did you uncheck Data & 3rd party apps.so you just wiped dalvik & cache and nothing else. I usually flash the factory image to get monthly update because my bootloader is unlocked. So I don't get OTA updates thru my phone.
fiverings said:
I have 6p 64gb also. We're you on the August build 7.1.2. and you only wiped dalvik and Cache and did you uncheck Data & 3rd party apps.so you just wiped dalvik & cache and nothing else. I usually flash the factory image to get monthly update because my bootloader is unlocked. So I don't get OTA updates thru my phone.
Click to expand...
Click to collapse
i think i was on may or June's build i don't remember correctly. I also have bootloader unlocked but i never allow automatic OTA updates threw my phone, I just download the file manually (from here https://developers.google.com/android/ota) and flash it with flashfire, that way i continue where i left off without loosing any data (+root ). you should try it. and yeah on wipe options i untick everything except cache and dalvik.
ixayman said:
i think i was on may or June's build i don't remember correctly. I also have bootloader unlocked but i never allow automatic OTA updates threw my phone, I just download the file manually (from here https://developers.google.com/android/ota) and flash it with flashfire, that way i continue where i left off without loosing any data (+root ). you should try it. and yeah on wipe options i untick everything except cache and dalvik.
Click to expand...
Click to collapse
Thanks ixayman, going to wait a few days, because the OTA says it's not compatible with T-Mobile, us Cellular, Fi. All those are in my fi that I use. And I read that people who down loaded either Factory image or OTA are not working with Fi . When they fix this I try it then.
Thanks, you've been a big help

Categories

Resources