Develop Bugs

[Q] Please help me get a usable phone again

I decided to try cyanogenmod on my SGH-I747 but have had so many issues I would be happy at this point if I could just get a working phone again.
I started with a 4.3 OTA-updated phone. I rooted the phone, then tried to install the latest 10.2 ROM. I also tried 10.1. I used CWM: I would have preferred the latest version but the best I could find that was not an .img file (I used Odin) was in the 5.x range. In both cases I hit what I believe is a bootloader error ("assert failed: ... Status 7"). At this point the phone is wiped with no recourse. I attempted to install the stock boot image for the I747, but after doing so the phone will no longer boot.
EDIT: I am able to get to downloading mode. I am afraid to use it to install stock firmware b/c of a post I found here claiming that downgrading from 4.3 OTA (e.g., to 4.1) will brick the phone.

tn6 said:
I decided to try cyanogenmod on my SGH-I747 but have had so many issues I would be happy at this point if I could just get a working phone again.
I started with a 4.3 OTA-updated phone. I rooted the phone, then tried to install the latest 10.2 ROM. I also tried 10.1. I used CWM: I would have preferred the latest version but the best I could find that was not an .img file (I used Odin) was in the 5.x range. In both cases I hit what I believe is a bootloader error ("assert failed: ... Status 7"). At this point the phone is wiped with no recourse. I attempted to install the stock boot image for the I747, but after doing so the phone will no longer boot.
EDIT: I am able to get to downloading mode. I am afraid to use it to install stock firmware b/c of a post I found here claiming that downgrading from 4.3 OTA (e.g., to 4.1) will brick the phone.
Click to expand...
Click to collapse
i actually had the same problem earlier today. what i did was use odin to install clockworkmod recovery. after it reboots, hold VOLUME UP and HOME at the same time. if you have a micro sd handy, download any of the two updates here http://forum.xda-developers.com/showthread.php?t=2498233 place them on you sd card and in recovery format cache and factory reset/data. then highlight "install zip from sd card" or something that sounds relevant. select the zip you placed on your sd card earlier and there.

Worked, I think
MrHaPpY66 said:
i actually had the same problem earlier today. what i did was use odin to install clockworkmod recovery. after it reboots, hold VOLUME UP and HOME at the same time. if you have a micro sd handy, download any of the two updates here http://forum.xda-developers.com/showthread.php?t=2498233 place them on you sd card and in recovery format cache and factory reset/data. then highlight "install zip from sd card" or something that sounds relevant. select the zip you placed on your sd card earlier and there.
Click to expand...
Click to collapse
Thank you. The phone now boots to a white screen with an AT&T symbol. How can I install either a stock or custom ROM without ruining everything again?

tn6 said:
Thank you. The phone now boots to a white screen with an AT&T symbol. How can I install either a stock or custom ROM without ruining everything again?
Click to expand...
Click to collapse
i think this should be a help http://forum.xda-developers.com/showthread.php?t=2539313

No luck
MrHaPpY66 said:
i think this should be a help http://forum.xda-developers.com/showthread.php?t=2539313
Click to expand...
Click to collapse
That appears to be the standard tutorial for rooting/flashing. I did it anyway, even though didn't the file you had me install before already root the phone? In any event, I ran CF-root and then I attempted to install CM 10.2 and it failed: "failed to verify whole-file signature." I believe that was the first error I hit in the beginning of this exercise. Additionally, now I get an error on the welcome screen that says "Unfortunately, SuperSU has stopped."

tn6 said:
That appears to be the standard tutorial for rooting/flashing. I did it anyway, even though didn't the file you had me install before already root the phone? In any event, I ran CF-root and then I attempted to install CM 10.2 and it failed: "failed to verify whole-file signature." I believe that was the first error I hit in the beginning of this exercise. Additionally, now I get an error on the welcome screen that says "Unfortunately, SuperSU has stopped."
Click to expand...
Click to collapse
for the supersu, you probably need to go update it on the market or disable KNOX

assert failed... getprop("ro.bootloader")
MrHaPpY66 said:
for the supersu, you probably need to go update it on the market or disable KNOX
Click to expand...
Click to collapse
Thanks for the suggestion. I went back to the no-KNOX file you pointed out earlier. I assume that is the same type of file as the CF-Root so I assume I don't need to install CF-root anymore after installing the no-KNOX file. So now I follow the tutorial from your second response minus the root step. I no longer get the SuperSU error. However, I still can't load a ROM. I get the same "assert failed... getprop("ro.bootloader... Status 7" that I mentioned in my first post. When I googled this in the first round, I saw several posts saying it means I had a bad bootloader. That is when I tried to flash the stock bootloader, which nearly hardbricked the phone. Do the two files you initially posted include a bootloader file?

tn6 said:
Thanks for the suggestion. I went back to the no-KNOX file you pointed out earlier. I assume that is the same type of file as the CF-Root so I assume I don't need to install CF-root anymore after installing the no-KNOX file. So now I follow the tutorial from your second response minus the root step. I no longer get the SuperSU error. However, I still can't load a ROM. I get the same "assert failed... getprop("ro.bootloader... Status 7" that I mentioned in my first post. When I googled this in the first round, I saw several posts saying it means I had a bad bootloader. That is when I tried to flash the stock bootloader, which nearly hardbricked the phone. Do the two files you initially posted include a bootloader file?
Click to expand...
Click to collapse
i think they contained the mj2 bootloader and modem. hmm i've been doing a little snooping around and i found this. http://forum.xda-developers.com/showthread.php?t=2540998 the thing is i still don't understand how to go from leaked (mj2) to the official release (mjb) maybe updating to this will help

MrHaPpY66 said:
i think they contained the mj2 bootloader and modem. hmm i've been doing a little snooping around and i found this. http://forum.xda-developers.com/showthread.php?t=2540998 the thing is i still don't understand how to go from leaked (mj2) to the official release (mjb) maybe updating to this will help
Click to expand...
Click to collapse
I'm worried about switching bootloaders. This post seems to indicate that doing so after I installed 4.3 OTA will brick the phone. Does anyone know if that is true?
http://forum.xda-developers.com/showthread.php?t=2321310

tn6 said:
I'm worried about switching bootloaders. This post seems to indicate that doing so after I installed 4.3 OTA will brick the phone. Does anyone know if that is true?
http://forum.xda-developers.com/showthread.php?t=2321310
Click to expand...
Click to collapse
ohh ho ho it's true alright. the new 4.3 bootloader, i'm guessing it is mjb, doesn't allow any downgrades. Downgrades of any kind will absolutely give you a nice, good brick. anyways do you understand how to go from 4.3 leaked to 4.3 official?

MrHaPpY66 said:
ohh ho ho it's true alright. the new 4.3 bootloader, i'm guessing it is mjb, doesn't allow any downgrades. Downgrades of any kind will absolutely give you a nice, good brick. anyways do you understand how to go from 4.3 leaked to 4.3 official?
Click to expand...
Click to collapse
No idea. I went ahead and tried to install the I747UCDLK3_aio.tar.md5, which I hoped was a 4.3 bootloader (don't know how you are supposed to tell). The error I got was this was another failure--this time saying the package was for d2att and this is a d2spr. My phone is definitely not a sprint phone. Some posts say I have to update the build.prop file, but I don't know how I can do that before a ROM is even installed.

resolved
tn6 said:
No idea. I went ahead and tried to install the I747UCDLK3_aio.tar.md5, which I hoped was a 4.3 bootloader (don't know how you are supposed to tell). The error I got was this was another failure--this time saying the package was for d2att and this is a d2spr. My phone is definitely not a sprint phone. Some posts say I have to update the build.prop file, but I don't know how I can do that before a ROM is even installed.
Click to expand...
Click to collapse
I realized that many of the errors I was getting seemed to be tied to cyanogenmod or stock. So I downloaded Hyperdrive and it installed with zero hiccups or errors. I have a working phone again.
Thank you for your helpful insights.

tn6 said:
I realized that many of the errors I was getting seemed to be tied to cyanogenmod or stock. So I downloaded Hyperdrive and it installed with zero hiccups or errors. I have a working phone again.
Thank you for your helpful insights.
Click to expand...
Click to collapse
you're welcome and i glad i was a help to you. anyways where'd you get hyperdrive? i've been trying to get my phone back to official stock and off the leaked one.

MrHaPpY66 said:
you're welcome and i glad i was a help to you. anyways where'd you get hyperdrive? i've been trying to get my phone back to official stock and off the leaked one.
Click to expand...
Click to collapse
I downloaded hyperdrive from the official spot: http://forum.xda-developers.com/showthread.php?t=2106830. I wouldn't have minded going back to stock, but clearly that was not going to happen any time soon.

tn6 said:
I downloaded hyperdrive from the official spot: http://forum.xda-developers.com/showthread.php?t=2106830. I wouldn't have minded going back to stock, but clearly that was not going to happen any time soon.
Click to expand...
Click to collapse
so how's the rom so far? probably going to get it myself.

MrHaPpY66 said:
so how's the rom so far? probably going to get it myself.
Click to expand...
Click to collapse
Zero issues. Worked great all day with no problems. Plus I am now able to tether and use the mobile hotspot, features that I couldn't get to work on the stock rom even with foxfi or similar apps.

tn6 said:
Zero issues. Worked great all day with no problems. Plus I am now able to tether and use the mobile hotspot, features that I couldn't get to work on the stock rom even with foxfi or similar apps.
Click to expand...
Click to collapse
so i see it's a lot better than stock. i'll install it as soon as i can and thanks for the link to the rom

Verizon LG G Pad 8.3 system update

I rooted this tablet last week (just rooted, I left it stock) and this morning I notice there is a system update waiting to be installed. I am reading Lollipop is starting to roll out in Asia somewhere now but I am in the US lol. I thought it wasn't possible to get OTA updates once you root? If I allow this to update will I get unrooted, would it even work?
I foolishly allowed it to update after checking in Supersu to not allow the root to be lost and now I keep booting directly into TWRP lol. How do I wipe this tablet from TWRP so that it is fully stock again (NO ROOT)? I see a factory reset option in TWRP do I need to include all the partitions in the advanced wipe or is just the normal wipe method enough? Or will this not work at all? I already tried to restore the phone using TWRP to my backup and that didn't seem to work.

Anthony-m said:
I rooted this tablet last week (just rooted, I left it stock) and this morning I notice there is a system update waiting to be installed. I am reading Lollipop is starting to roll out in Asia somewhere now but I am in the US lol. I thought it wasn't possible to get OTA updates once you root? If I allow this to update will I get unrooted, would it even work? .
Click to expand...
Click to collapse
Simply rooting a device doesn't keep it from TRYing to update via OTA. Rooting can prevent an OTA from succeeding, plus can hard or soft brick if you try to take an OTA, although usually only if you've gone beyond just rooting by installing a custom recovery or changing the contents of any partition besides Data by, fire example, downgrading your bootloader (aboot.img) or modem, running a custom kernel, debloating system apps, etc.
There are at least three variants of the G Pad 8.3. I have the VK810.4G, which do you have?
I know on the VK810.4G, Verizon just released a very, very minor update from LG build #23A to 24A. Still KitKat.
I foolishly allowed it to update after checking in Supersu to not allow the root to be lost and now I keep booting directly into TWRP lol.
Click to expand...
Click to collapse
There's the main problem, you had a custom recovery installed. OTAs are applied with the stock recovery, that's why it (probably soft) bricked it.
How do I wipe this tablet from TWRP so that it is fully stock again (NO ROOT)? I see a factory reset option in TWRP do I need to include all the partitions in the advanced wipe or is just the normal wipe method enough? Or will this not work at all? I already tried to restore the phone using TWRP to my backup and that didn't seem to work.
Click to expand...
Click to collapse
You might not be able to fix it from TWRP. You could try @autoprime 's fix recovery zip available the same page his flash2 scripts are. You'll have to Google:
autoprime flash2
Click to expand...
Click to collapse
.
Otherwise, you'll have to restore to 100% stock unrooted and start from scratch. Two methods.
One is using LG's official Mobile Tool, which will download the latest official ROM in KDZ format (takes 20+ minutes to download) and flash it with your tablet in Download mode (probably with the tablet off, hold both up and down volume buttons in and while holding them, turn the tablet on.
I've got to go do something so hopefully someone else will help further or I can get back to you later, dont know when though.
Good luck!
Sent from my VK810 4G

I did the TWRP terminal commands from the thread listed below and it got me right out of that jam...
http://forum.xda-developers.com/lg-g-pad-83/help/vk810-download-mode-boot-loop-t2991512

OK now that I am up and running fine the system update message keeps popping up. This time I KNOW not to try and upgrade while rooted. Is there any way I can stop the tablet from constantly giving me the upgrade message? Can I do anything from TWRP to stop this?

Anthony-m said:
... This time I KNOW not to try and upgrade while rooted. Is there any way I can stop the tablet from constantly giving me the upgrade message? Can I do anything from TWRP to stop this?
Click to expand...
Click to collapse
Don't install TWRP. I was rooted (w/ stock recovery) with 23A, and the OTA update worked fine (still rooted).

DeanGibson said:
Don't install TWRP. I was rooted (w/ stock recovery) with 23A, and the OTA update worked fine (still rooted).
Click to expand...
Click to collapse
TWRP is already installed..
Can I uninstall TWRP, keep root , do the update and then reinstall TWRP? If so how? Is there any other way around this issue, any way of not having the tablet continue to ask me to upgrade? Thanks BTW...

Anthony-m said:
TWRP is already installed..
Can I uninstall TWRP, keep root , do the update and then reinstall TWRP? If so how? Is there any other way around this issue, any way of not having the tablet continue to ask me to upgrade? Thanks BTW...
Click to expand...
Click to collapse
Yes, you can do that, but I don't know the steps. Others here do.
Why do you want TWRP? I thought the usual reason was to install custom ROMs (in which case you won't receive any OTA updates). If you just want to root, it's an unnecessary complication (as you have discovered).

DeanGibson said:
Yes, you can do that, but I don't know the steps. Others here do.
Why do you want TWRP? I thought the usual reason was to install custom ROMs (in which case you won't receive any OTA updates). If you just want to root, it's an unnecessary complication (as you have discovered).
Click to expand...
Click to collapse
Thanks Dean, and yes I do agree with you about it being a complication. I was always under the assumption if I rooted a phone that I needed to also use some sort of recovery god forbid I had an issue with the phone not booting up or something so I could possibly fix the issue, make a backup/install a backup etc. Maybe I will ****can it if someone will tell me how to do so without losing my data or root.

Anthony-m said:
Thanks Dean, and yes I do agree with you about it being a complication. I was always under the assumption if I rooted a phone that I needed to also use some sort of recovery god forbid I had an issue with the phone not booting up or something so I could possibly fix the issue, make a backup/install a backup etc. Maybe I will ****can it if someone will tell me how to do so without losing my data or root.
Click to expand...
Click to collapse
FYI I just froze the update using Titanium backup pro and my problem is solved for now..

Flashed faulty [System] from recovery

What happened:
1. Used TWRP to flash an earlier System backup
2. Boots but two system apps force close and phone reboots
3. This goes on indefinitely
4. Can no longer go to either recovery
I'm thinking I should use FlashTool and flash a default System for 14.5.A.0.270 but I can't seem to find any firmware image for it. Does anybody have this/better idea to get me out of the boot loop?
Edit: found the file, will report back.

another complication: I can't go into flashmode

ctap001 said:
another complication: I can't go into flashmode
Click to expand...
Click to collapse
Bl locked or unlocked?

levone1 said:
Bl locked or unlocked?
Click to expand...
Click to collapse
locked. Am I SOTL?

ctap001 said:
locked. Am I SOTL?
Click to expand...
Click to collapse
Probably not. Are you wanting to save data, etc?

levone1 said:
Probably not. Are you wanting to save data, etc?
Click to expand...
Click to collapse
If possible, yes. My last complete backup was on September. I'm still waiting for the firmware download to finish, however if I that doesn't work (won't allow me to flash) I am completely OK with wiping everything.

ctap001 said:
If possible, yes. My last complete backup was on September. I'm still waiting for the firmware download to finish, however if I that doesn't work (won't allow me to flash) I am completely OK with wiping everything.
Click to expand...
Click to collapse
I wasn't sure from the first post. Does the phone stay on if you don't do anything or does it automatically reboot? I was thinking a good first try might be NUT dual recovery installer, but won't work if phone won't stay on. Check back after your flash attempt - note that you will likely wipe all of your data if flashing with FT.

levone1 said:
I wasn't sure from the first post. Does the phone stay on if you don't do anything or does it automatically reboot? I was thinking a good first try might be NUT dual recovery installer, but won't work if phone won't stay on. Check back after your flash attempt - note that you will likely wipe all of your data if flashing with FT.
Click to expand...
Click to collapse
It won't stay on. It will crash then reboot.
Can't proceed with flashtool because I am having trouble installing the drivers (on w10)

ctap001 said:
It won't stay on. It will crash then reboot.
Can't proceed with flashtool because I am having trouble installing the drivers (on w10)
Click to expand...
Click to collapse
If you can't boot, you might be able to save data through adb. If you give up on saving data, either Emma or PC Companion can repair phone if you can't get FT to work. Since they're both official Sony programs, they may be easier to get working with Win10.

levone1 said:
If you can't boot, you might be able to save data through adb. If you give up on saving data, either Emma or PC Companion can repair phone if you can't get FT to work. Since they're both official Sony programs, they may be easier to get working with Win10.
Click to expand...
Click to collapse
I have flashed System from an unrooted FTF. Still can't access recovery though

ctap001 said:
I have flashed System from an unrooted FTF. Still can't access recovery though
Click to expand...
Click to collapse
Which fw did you flash? If it's 5.1, (368 at least, not sure about 216), I've read that Kingroot method is working now. Look here - http://forum.xda-developers.com/sony-xperia-z1-compact/general/root-14-6-0-368-via-kingroot-t3242735 . If 5.0, there is a root tool that will work. Once rooted, flash NUT's installer for recovery.

levone1 said:
Which fw did you flash? If it's 5.1, (368 at least, not sure about 216), I've read that Kingroot method is working now. Look here - http://forum.xda-developers.com/sony-xperia-z1-compact/general/root-14-6-0-368-via-kingroot-t3242735 . If 5.0, there is a root tool that will work. Once rooted, flash NUT's installer for recovery.
Click to expand...
Click to collapse
>5.1
I tried flashing the early pre-rooted 5.1s and they gave me problems with NFC so I reverted to 5.0.1
Looking for the 5.0 root tool right now.
edit: kingroot doesn't work

ctap001 said:
>5.1
I tried flashing the early pre-rooted 5.1s and they gave me problems with NFC so I reverted to 5.0.1
Looking for the 5.0 root tool right now.
edit: kingroot doesn't work
Click to expand...
Click to collapse
Haven't tried it myself, but it seems like they've got it working. I noticed in the thread that there seems to be different instructions for 368 and 216....

levone1 said:
Haven't tried it myself, but it seems like they've got it working. I noticed in the thread that there seems to be different instructions for 368 and 216....
Click to expand...
Click to collapse
I got everything back to 270 now. Currently at the optimizing apps part. This all began because I upgraded SD cards and while everything was carried over through a plain copy-paste, my Walkman playlists and favorites didn't make it. I somehow equated the System portion as a possible fix.
Anyway are you on 5.1? Does NFC unlock works? Thanks for pointing me at the right direction.

ctap001 said:
I got everything back to 270 now. Currently at the optimizing apps part. This all began because I upgraded SD cards and while everything was carried over through a plain copy-paste, my Walkman playlists and favorites didn't make it. I somehow equated the System portion as a possible fix.
Anyway are you on 5.1? Does NFC unlock works? Thanks for pointing me at the right direction.
Click to expand...
Click to collapse
Haven't had any problems with 5.1. I flashed stock .216 few a week ago, and have since rooted, modded, etc., and everything good. Your problems were probably related to PRF. I've read the same from others

levone1 said:
Haven't had any problems with 5.1. I flashed stock .216 few a week ago, and have since rooted, modded, etc., and everything good. Your problems were probably related to PRF. I've read the same from others
Click to expand...
Click to collapse
> .216
The latest I tried was .380

King root
I had a similar problem last night. Installed stock firmware off flashtool then loaded it up and King Root worked perfectly. Having trouble getting a recovery on the phone now.

wwwjunkboywww said:
I had a similar problem last night. Installed stock firmware off flashtool then loaded it up and King Root worked perfectly. Having trouble getting a recovery on the phone now.
Click to expand...
Click to collapse
Use 'installer' option from Z1c downloads on NUT's download page. It's never failed for me. Just watch phone screen and grant 'OK' for adb access and for root. Besides that, if you have unlocked bl, use fastboot or Rashr.

Thanks
levone1 said:
Use 'installer' option from Z1c downloads on NUT's download page. It's never failed for me. Just watch phone screen and grant 'OK' for adb access and for root. Besides that, if you have unlocked bl, use fastboot or Rashr.
Click to expand...
Click to collapse
Yeah i had tried that. The BAT right? I ended up flashing multi twrp and then using that to get NUT's, he's made a sweet recovery.

Guide [Simple]: OTA update with rooted and unlocked

Hi,
This guide is based in my first post about how to do it with the Moto G4: http://forum.xda-developers.com/moto-g4/how-to/guide-simple-ota-update-rooted-unlocked-t3510126
(Read it for full info).
Then, here the updated info for the Moto G5+:
1) If you are in NPN25.137-33 and like to apply the last OTA, but you have rooted and/or flashed a custom recovery (TWRP) + custom kernel, then you can.
2) Requirements: original SYSTEM and BOOT partitions. If you have flashed another version, then restore the originals. You can use any backups from you, or you can download from here: http://drive.google.com/open?id=0B6-Tz_7kDyxsZnVNa0pldnhndG8
(Thank you to GtrCraft: http://forum.xda-developers.com/showpost.php?p=72387571&postcount=15)
3) To apply the OTA download this ZIP and install it from the TWRP recovery (it's not required to have the TWRP flashed, you can start it from the fastboot util): http://www.sendspace.com/file/7w75rw
This file is the original OTA (shared by the user olive23) and patched by me to remove the check for the fingerprint of the running firmware. Then it can run over the TWRP.
Warning: Don't install this OTA if you don't have the exact version of the required firmware.
4) After install the OTA, reboot and check the new version. At that point the ROM isn't rooted. Then, you need to re-root.
That's all!

Tried flashing and it fails.

You need stock recovery to flash OTA's

GtrCraft said:
You need stock recovery to flash OTA's
Click to expand...
Click to collapse
Isn't that the point of this post? He said he patched the OTA update so it could be flashed with TWRP.
3) To apply the OTA download this ZIP and install it from the TWRP recovery (it's not required to have the TWRP flashed, you can start it from the fastboot util): http://www.sendspace.com/file/7w75rw
This file is the original OTA (shared by the user olive23) and patched by me to remove the check for the fingerprint of the running firmware. Then it can run over the TWRP.
Click to expand...
Click to collapse

bvsbutthd101 said:
Isn't that the point of this post? He said he patched the OTA update so it could be flashed with TWRP.
Click to expand...
Click to collapse
Well the OTA isn't meant for reteu firmware. So that will bring problems with it

bvsbutthd101 said:
Tried flashing and it fails.
Click to expand...
Click to collapse
Because isn't for your device OR you have modified SYSTEM or BOOT.

GtrCraft said:
You need stock recovery to flash OTA's
Click to expand...
Click to collapse
FALSE!
GtrCraft said:
Well the OTA isn't meant for reteu firmware. So that will bring problems with it
Click to expand...
Click to collapse
TRUE! :silly:

manos78 said:
Because isn't for your device OR you have modified SYSTEM or BOOT.
Click to expand...
Click to collapse
Installing TWRP and rooting doesn't change the SYSTEM or BOOT right? Must just not be for my device then. I have the US 4gb model (XT1687)

bvsbutthd101 said:
Must just not be for my device then. I have the US 4gb model (XT1687)
Click to expand...
Click to collapse
Probably. This OTA is from user "olive23".
I don't have (still) received any OTA in my XT1685 (EU 3/32).

manos78 said:
Probably. This OTA is from user "olive23".
I don't have (still) received any OTA in my XT1685 (EU 3/32).
Click to expand...
Click to collapse
Here's the OTA for the US 4gb model if you're interested. :good:
https://drive.google.com/open?id=0BxqNotAWlwLUQ1Fzcjc2YXd4QzA

bvsbutthd101 said:
Installing TWRP and rooting doesn't change the SYSTEM or BOOT right? Must just not be for my device then. I have the US 4gb model (XT1687)
Click to expand...
Click to collapse
I have the same US model and this is supposed to be for it but it didn't work for me either, got errors during flash of OTA zip in TWRP that various partitions weren't accessible &/or verifiable. Even tried it a second time after a full restore to stock and had similar errors. I restored SYSTEM too (not sure that our rooting process works for systemless yet, meaning it would change SYSTEM), so that wasn't the problem in my case. Restored stock again and will wait to see if I get OTA normally.
bvsbutthd101 said:
Here's the OTA for the US 4gb model if you're interested. :good:
https://drive.google.com/open?id=0BxqNotAWlwLUQ1Fzcjc2YXd4QzA
Click to expand...
Click to collapse
So did you get this OTA normally as a system update, indicating that we should be receiving it now?

Dahenjo said:
I have the same US model and this is supposed to be for it but it didn't work for me either, got errors during flash of OTA zip in TWRP that various partitions weren't accessible &/or verifiable. Even tried it a second time after a full restore to stock and had similar errors. I restored SYSTEM too (not sure that our rooting process works for systemless yet, meaning it would change SYSTEM), so that wasn't the problem in my case. Restored stock again and will wait to see if I get OTA normally.
So did you get this OTA normally as a system update, indicating that we should be receiving it now?
Click to expand...
Click to collapse
I got the update weeks ago. I've been postponing until someone makes it's flashable. I ripped it from my phone when I got it so yes, it's from my phone.

bvsbutthd101 said:
I got the update weeks ago. I've been postponing until someone makes it's flashable. I ripped it from my phone when I got it so yes, it's from my phone.
Click to expand...
Click to collapse
Thanks. I wonder why I haven't gotten anything and had phone since it came out on 3/31. I'm on NPN25.137-33 with a 4GB XT1687 from Amazon ($299 full-price without ads) on AT&T if carrier matters. Rooted or not we should still get the notifications as you have.

Dahenjo said:
Thanks. I wonder why I haven't gotten anything and had phone since it came out on 3/31. I'm on NPN25.137-33 with a 4GB XT1687 from Amazon ($299 full-price without ads) on AT&T if carrier matters. Rooted or not we should still get the notifications as you have.
Click to expand...
Click to collapse
Yeah I got mine the day it came out from amazon, using on Verizon.

Here is a flashable stock zip based on reteu firmware:
https://drive.google.com/open?id=0B6-Tz_7kDyxsU2NlTERsSzZsalk

U have*67 files??

Same Here
US variant XT1687 4/64GB on Sprint but no OTA notification. Maybe I should just wait another week before flashing this. Not sure if there is something in the SIM the server notices and stops updates on some carriers. But maybe the SIM is how they decide, not sure what else they could go by other than IP to detect the carrier.
bvsbutthd101 said:
Yeah I got mine the day it came out from amazon, using on Verizon.
Click to expand...
Click to collapse

I also have XT1687 4/64G US on 25.137-33 + root & TWRP, and no OTA notification.
So, is there a way to go to -67 (flash over TWRP, restore back to -15 stock)?
I could not understand the right answer from all the thread on the subject.

Sorry for this noob question: I have just rooted a brand new phone. After the first login the OTA warning popped out so I downloaded it. When finished I got a loop on the recovery; I fastbooted boot and got my phone working again ... what do I have to do? Thanks.

Hi,
My upgraded guide: http://forum.xda-developers.com/g5-plus/how-to/guide-complex-ota-update-magisk-rooted-t3688175

Cannot update to Oreo

I cannot update to Oreo on my Sprint variant. I was rooted with TWRP but did the flash all back to stock. I am unrooted, stock recovery, with unlocked bootloader. I have tried through update.zip, sideload, and the normal way through the settings and they all fail. I successfully updated the normal way with the last 2 updates that were released, but no luck with this one.

Comet1966 said:
I cannot update to Oreo on my Sprint variant. I was rooted with TWRP but did the flash all back to stock. I am unrooted, stock recovery, with unlocked bootloader. I have tried through update.zip, sideload, and the normal way through the settings and they all fail. I successfully updated the normal way with the last 2 updates that were released, but no luck with this one.
Click to expand...
Click to collapse
Very weird as I was in the same predicament as you with being rooted with twrp & having to use flash all to go back to stock, but I was able to take the Oreo ota with no problems afterwards.
Sent from my Moto Z (2) using Tapatalk

piscesjoey said:
Very weird as I was in the same predicament as you with being rooted with twrp & having to use flash all to go back to stock, but I was able to take the Oreo ota with no problems afterwards.
Sent from my Moto Z (2) using Tapatalk
Click to expand...
Click to collapse
It's like the system and recovery don't have access to the storage at all.

Which flash all did you use? mine updated just fine with that file doing adb sideload file/name/here when selecting the option for update via adb. How long did it take before the error. It takes awhile for the update to go through. (roughly the same time or longer than updating in android. my time was about 12mins.

Uzephi said:
Which flash all did you use? mine updated just fine with that file doing adb sideload file/name/here when selecting the option for update via adb. How long did it take before the error. It takes awhile for the update to go through. (roughly the same time or longer than updating in android. my time was about 12mins.
Click to expand...
Click to collapse
It got to 47% then started to flash and then the error that's for the sideload. As for the update.zip and applying it, it fails instantly.
I think I did this one: https://forum.xda-developers.com/z2-force/how-to/to-stock-roms-t3672859

Comet1966 said:
It got to 47% then started to flash and then the error that's for the sideload. As for the update.zip and applying it, it fails instantly.
I think I did this one: https://forum.xda-developers.com/z2-force/how-to/to-stock-roms-t3672859
Click to expand...
Click to collapse
So, you flashall and then it doesn't take Oreo but all others? Sounds like something is really messed up on your device then. Did you flash a modified logo bin?

Uzephi said:
So, you flashall and then it doesn't take Oreo but all others? Sounds like something is really messed up on your device then. Did you flash a modified logo bin?
Click to expand...
Click to collapse
I did the flashall and that's it. I have no idea what's up with it

Comet1966 said:
I did the flashall and that's it. I have no idea what's up with it
Click to expand...
Click to collapse
What is your current version? -11/November patch?

Uzephi said:
What is your current version? -11/November patch?
Click to expand...
Click to collapse
This

Comet1966 said:
This
Click to expand...
Click to collapse
That isn't one of the flash all's in the thread. You need to run the bat file. Depending on the one you use you should go to the August or September security patch.

Uzephi said:
That isn't one of the flash all's in the thread. You need to run the bat file. Depending on the one you use you should go to the August or September security patch.
Click to expand...
Click to collapse
I am trying that one again. Factory reset didn't help either.

I did the flashall to 122-59-8. Now I am updating to 122-59-8-6

Comet1966 said:
I did the flashall to 122-59-8. Now I am updating to 122-59-8-6
Click to expand...
Click to collapse
Which version of the bootloader? If the Oreo bootloader then perhaps this will result in an error.
If you installed Oreo Global or TMO after that, the bootloader will be upgraded to Oreo, perhaps this will lead to an error.

So I did the flashall, updated all the way through and it worked. It was the same flash all I did before because I already had it downloaded. Thanks for helping, sucks I had to wipe, but it is what it is.

Comet1966 said:
So I did the flashall, updated all the way through and it worked. It was the same flash all I did before because I already had it downloaded. Thanks for helping, sucks I had to wipe, but it is what it is.
Click to expand...
Click to collapse
Wow, must've been some kind of bad flash previously? Either way glad that you've finally joined the rest of us!
Sent from my Moto Z (2) using Tapatalk