Database Users

[FOUND] OTA Update Link!

Just got prompted for a new update here is the link
https://android.clients.google.com/packages/incrediblec/OTA_IncredibleC_Verizon_WWE_1.22.605.2_1.22.605.0_release_sign.a33bc3bf.zip

Instructions?

if you want to install this you just downlaod it put it on the root of your sd card, than rename it to update.zip than rebbot to rcovery than select apply update.zip.
Im not saying its ok to install this, as for me i am going to wait for a bot till i can look into more.

Mirror Here

Anybody without a corp account try flashing this yet?

i flashed it today and I do NOT have the CorpEmail account. I really hope this doesn't stop me from getting root.

Gimpeh said:
Anybody without a corp account try flashing this yet?
Click to expand...
Click to collapse
i have, no differences at all. battery life will tell in a day or two

So are we safe letting update go thru? Or should we hold off if we want root?

I wouldn't flash it yet. It contains a recovery image and I don't know if anyone knows for certain what's different about the image.

Would this have the correct test keys?

I flashed. Not noticing anything unexpected. Im getting my incredible replaced anyway. Sounds like I'm listening to people talk underwater.

I doubt you'd notice anything different; I'm just afraid that they've closed a useful hole.
Now if this thing would just stop asking me every 20-30 minutes ... grrrr.

The update fixes the email client for business users.
The meat of the update they don't tell you about, however, is there is a new recovery image in the updater. So yeah, maybe a hole was closed.

I held down volume down button and hit power, booted into the prompt, selected "recovery mode," and all I got was a red triangle and exclamation point.
I downloaded the zip, renamed it update.zip, and put it on /sdcard using Astro.
Am I doing something wrong?

I have the exact same problem.

dont do it

Just checking to see if people successfully installed this OTA update from the mirror site link provided earlier in this thread. I think it's my only chance to go to FroYo without using RUU/wiping the phone.
I figure I can update from 1.22.605.0 with this update and then go to the FroYo thread and run that update. Does that sound like it will work?

This whole subject was coverd in another thread.
http://forum.xda-developers.com/showthread.php?t=770091

swindelljd said:
Just checking to see if people successfully installed this OTA update from the mirror site link provided earlier in this thread. I think it's my only chance to go to FroYo without using RUU/wiping the phone.
I figure I can update from 1.22.605.0 with this update and then go to the FroYo thread and run that update. Does that sound like it will work?
Click to expand...
Click to collapse
read the other thread, you need to update to 1.22.605.2 first, easy and does not lose date.

Root and OTA
I have rooted with unrevoked 3.1 but still have stock 2.1. Do I need to unroot to install the OTA or will the OTA still be pushed to my phone while I am still rooted?

Lost 1.141 Update

Hey folks,
maybe someone can help me.
In the morning on my A500 appeared an update available message. I tried to install it, but it failed in the middle. So I got a brick, which I solved with the chinese update. Afterwards I pushed my saved system.img.
BUT: Now the Build Number says Acer_A500_1.112. instead of Acer_A500_1.112.01_EMEA_CUS7
I checked the build.prop but there the correct build number is written.
Also another check of update gimme the message, that my system is up-to-date.
Is anyone able to provide help, like EMEA flexrom.img, boot.img, or some useful advises?

There is a EMEA signed update.zip floating around. Try to restore with that one and see what happens.

I got the same "Update" message (34MB?). I don't know if it was because mine was already rooted. D/L and updated, in the middle the dreadful Triangle with the exclamation mark pops up. Bricked! Did a reboot and try to reapply the update again..Bricked again.
Is this because I'd rooted the tablet?

gotta push flexrom
You gotta push your flexrom image onto the tablet too then "FACTORY RESET". The flexrom (mmcblk0p6) has the information of the update... that is where you are getting the difference from (if i am not mistaken)...
Try that and see if it helps ... I believe it should... jejeje

xo96 said:
I got the same "Update" message (34MB?). I don't know if it was because mine was already rooted. D/L and updated, in the middle the dreadful Triangle with the exclamation mark pops up. Bricked! Did a reboot and try to reapply the update again..Bricked again.
Is this because I'd rooted the tablet?
Click to expand...
Click to collapse
Nope, mine was rooted with gingerbreak 1.20 and worked fine.
did you delete/rename any phone apks???
or delete/rename any stock software???
I have not messed or removed anything, was rooted, root-explorer/titanium loaded and updated without issue.
reran gingerbreak afterwords and all is well....

Have never seen any OTA update in Australia :|

Wish I knew what was inside this update... media player still only sees mp4, mp3... email doesn't allow exchange... I wonder how many updates we will have to wait for to get a few of the things I want?... I didn't root so that I could load updates easily but if I have to try to fix this thing up the way I did my epic then I guess I will...shame they couldn't put divx, wmv, and some other poplar codecs in this... don't they realize some of us bought this to work with too? If exchange was added I would be sorta happy... (I love my A500 short of a couple things)

ive read the update fixes the issue with the PHONE DRAIN... but that is all, there are no other changes that I know of... jejeje

threedfreek said:
Wish I knew what was inside this update... media player still only sees mp4, mp3... email doesn't allow exchange... I wonder how many updates we will have to wait for to get a few of the things I want?... I didn't root so that I could load updates easily but if I have to try to fix this thing up the way I did my epic then I guess I will...shame they couldn't put divx, wmv, and some other poplar codecs in this... don't they realize some of us bought this to work with too? If exchange was added I would be sorta happy... (I love my A500 short of a couple things)
Click to expand...
Click to collapse
Typically I ignore posts that seem to just be complaining, but you seem real torn up about this so... go to settings, accounts, add your exchange account and be happy.

Another thing that can cause the update to hang would be any edits to your build.prop (ie. Netflix early fixes, etc). Changing back to the original resolved the triangular fail icon for me and completed the update with root still installed, gingerbreak did have to be I installed again but root is still attainable.
Sent from my A500 using XDA Premium App

Alright in my case I uninstalled some of the crapware that was on the tablet but then I try to apply the update and get the exclamation. Im assuming it cant update because of the missing apps.

fcmugen said:
Alright in my case I uninstalled some of the crapware that was on the tablet but then I try to apply the update and get the exclamation. Im assuming it cant update because of the missing apps.
Click to expand...
Click to collapse
You are correct, there is a thread in the general fourm with a link to all the apk's that came stock on the system.
I can't post links yet, but either thread about the OTA update you will find your required apk's.

mapaz04 said:
ive read the update fixes the issue with the PHONE DRAIN... but that is all, there are no other changes that I know of... jejeje
Click to expand...
Click to collapse
Full charge, 3 hours... phone 40pct... overall so far more laggy.. nice update

daveid said:
Typically I ignore posts that seem to just be complaining, but you seem real torn up about this so... go to settings, accounts, add your exchange account and be happy.
Click to expand...
Click to collapse
Alright... how long has that been there? THANKS!!!

I have the /system/app folder uploaded if u need it... Here is the link...
http://forum.ppcgeeks.com/acer-iconia-a500/143826-system-app-recovery-acer-a500-iconia-tablet.html
Sent from my T7575 using Board Express

Reset back to stock and still cant update.
Ive only had my a500 for a week. I have not removed/deleted/renamed any of the stock apps. I installed gingerbreak (to root) and thats about it. oh i changed the resolution with LCD density changer. I cant update.
So i reset back to stock and still no luck. Any ideas?

Where u @ gravy? Some people still haven't gotten the update yet. I didn't get it this morning when I tried but am hoping I get it tonite when I get home... jejeje
PS... I'm in tennessee
Sent from my T7575 using Board Express

I was having all kinds of problems not getting the update to run and kept Triangle halt..
I resolved it by the following:
you dont need to do anything with Gingerbreak, its ok. The problem is for those that changed any system files. In my case, i wanted exchange, so i was using a different email.apk, well as learned from another thread here, if you look in Cache/recovery/logs, you will see a file where you can see where the update went wrong. Like i said, in my case, i saw the file size was not what was expected for email.apk. I removed the exchange account, used rootexp and renamed email.apk.old (the original) to email.apk and the obex file then the update worked correctly.
I was going crazy as i was messing with this instead of watching my heat vs the bulls 1st half.

gravyplaya said:
Ive only had my a500 for a week. I have not removed/deleted/renamed any of the stock apps. I installed gingerbreak (to root) and thats about it. oh i changed the resolution with LCD density changer. I cant update.
So i reset back to stock and still no luck. Any ideas?
Click to expand...
Click to collapse
look at your /Cache/recovery/logs for an error and post results

I had to try about 7-8 times looking in the recovery log after each time to see what .apk that i forgot that I had deleted, then put it back and try again. I finally was successful and haven't seen much difference other than no random wake ups. Maybe a little snappier.
I had mine hang in recovery every unsuccessful update which is NOT THE SAME AS BRICKING.

My experience rooting my B80 & .21 with GUIDE

I picked this baby up as a gift for myself for being such a deserving guy for Christmas.
After reading up on the forums about the difficulties, and ASUS's hate for the modding community and their constant attempts to lock people out with the new iterations of the EEE Pad, I was in a slum. Especially after seeing I have a B80 AND updating the thing the day I received it to x.21 without knowing the implications that held for me.
So after doing some research, here's where I am now. Rooted, and running a custom ROM! And here's 'my' version of events which led to this great success. I wasn't able to use Nvflash through APX mode, due to write errors.
1. Head over to pjfriend's thread here. http://forum.xda-developers.com/showthread.php?t=1417006
Download the .19 update http://www.multiupload.com/X65RBVD2MB , extract the .zip to reveal another .zip, and place that new .zip in the root of the MicroSD card mounted inside your TF101.
2. Reboot your TF101, once it's up and running again, you'll see a triangular icon in the notification bar in the bottom right, click it to reveal an offer to update to .19.
3. After a reboot, you should be back to .19.
4. Head over to rayman84's thread. http://forum.xda-developers.com/showthread.php?t=1345049
Download Razorclaw v1.0.1 http://androidroot.mobi/download/Razorclaw_1.0.1.apk and run it. You should now have successfully rooted.
5. Time for CWM, get yourself 'Superuser' from the Market, once installed make sure you update binaries. Open Superuser application, and hit the wrench in the top right corner, and have it update binaries, under the General tab.
6. Reboot.
7. Download a ROM, I grabbed Revoler 3.11 by Gnufabio http://forum.xda-developers.com/showthread.php?t=1173230 I'd recommend it as its worked for me no problem. Pick up the regular version, NOT the Nvflash one. Place it in the root of your MicroSD card.
8. Install both Gnufabio's RecoveryInstaller http://forum.xda-developers.com/showthread.php?p=19319421
When running for the first time, it should prompt for Root Access, Confirm YES.
9. Install 'Transformer reboot to Recovery' from the Market. Once recovery is installed, reboot to recovery using the app. Scroll to install from zip, and select the .zip file of the ROM you downloaded earlier.
9. You're done! Rooted and running a custom ROM, go tell Ma' and make her proud.
THIS HAS WORKED FOR ME, IT MAY OR MAY NOT WORK FOR YOU. Who knows, might just have been the way the wind was blowing where I am. SO TRY AT YOUR OWN RISK.

great write up,

Great guide
Now if only this was possible for those with the TF101G & 8.6.6.23.

cr_972003 said:
Great guide
Now if only this was possible for those with the TF101G & 8.6.6.23.
Click to expand...
Click to collapse
Could have sworn the file was from a TF101G..
Sent from my Transformer TF101 using xda premium

Yeah it is. The problem is that it isn't considered an upgrade for the TF101G as it is already at 8.6.6.23

new way to root tf101g
Hi guys
Just for all like me who owns a b80 tf101g pad with the .23 firmware
and razorclaw unsucessful here is the solution...
al least the one that worked on my dam pad
http://forum.xda-developers.com/showthread.php?t=1427838
BIG Thanks to Jcase who found this way!!!

Awesome news...
pippo_73 said:
Hi guys
Just for all like me who owns a b80 tf101g pad with the .23 firmware
and razorclaw unsucessful here is the solution...
al least the one that worked on my dam pad
http://forum.xda-developers.com/showthread.php?t=1427838
BIG Thanks to Jcase who found this way!!!
Click to expand...
Click to collapse

Best root for stock ROM?
I want to root my B80 but and keep the stock ROM, is this the best way to root for my situation?

DougP123 said:
I want to root my B80 but and keep the stock ROM, is this the best way to root for my situation?
Click to expand...
Click to collapse
Try NachoRoot
Sent from my Transformer TF101 using Tapatalk

Fix for JSS15J Update failure!

So it appears that some people (myself included) are having issues with their new Nexus 7. Specifically, where it is failing to install the second OTA update, which brings the tablet to version JSS15J. The first update (which is almost instant) works, but the second 50+MB one fails after rebooting into stock recovery.
It is failing because the file "/system/app/PrebuiltGmsCore.apk" is failing the sha1 checksum check. Why is this happening? Because the tablet is looking for a different version of the file then what is installed on some of our tablets. Why do different people have different versions? I have no idea. But it's certainly an issue for a few people including myself. I tried various standard work arounds but came up with no fix to get the OTA update, as is, to install. Then I decided to see if that was the only issue present and develop a work around.
I'm pleased to say that:
1) The PrebuiltGmsCore.apk file is the only one that breaks the OTA update. Everything else is fine.
2) I was successful in fixing this by creating a custom OTA update zip and installing it on my tablet.
3) I'm providing this modified update.zip for people to load on their tablets if they are having the same issue.
A couple of notes first...
Obviously, flash this at your own risk.
You NEED TO HAVE A CUSTOM RECOVERY for it to work. TWRP has already been ported over, so install that first.
Once you are in custom recovery, flash this file just like any other update.
Lastly, you should only download/install this if you are having the problem where the second OTA update fails. If you are currently running JSS15J, this update will fail (as it should).
This is 98% stock OTA update. All I did was some minor tweaks to fix the issue. Specifically:
1) I removed both the check for the PrebuiltGmsCore.apk file as well as the patching of it (since this fails).
2) I took the full JSS15J version of PrebuiltGmsCore.apk and built it directly into the update.
3) I removed the parts of the OTA update that mess with custom recovery. It will not install the /system/boot-from-recovery.p or /system/etc/install-recovery.sh files.
Once you install this, your tablet should be running identically to one that didn't suffer this issue.
Outside of using this, the only other option (AFAIK) is to wait until Google releases the full factory images and flash everything manually.
A big thanks to ATGAdmin for providing the stock JSS15J system dump that let me extract the updated PrebuiltGmsCore.apk file.
So without further ado, here is the update:
http://core.routed.com/JSS15J-Update.zip
Enjoy, and let me know if you have any questions.

Question: was your nexus 7 missing the wallpaper that they've been marketing with?
Sent from my Nexus 4 using xda app-developers app

shredder47 said:
Question: was your nexus 7 missing the wallpaper that they've been marketing with?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yes.
And I bought mine from Best Buy, which seems to be a common denominator with both of those issues.
However, I just checked, and I have that wallpaper now after installing this update.

Yeah sounds like that's the common denominator... I'm out right now but I'll try this out when I get home, thanks man!
Sent from my Nexus 4 using xda app-developers app

Thanks so much! This worked for me after trying other options failed. Mine was from Best Buy also.

Oh, one other quick note:
As I wanted to leave this as close to the stock OTA update as possible, this WILL remove root. Technically, the 'su' binary will remain, but it will lose it's suid permissions. It will also remove the daemon launcher (which is installed as the install-recovery.sh file).
So make sure to flash the root zip after installing this update.
One more thing:
While there aren't many mods out there yet that will mess with the update, eventually there will be. This custom update will check and verify that everything else (except that one file) is stock. So if you made any other modifications to any other system file (ie: build.prop, etc.), it will fail just like any other OTA. Your best bet is to install this before tweaking.

Worked great man!
Also, your download was rather slow so if you don't mind I made a mirror on mega: https://mega.co.nz/#!aE4CwJZB!J7QtUlqXhthhZcpPOUriaQ_u861k7rAGdHffRCmkQao

I have one from best buy and it updated just fine (both updates). I guess it's just luck of the draw.
Sent from my Nexus 7 using Tapatalk HD

Nburnes said:
Worked great man!
Also, your download was rather slow so if you don't mind I made a mirror on mega: https://mega.co.nz/#!aE4CwJZB!J7QtUlqXhthhZcpPOUriaQ_u861k7rAGdHffRCmkQao
Click to expand...
Click to collapse
Awesome, glad to hear! And sure, that's perfectly fine with me.
It's on a 100Mb pipe, but the data center occasionally has some bad routing that makes certain destinations slow. Can't complain since I get a dedicated server for $59/month .

fosser2 said:
I have one from best buy and it updated just fine (both updates). I guess it's just luck of the draw.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Yeah, I believe it to be a minority of tablets. Maybe just a bad batch that all happened to get sent to Best Buy. As time goes on and more people get them we'll see how wide spread it is. I'm curious to see what Google's official fix will be.

Yeah, got mine from best buy too, the 2nd update stood at the boot screen. I just rebooted and it's back to normal
Sent from my Nexus 4 using Tapatalk 4 Beta

paranoid android85 said:
Yeah, got mine from best buy too, the 2nd update stood at the boot screen. I just rebooted and it's back to normal
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Did you check to see if the update worked? If your version is still JWR66N, then it failed and you will either need to flash this or wait for an official fix from Google.

phonic said:
Did you check to see if the update worked? If your version is still JWR66N, then it failed and you will either need to flash this or wait for an official fix from Google.
Click to expand...
Click to collapse
I brick my nexus. Can someone upload nandroid backup please?

phonic said:
... Why is this happening? Because the tablet is looking for a different version of the file then what is installed on some of our tablets. Why do different people have different versions? I have no idea. But it's certainly an issue for a few people including myself. ...
Click to expand...
Click to collapse
Interesting. My update worked (mostly because oldblue910 was doing it). LOL
I got mine at Walmart and noticed one of the box labels had been modified. There is an extra label covering one label on the box (also, there are labels on both ends). It is barely noticeable. I tried to remove the one on top (to peek) but it started to tear.
I theorize mine was part of a modification process. Do you think some of those failed units at Best Buy *might* have missed the modification process?

Bob Smith42 said:
Interesting. My update worked (mostly because oldblue910 was doing it). LOL
I got mine at Walmart and noticed one of the box labels had been modified. There is an extra label covering one label on the box (also, there are labels on both ends). It is barely noticeable. I tried to remove the one on top (to peek) but it started to tear.
I theorize mine was part of a modification process. Do you think some of those failed units at Best Buy *might* have missed the modification process?
Click to expand...
Click to collapse
I'm not really sure. After looking at the first OTA update that oldblue910 posted, it definitely indicates that it was modified by that. If so, it had to have initially passed that first check. Why some units fail the second check makes little sense to me. The lack of the official wallpaper is also weird.
Additionally, that first OTA clearly shows that these devices were rushed. The fact that they were sent out with developer keys is just really bad QA.
My device, hardware wise, seems to be perfect. So I don't want to roll the dice and try to get another one, especially if the only issue is some minor software glitch that I already corrected. I haven't had a chance to really play with it yet, as I've been spending my time backing up/restoring files, so I'll see how it goes.

Thanks for this. Bought mine at Best Buys too and had the update fail.
Edit: TWRP gave the option to fix SU after flashing that zip and it seemed to work. I'll probably refresh zip anyways but TB still works.
Sent from my Nexus 4 using Tapatalk 4 Beta

stab244 said:
Thanks for this. Bought mine at Best Buys too and had the update fail.
Edit: TWRP gave the option to fix SU after flashing that zip and it seemed to work. I'll probably refresh zip anyways but TB still works.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yes, you should reapply the root zip.
The OTA update does two things in this regard. It removes the two 'recovery recovery' files, and it also removes the suid bit from the su binary. The TWRP su fix will reapply the suid bit to 'su' (thus making it actually work), but it doesn't put back the SuperSU daemon launcher (/system/etc/install-recovery.sh). By applying the root zip again, it will fix both of these.
I thought about removing the part of the update that deletes this file, but again I wanted to keep it as stock as possible. Also, for people who hadn't rooted yet but do have a custom recovery, it would help keep it custom and not require them to manually remove those files that would (stock) reset the recovery back.

I also purchased mine at Best Buy, therefore I also have the problem.
What exactly does this 2nd update do? Is it a drastic improvement over JWR66N?

xene97 said:
I also purchased mine at Best Buy, therefore I also have the problem.
What exactly does this 2nd update do? Is it a drastic improvement over JWR66N?
Click to expand...
Click to collapse
If you are asking what files it changes, you can look inside the zip file and see all of that. It's fairly extensive. The vast majority are patches to many components of the operating system and included applications. The first OTA update was only a few hundred kilobytes, while this one is 50megs, so a lot was updated.
If you are asking what the end-user result or benefit is between the two, I am not sure. I spent most of my time working on trying to get the update working, and spent very little time using the tablet before I was successful. So I can't comment about whether the update improves anything. However, others have said that it did help to resolve some issues they experienced before hand.
In any case, the new N7 was released quite quickly and we know that the factory installed OS had some issues. The fact that there were two OTA updates before the device was even released show that Google needed to fix a lot of stuff. While future updates (Key Lime Pie anyone?) will be more optional as it focuses on enhancements and upgrades, these two updates are significantly more important.

phonic said:
If you are asking what files it changes, you can look inside the zip file and see all of that. It's fairly extensive. The vast majority are patches to many components of the operating system and included applications. The first OTA update was only a few hundred kilobytes, while this one is 50megs, so a lot was updated.
If you are asking what the end-user result or benefit is between the two, I am not sure. I spent most of my time working on trying to get the update working, and spent very little time using the tablet before I was successful. So I can't comment about whether the update improves anything. However, others have said that it did help to resolve some issues they experienced before hand.
In any case, the new N7 was released quite quickly and we know that the factory installed OS had some issues. The fact that there were two OTA updates before the device was even released show that Google needed to fix a lot of stuff. While future updates (Key Lime Pie anyone?) will be more optional as it focuses on enhancements and upgrades, these two updates are significantly more important.
Click to expand...
Click to collapse
Thanks for the clarification!

OTA push

OK, I must have inadvertantly started OTA and got the must install / delay screen pop up. I froze the smaller update system app to rid the pop up, and removed the update.zip package.
So far 2 weeks of reboots and use age no OTA package installer pop ups.

Is that for your I467 model and are you blocking the KitKat update, or a different model?

On both types... I am not dissabling OTA, as I may want to install 4.4.2 later. Just keeping the blasted install update notice from popping up every so often. It does not effect downloads or app installs, just keeps the notice from being a pain in the arse.

Do you happen to still have the 4.4.2 update.zip file?
@muniz_ri is trying to help us get root on 4.4.2 but he needs the 4.4.2 update.zip file for the i467.
If you have the file would you be willing to post a link so we can download it and work on rooting it?

dandroid7 said:
Do you happen to still have the 4.4.2 update.zip file?
@muniz_ri is trying to help us get root on 4.4.2 but he needs the 4.4.2 update.zip file for the i467.
If you have the file would you be willing to post a link so we can download it and work on rooting it?
Click to expand...
Click to collapse
Not for the i467 as I never connected with AT&T, just rooted and unlocked to use Virgin UK. Though I froze the software update to mirror my GT-N5110 settings.

OK thanks for the response

dandroid7 said:
OK thanks for the response
Click to expand...
Click to collapse
Sent you a message

gooberdude said:
On both types... , just keeps the notice from being a pain in the arse.
Click to expand...
Click to collapse
I thought I had read somewhere that you had both models, it was a pain.
I just couldn't remember how I stopped my pop-up, thanks you.
Quote godzulu
If you have the file would you be willing to post a link so we can download it and work on rooting it?
I'm sure that I have yet to complete a download of the OTA for I467. For years I'd preferred a custom Rom or kernel vs a carrier update - with that being said, how can I Download it & then STOP the installation (i do not want the update without root) & next, locate the zip to get it to you?
I would already guess that you and others have already tried.
***********************
It looks like someone had passed the file along & maybe Da_G is attempting a a workaround, yea!

OK, I realized that I had changed the option in about device to set auto update. If you go into app manager, and clear cache and data in both software update apps, you will reset parameters for FOTA. The nice thing about doing so on the GT-N5110, is that you can select world ROMs. UK GB is what I use, as it has 13 channel WIfI already set.
If you choose automatic, you will get a notice and will ask to install once the download iscompleted. if you do it manually, it will download when you select download.... but you can cancel.
The Firmware is located in System/cache/update, and the fle is update.zip.
If you like to mess with a library of ROMs, you can download as many as you like after renaming and moving them to SD.
As for rooting... Saferoot.zip works fine. there are a few topics that have it downloadable. just search in the Note 8.0 general and Q&A sections.