Im on MI1 and it won't allow me to install the new OTA. Keeps failing. Ive reset my phone, odined to the original stock and still the OTA fails. Help please
@kiilajoe are you still rooted? I had to unroot before it would take. I also had to completely remove SS. Not sure if you have recovery installed or not. There are a few people saying that OTA service is unavailable at this time as well. Update has not shown up in Kies yet so that is not an option. Not sure if a emergency recovery would work for you or not but could give it a try also. When you went back to stock did all the native apps reinstall. I had to go through MyApps in play store and manually install everything prior to upgrade.
Sent from my SCH-I545 using Tapatalk
You can ODIN back to stock 4.2.2 with http://forum.xda-developers.com/showthread.php?t=2484726 its non destructive so it will not wipe your device. However you will lose root. Then you can take the OTA with out issue.
So i recently just got my system update settings back after a minor mishap where the apk went missing. So the problem i am having is that when i try to download the 12B update since im still in 11C however the download fails. And im slightly confused as to why the update fails on the download seconds after clicking download now
ToF_Itachi said:
So i recently just got my system update settings back after a minor mishap where the apk went missing. So the problem i am having is that when i try to download the 12B update since im still in 11C however the download fails. And im slightly confused as to why the update fails on the download seconds after clicking download now
Click to expand...
Click to collapse
Have you done ANY modification of the system files (freezing) or did you bump (install TWRP)? If you installed TWRP, you cannot take OTAs and install them. You must be on the stock recovery.
iBolski said:
Have you done ANY modification of the system files (freezing) or did you bump (install TWRP)? If you installed TWRP, you cannot take OTAs and install them. You must be on the stock recovery.
Click to expand...
Click to collapse
Actually i managed to fix it myself had to go through a long 2 hour factory reset and reflashing using the flash tool just to get the update to work. But thanks for replying :good::fingers-crossed:
EDIT: Turns out the root was not the problem. It was the developer edition firmware. I flashed the new firmware from the OTA update separately and now I'm booting fine.
If you have this exact problem, unbrick instructions here:
Try using Phone Flash Tool from the Dell site, and this zip:
https://mega.co.nz/#!Vgw1CTYT!y1_tSTCMmzrhJSQy0lxwY59iyRhdJovC-IDMF25PB4k
It's the new boot firmware binaries packed in the developer edition firmware zip with the xml changed to point to the new files.
For the flashing process of this zip, start with the tablet completely off and disconnected, then in Phone Flash Tool, load the zip file, click "Start to flash" (the button near the bottom should be blue/clickable), then once it's counting attempts (attempt #0, attempt #1, etc.) then connect USB. It should proceed to flash.
Click to expand...
Click to collapse
ORIGINAL POST:I just received the Lollipop OTA, and I installed it. I did not remove my Superuser installation or my Busybox installation first. Now I am bootlooping.
So, take this as a warning, do not install the OTA if you have modified your system.
Now I am going to try to find a way to fix this...
xBIGREDDx said:
I just received the Lollipop OTA, and I installed it. I did not remove my Superuser installation or my Busybox installation first. Now I am bootlooping.
So, take this as a warning, do not install the OTA if you have modified your system.
Now I am going to try to find a way to fix this...
Click to expand...
Click to collapse
Well, yeah anytime a update via OTA is available unroot and revert the device to stock, the update is designed to go over a stock tablet.
vampirefo said:
Well, yeah anytime a update via OTA is available unroot and revert the device to stock, the update is designed to go over a stock tablet.
Click to expand...
Click to collapse
What is the process to unroot on our device?
Install es file explorer or root explorer.
Grant root access to the app.
in es you need to enable root explorer in the settings menu.
Go to
Code:
/system/bin
delete su (mine was not locate in here)
/system/xbin
delete su (mine was here)
/system/app/Superuser.apk delete this
SuperSu has a selection of uninstall options in the app's menus.
vampirefo said:
Well, yeah anytime a update via OTA is available unroot and revert the device to stock, the update is designed to go over a stock tablet.
Click to expand...
Click to collapse
I've applied plenty of OTAs in the past to other devices on top of rooted systems, and never had a problem as bad as bootlooping.
(Not saying it's not my fault, as I knew there was a risk, I guess I was just running on a series of good luck, or maybe other companies write better OTA pre-checking features.)
good you mentioned this
supersu - complete unroot - update worked
i forgot to uninstall xposed - modifications where gone after reboot (batterie percentage etc. from gravitybox)
has anyone tried rooting after update? could the kitkat method work?
kage69 said:
good you mentioned this
supersu - complete unroot - update worked
i forgot to uninstall xposed - modifications where gone after reboot (batterie percentage etc. from gravitybox)
has anyone tried rooting after update? could the kitkat method work?
Click to expand...
Click to collapse
It's hard to say, as lollipop was just released, only you guys with lollipop can test and see.
Neither SDC nor myself have lollipop so we can't test.
sent from my kingSing T1 via taptalk
On mine, I forgot to un-root with no issues, but it defaults to encrypting the tablet and now I can't re-root.
Hmm, I also had the developer firmware installed from their opensource site; maybe that's it? The only other thing would have been Busybox, I think...
EDIT: HEY IT WORKS! I just pulled the firmware binaries out of the update.zip, and flashed with xfstk-downloader, and now I'm on the Encrypting screen! Thanks!
old root method dont work :crying:
kage69 said:
old root method dont work :crying:
Click to expand...
Click to collapse
Well you tried, did you get an error? Can you give more details?
sent from my kingSing T1 via taptalk
xBIGREDDx said:
EDIT: Turns out the root was not the problem. It was the developer edition firmware. I flashed the new firmware from the OTA update separately and now I'm booting fine.
ORIGINAL POST:I just received the Lollipop OTA, and I installed it. I did not remove my Superuser installation or my Busybox installation first. Now I am bootlooping.
So, take this as a warning, do not install the OTA if you have modified your system.
Now I am going to try to find a way to fix this...
Click to expand...
Click to collapse
Will the same rooting procedure work fine after you have upgraded to Lollipop on the 7840? Wanted to try but not sure if everything will work. Also since i'm on a Mac the .bat file doesn't run out of the box...
ely105 said:
Will the same rooting procedure work fine after you have upgraded to Lollipop on the 7840? Wanted to try but not sure if everything will work. Also since i'm on a Mac the .bat file doesn't run out of the box...
Click to expand...
Click to collapse
@kage69 says no, only you guys with lollipop can confirm or deny if root works or not.
sent from my kingSing T1 via taptalk
the tool flashes temp cwm but the tab dont boot to recovery
stays in bootloader where you can choose boot normal, power down and recovery
choosing recovery boots to stock recovery
there were errors while flashing, ill post them tomorrow
reading a book in bed on my lollipopped tab now
hope we can root it again, need that for customizations and airaudio
see u tomorrow
So how were you able to flash after bootlooping the first time when you tried to update with root? I cannot get into the bootloader or anything :silly:
Does any one have the ota so I can patch the stock firmware to investigate rooting it?
might be stored in cache i think
cant get to that without root
kage69 said:
might be stored in cache i think
cant get to that without root
Click to expand...
Click to collapse
Yeah I we hoping someone captured it before updating
xBIGREDDx said:
Hmm, I also had the developer firmware installed from their opensource site; maybe that's it? The only other thing would have been Busybox, I think...
EDIT: HEY IT WORKS! I just pulled the firmware binaries out of the update.zip, and flashed with xfstk-downloader, and now I'm on the Encrypting screen! Thanks!
Click to expand...
Click to collapse
Exactly which binaries did you flash back? In the zip I see:
dnx_fwr_ann_a0-mofd_v1.bin
dnx_fwr_ann_a0-mofd_v1-DBG.bin
dnx_fwr_blackburn_preqs_preqs.bin
dnx_fwr_blackburn_qs_qs.bin
dnx_fwr_preqs.bin
dnx_fwr_qs.bin
ifwi_ann_a0-mofd_v1.bin
ifwi_ann_a0-mofd_v1-DBG.bin
ifwi_preqs.bin
ifwi_qs.bin
I've had this pending on my phone for quite awhile, I haven't done it because I'm rooted. I decided one day to try it, my phone rebooted to TWRP and nothing happened. Which is exactly what I thought would happen. So I pulled the stock recovery from the stock rom and successfully flashed it. Tried the update again and I am getting a bit error from the stock recovery. The phone goes into "wtf just happened" mode and I have to do a battery pull and reboot. Which works fine. I don't really want to backup everything and re-root and reinstall everything, so does anyone know what my bootloader isn't seeing, but needs to see in order to push the update through?
Also, my phone isn't reading my brand new 64gb SanDisk evo suddenly. Was reading it fine last week... And ideas?
I'm on stock rooted ZV8 with sprint naval kernel.
Sent from my Sprint LG G3 sexiness via tapatalk
partitions may be zv4/zv6 on your phone? that may be why you cant do the OTA. what about dirty flashing stock rooted ZVA(not recommended, but works great for me)? there is a navel kernel for it also. Make a backup and if you dont like it, flash back? what connectivity fix does the ZVA update claim? I thought the only (LISTED) update was they added factory reset protection?
He can't take the OTA cause he has TWRP installed. OTA will only install with stock recovery. Probably will need to use the flashtool to go to complete stock if you want to receive the OTA.
Sent from my SM-G920P
Arjohns said:
He can't take the OTA cause he has TWRP installed. OTA will only install with stock recovery. Probably will need to use the flashtool to go to complete stock if you want to receive the OTA.
Sent from my SM-G920P
Click to expand...
Click to collapse
He said he put stock recovery back on, but yes he would probably need to flash completely stock to do the ota
Sent from my LGLS990 using XDA Free mobile app
Guess I should have read that better, sorry. As stated, try the rooted ZVA. OTA can be stopped due to edited build prop, debloating, etc. So complete stock through flashtool or flashing a rooted ZVA would be the only way to get to the new version.
Sent from my SM-G920P
I was trying to install a custom rom and was not aware that you can only unlock the bootloader by paying, which is fine but I can't afford it at the moment but by then I downgraded my rom.
I returned to version 9 on my phone OS and was hoping to get updates afterwards through official updates as I was restoring back to stock but I made a mistake and downloaded and installed ANE-LGRP2-OVS 9.1.0.200 which was not the correct one.
I have tried a few roms, copied to SD card in the dload folder but no matter what I try it keeps failing. No matter what I try downgrades and upgrades won't work anymore.
It seems similar to this: https://forum.xda-developers.com/t/downgrade-ane-lx3-ane-lgrp2-ovs-pie-to-oreo.3944399/
Everything does seem to work fine on my phone except the update system and google pay is not happy and not enabling contactless (which I use all the time)
Is there anything I can do to fix my dumbness
How does the dload method fail? Or is it successful in installing a different firmware yet the official update service is still broken?
Have you tried the forced dload method and did a factory reset/wipe data immediately after installation in recovery?
lemon567 said:
How does the dload method fail?
Click to expand...
Click to collapse
for several reasons .
In this specific case it is due to installing the wrong FW (ANE-LGRP2-OVS ). With this build number it is impossible to install another full stock FW or update system via OTA.
I totally forget to mention on here that I solved it. I managed to get hold of a version 8 stock rom and installed it to the SD card, then it was happy to update itself from there all the way up to current version.
I don't know why it worked at that point as I'm pretty sure I tried that same thing several times before but sometimes there are things I cannot explain, it just randomly worked all of a sudden