just wanted to share the original recovery image that came with the phone for anyone that is trying to get the update but dont want to have to restore their phone with kdz/tot file. just push this image to your device via adb. if you have supersu as your root, in the options of supersu you can do a clean uninstall and completely get rid of root with it. then take the OTA update so you dont have any problems with the update. or if you want to keep root you dont have to uninstall it. it seems after the 4.4.2 update, root is still there. enjoy.
d800 stock recovery
freebee269 said:
just wanted to share the original recovery image that came with the phone for anyone that is trying to get the update but dont want to have to restore their phone with kdz/tot file. just push this image to your device via adb. if you have supersu as your root, in the options of supersu you can do a clean uninstall and completely get rid of root with it. then take the OTA update so you dont have any problems with the update. or if you want to keep root you dont have to uninstall it. it seems after the 4.4.2 update, root is still there. enjoy.
d800 stock recovery
Click to expand...
Click to collapse
I'm assuming we would push this using ADB? Is there a quick guide for that? I haven't manually installed a recovery in forever.
Are you sure your root was still working after the update? On every other device I have updated to Kitkat, the Superuser app was still there, but you couldn't update the binaries. Something changed with 4.4 that makes the old root method not work. Apparently, Superuser has to be flashed every single time you update from 4.4 on. At lest, that's what I read when I was updating my Nexus and Moto X.
PLEASE READ ENTIRE THREAD BEFORE ATTEMPTING!! I AM NOT RESPONSIBLE FOR ANY DAMAGE
FILE WAS DOWNLOAD FROM AT&T VIA OTA UPDATE FROM MY MEGA & EXTRACTED FROM THERE - I527UCUBNE7 CFG FILE OTA UPDATE
I only recommend running adb sideload to install.
ADB SIDELOAD DETAILED INSTRUCTIONS
- Make sure USB debugging is ENABLED
- Reboot device into recovery
- Plug device into computer
- Select adb sideload from your devices recovery screen (drivers might need to install, wait for this and then continue)
- load up command prompt for adb
From here I will give examples (adjust according where your file is stored)
As example say I saved my file in my documents folder this would be the command to sideload
adb sideload c:/users/owner/my documents/ATT OTA 4.4 UPDATE.cfg .............you can rename the file whatever you want but I changed the name for confusion as to what it was.
The file will start to load onto the device and show percentage in adb until upload is complete. Once the file is loaded your device will start the update process. If it fails it will show where it stopped at most likely being that a factory file is missing or changed. Everything must be original from previous mr2 firmware.
AGAIN IF YOU REMOVED, MODIFIED, FROZE APPS LIKE KNOX MOST LIKELY YOUR UPDATE WILL FAIL AFTER 25-30%. FOR BEST RESULTS YOUR ROM MUST HAVE ALL ORIGINAL FILES. THIS UPDATE SCANS YOUR FILE SYSTEM TO ENSURE NOTHING HAS BEEN CHANGED. ANY CHANGE WILL CAUSE A FAILURE.
IF YOU GET AN ERROR DURING UPDATE - INSTALL INSTRUCTIONS IF YOU GET AN ERROR
- Download mr2.tar.md5 file located in my signature under galaxy mega repository
- Install via Odin & make sure "Auto-Reboot" is UN-CHECKED
- Once install is finished reboot device into recovery
- Select adb sideload install then follow the steps above to install update via sideload
THIS UPDATE IS NOT ROOTED OR UNLOCKED. INSTALLING WILL CAUSE YOU TO LOOSE ROOT!!
IF YOURE NOT SURE WHAT YOUR DOING - DONT DO IT - RECOMMEND REMOVING BUSYBOX - ROOT BEFORE INSTALL -
AT&T I527UCUBNE7 OTA UPDATE - CFG FILE - DROPBOX CURRENTLY DOWN DUE TO CONGESTION
- GOOGLE DRIVE LINK - I527UCUBNE7 OTA UPDATE - GOOGLE DRIVE LINK -
- MEGA LINK - I527UCUBNE7 OTA UPDATE - MEGA LINK -
AGAIN USE AT YOUR OWN RISK.
Can I remove apps and flash?
updated no problems but now i have no touch on the screen. no buttons light up or nothing. has anybody else ran into this problem.
thanks
hedgehogmd said:
updated no problems but now i have no touch on the screen. no buttons light up or nothing. has anybody else ran into this problem.
thanks
Click to expand...
Click to collapse
did you run update while your phone was rooted?
KDKobes said:
did you run update while your phone was rooted?
Click to expand...
Click to collapse
No i did a full system reload with Odin then applied the OTA. everything went fine no errors rebooted and no touch.
hedgehogmd said:
No i did a full system reload with Odin then applied the OTA. everything went fine no errors rebooted and no touch.
Click to expand...
Click to collapse
I have seen this happen before. Which "full system reload file" did you use and where was it downloaded? Usually is fixed by re-installing a lower version rom then reapplying the update. I would recommend reinstalling the official rom if thats what you used if you can. This would be the mr2 tar.md5 file in odin. Which way did you install update? Did you try reinstalling the update?
*currently uploading stock official att mr2.tar.md5 to my repository. File should be up shortly*
KDKobes said:
I have seen this happen before. Which "full system reload file" did you use and where was it downloaded? Usually is fixed by re-installing a lower version rom then reapplying the update. I would recommend reinstalling the official rom if thats what you used if you can. This would be the mr2 tar.md5 file in odin. Which way did you install update? Did you try reinstalling the update?
*currently uploading stock official att mr2.tar.md5 to my repository. File should be up shortly*
Click to expand...
Click to collapse
i replaced the screen about 4 months ago with a aftermarket lcd assy and i had to hookup my cracked factory screen boot phone the plug in my aftermarket screen and touch works.
My phone is unlocked. If I do this, what are the chances I lose that unlock?
I updated to 4.2.2 via Kies and didn't lose the unlock, so curious about this.
kwed73 said:
My phone is unlocked. If I do this, what are the chances I lose that unlock?
I updated to 4.2.2 via Kies and didn't lose the unlock, so curious about this.
Click to expand...
Click to collapse
I updates and didn't lose my unlock
Is someone working on a odin version of this update
Great!
Wow..... I have been here and there before I got here. It worked flawlessly!
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 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.