OK, so i am rooted and have TWRP. The OTA update keeps failing to install and I cannot see the error because it goes away so fast. Is this because I have a custom recovery?
thanks,
aaronc_98 said:
OK, so i am rooted and have TWRP. The OTA update keeps failing to install and I cannot see the error because it goes away so fast. Is this because I have a custom recovery?
thanks,
Click to expand...
Click to collapse
Hi, aaronc_98...
Short answer is 'yes'.
You need to be running 100% unmodified official factory stock for a Google OTA to work.
Any deviation from factory stock, such as a custom recovery, as well as the root su binary and the SuperSU app will likely cause the OTA to abort, and with no changes made.
Rgrds,
Ged.
Related
I've been on stock rooted ROM (MDK) for longest time w/ CWM recovery. I decided I wanted to get back on the update track after this recent update came out and is already rooted. I defrosted all apps, unrooted the device with Voodoo OTA rootkeeper, and uninstalled SuperSU. I then flashed stock firmware with Odin as explained here: http://forum.xda-developers.com/showthread.php?t=2301259
This didn't work. I get an error during install every time. After this I noticed when going into recovery (now stock) it would have an error immediately but then went into recovery. It would not let me clear the cache (after searching this seems to be common.) So I then did factory reset multiple times (didn't help) and next flashed a stock firmware that wipes my data. This had the same results as before. Do I have a corrupt recovery of some kind? Shouldn't flashing the stock firmware fix this? Do I need to get a new phone? Help!
zregnier said:
I've been on stock rooted ROM (MDK) for longest time w/ CWM recovery. I decided I wanted to get back on the update track after this recent update came out and is already rooted. I defrosted all apps, unrooted the device with Voodoo OTA rootkeeper, and uninstalled SuperSU. I then flashed stock firmware with Odin as explained here: http://forum.xda-developers.com/showthread.php?t=2301259
This didn't work. I get an error during install every time. After this I noticed when going into recovery (now stock) it would have an error immediately but then went into recovery. It would not let me clear the cache (after searching this seems to be common.) So I then did factory reset multiple times (didn't help) and next flashed a stock firmware that wipes my data. This had the same results as before. Do I have a corrupt recovery of some kind? Shouldn't flashing the stock firmware fix this? Do I need to get a new phone? Help!
Click to expand...
Click to collapse
i dont think you can update with an unlocked recovery... if you have cwm you have an unlocked recovery and i dont think you can relock it.
also you dont need to update if you have cwm then all you need to do is flash a MI1 rom (once they come out) and youre good. there is NO reason you would need to ACTUALLY update. you can flash pretty much everything whilst still keeping unlocked recovery under actual MDK firmware but with MI1 (or ME7) rom kernel and radios.
zregnier said:
I've been on stock rooted ROM (MDK) for longest time w/ CWM recovery. I decided I wanted to get back on the update track after this recent update came out and is already rooted. I defrosted all apps, unrooted the device with Voodoo OTA rootkeeper, and uninstalled SuperSU. I then flashed stock firmware with Odin as explained here: http://forum.xda-developers.com/showthread.php?t=2301259
This didn't work. I get an error during install every time. After this I noticed when going into recovery (now stock) it would have an error immediately but then went into recovery. It would not let me clear the cache (after searching this seems to be common.) So I then did factory reset multiple times (didn't help) and next flashed a stock firmware that wipes my data. This had the same results as before. Do I have a corrupt recovery of some kind? Shouldn't flashing the stock firmware fix this? Do I need to get a new phone? Help!
Click to expand...
Click to collapse
I would try using the me7 factory image that wipes everything and then try the upgrade.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
---------- Post added at 09:21 PM ---------- Previous post was at 09:19 PM ----------
reinaldistic said:
i dont think you can update with an unlocked recovery... if you have cwm you have an unlocked recovery and i dont think you can relock it.
also you dont need to update if you have cwm then all you need to do is flash a MI1 rom (once they come out) and youre good. there is NO reason you would need to ACTUALLY update. you can flash pretty much everything whilst still keeping unlocked recovery under actual MDK firmware but with MI1 (or ME7) rom kernel and radios.
Click to expand...
Click to collapse
There is no unlocked bootloader on the s4 what allows the installation of custom recovery is the loki exploit and its reversible.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
hexitnow said:
[/COLOR]
There is no unlocked bootloader on the s4 what allows the installation of custom recovery is the loki exploit and its reversible.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Click to expand...
Click to collapse
Thus the word think but thanks for the info...
hook the guy up with the link for reversing loki then
reinaldistic said:
Thus the word think but thanks for the info...
hook the guy up with the link for reversing loki then
Click to expand...
Click to collapse
There is no link or post on it really. Its a patched recovery and boot image so when you odin back to a factory image they get replaced with the non patched versions
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
zregnier said:
I've been on stock rooted ROM (MDK) for longest time w/ CWM recovery. I decided I wanted to get back on the update track after this recent update came out and is already rooted. I defrosted all apps, unrooted the device with Voodoo OTA rootkeeper, and uninstalled SuperSU. I then flashed stock firmware with Odin as explained here: http://forum.xda-developers.com/showthread.php?t=2301259
This didn't work. I get an error during install every time. After this I noticed when going into recovery (now stock) it would have an error immediately but then went into recovery. It would not let me clear the cache (after searching this seems to be common.) So I then did factory reset multiple times (didn't help) and next flashed a stock firmware that wipes my data. This had the same results as before. Do I have a corrupt recovery of some kind? Shouldn't flashing the stock firmware fix this? Do I need to get a new phone? Help!
Click to expand...
Click to collapse
I to am having same exact problem but im on me7 and was safstrapped????????
The advice from @hexitnow worked! I downloaded ME7 image here http://forum.xda-developers.com/showthread.php?t=2357235
It worked fine then I took the latest OTA. Thanks guys!:good:
Quick Qestion
I have a quick question, and i dont want to make a who new thread about it. But since we already talkin about it on here, is it worth it to do this Verizon update?? I just did a Verizon update 2 days ago. And now to me i think it just aggitated me. My Email are different now. My delete button moved and it added more buttons. And my task manager seems a lil different. Cant seem to put my finger on it.. But its weird. What else has changed? Was it even worth doing an update?
I'm trying to install the latest update but it keeps failing. It says "downloading" for hours and hours but nothing ever happens. I'm on ME7 (or whatever it is) so the phone is rooted but no recovery is installed. I'm hoping to figure it out before the 4.3 update. I searched but did not see this problem posted. Any ideas?
lithium630 said:
I'm trying to install the latest update but it keeps failing. It says "downloading" for hours and hours but nothing ever happens. I'm on ME7 (or whatever it is) so the phone is rooted but no recovery is installed. I'm hoping to figure it out before the 4.3 update. I searched but did not see this problem posted. Any ideas?
Click to expand...
Click to collapse
If you want the update just flash it with Odin. Or use voodoo root keeper to try and keep root. To get the OTA to take the phone must be in stock form. Which means no system apps have been frozen or deleted.
http://forum.xda-developers.com/showthread.php?t=2301259
Travisdroidx2 said:
If you want the update just flash it with Odin. Or use voodoo root keeper to try and keep root. To get the OTA to take the phone must be in stock form. Which means no system apps have been frozen or deleted.
http://forum.xda-developers.com/showthread.php?t=2301259
Click to expand...
Click to collapse
Thank you for the quick reply. I have not done much with the phone yet so I have not seen ODIN. Hopefully 4.3 is released soon like the rumors suggest.
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 been thinking about reversing the CM12 install so I can play with the B320 or B321 updates. The problem is, I'm not certain of the reversal process. Do I have this right?
flash B148 via the dload method
FLash B309 via the dload method
Flash the B320 via the dload method
I'm sure I must be missing interim steps. Could someone list out the necessary steps?
After flashing stock recovery. Flash 309. Don't really need 148.
I'm going to ask a stupid question so brace yourself. :laugh: Isn't b148 the stock recovery?
Bill R said:
I'm going to ask a stupid question so brace yourself. :laugh: Isn't b148 the stock recovery?
Click to expand...
Click to collapse
B148 is the rom itself. Recovery can be stock. Or twrp.
If you did a backup of you Hauwei's stock rom couldn't you just restore from that using TWRP?
robertbarber said:
If you did a backup of you Hauwei's stock rom couldn't you just restore from that using TWRP?
Click to expand...
Click to collapse
Yep.
Ok, now I understand. I went through three pages and could not find a download for the stock recovery. Is there a link?
Never mind. Found the stock recovery here:
http://forum.xda-developers.com/showpost.php?p=55617080&postcount=7
Then remembered I had made a backup prior to loading CM so it should be at least 309. I'll still have to flash the stock recovery to get from B309 to B320 correct?
yes, if its b309, I think you have to install b320 pkg locally using stock recovery. last time for me, I cannot see b321 ota when mine is b309, i must first 'bring' it to b320 in order to see b321 ota.
xordos said:
yes, if its b309, I think you have to install b320 pkg locally using stock recovery. last time for me, I cannot see b321 ota when mine is b309, i must first 'bring' it to b320 in order to see b321 ota.
Click to expand...
Click to collapse
That's what I ended up doing. TWRP restore to B309 then flashed the stock recovery, then flashed B320. I haven't registered my EMIE number yet as I'm not sure if I'm going to stay with the stock lollipop.
One interesting note; when I flashed B320, I had to facotroy reset 3 times because every time when it came to restoring my apps, it would, like, time out and flash past it. The fourth time I was ready for it.
I was at work so I never got a chance to capture the D/L. It was small, around 4MB. Anyone else see it?
Probably the Nov security update posted here
McChen147 said:
november security update:
https://android.googleapis.com/pack...5f522d.signed-volantis-MRA58N-from-MRA58K.zip
Click to expand...
Click to collapse
Can install with root?
TWRP Failed to install
edgardo_0691 said:
Can install with root?
TWRP Failed to install
Click to expand...
Click to collapse
When I flashed Marshmallow, I went back to unrooted. So the OTA worked fine, but not sure if you can stall with Root.
No.
edgardo_0691 said:
Can install with root?
TWRP Failed to install
Click to expand...
Click to collapse
OTA Update
I am also unable to install the update however I am on Marshmallow 6 and every time I boot up my device it tells me that the device is untrusted.
is this part of a larger issue?
ImzTinoz said:
I am also unable to install the update however I am on Marshmallow 6 and every time I boot up my device it tells me that the device is untrusted.
is this part of a larger issue?
Click to expand...
Click to collapse
This is normal. The warning is displayed because you have modified your device. It means nothing for the functionality of your tablet.
You cannot use the OTA update if your system is modified. You must be stock unrooted, unless you used the systemless root method in which case you need to restore stock recovery and kernel, then OTA will work.
This zip is not meant to be flashed in TWRP, it's the official OTA update which needs the stock recovery and completely unmodified /system partition.