I turned on my kids KFHD today and saw a lock screen ad, which I had eliminated when I rooted the device. I went to titanium backup and, sure enough, no root anymore. Voodoo didnt keep it. I used a method on XDA to root in the first place but IDK if it will still work on 8.3.0 (doubt it) and I dont feel like doing a data wipe right now to find out. Does anyone know to regain root on this version? Its only a few hours old and I havent seen anything about it yet.
ecopunk said:
I turned on my kids KFHD today and saw a lock screen ad, which I had eliminated when I rooted the device. I went to titanium backup and, sure enough, no root anymore. Voodoo didnt keep it. I used a method on XDA to root in the first place but IDK if it will still work on 8.3.0 (doubt it) and I dont feel like doing a data wipe right now to find out. Does anyone know to regain root on this version? Its only a few hours old and I havent seen anything about it yet.
Click to expand...
Click to collapse
I was able to get it re-rooted, but it took two tries before it finally worked.
You can reflash 8.1.4, and then run Chris/Prokennexusa's OTA-Update-Defeat script to kill the update services. My 8.9 survived Amazon's OTA update and remained on 8.1.4, rooted, with Hashcode's bootloader intact. Chris's defeat script works!
Hashcode reviewed the update the and major change was to plug the security hole that allows us to use an alternate bootloader and flash new operating systems.
Nestaron said:
I was able to get it re-rooted, but it took two tries before it finally worked.
Click to expand...
Click to collapse
Using what method? Same as 8.1.4 or something else?
Slimepuppy said:
You can reflash 8.1.4, and then run Chris/Prokennexusa's OTA-Update-Defeat script to kill the update services. My 8.9 survived Amazon's OTA update and remained on 8.1.4, rooted, with Hashcode's bootloader intact. Chris's defeat script works!
Hashcode reviewed the update the and major change was to plug the security hole that allows us to use an alternate bootloader and flash new operating systems.
Click to expand...
Click to collapse
Thanks, might have to do that.
I rooted 8.3.0 with the same method I rooted 8.14 with.
It still works, because it's a bug in ICS that hasn't been patched.
Just saw this. I didn't check the version on mine until now. It's on 8.3, and has been rooted since I brought it home on Wednesday. I did it Wednesday night and if it updates overnight it kept root.
If not, it was on 8.3 the whole time.
gunnyman said:
I rooted 8.3.0 with the same method I rooted 8.14 with.
It still works, because it's a bug in ICS that hasn't been patched.
Click to expand...
Click to collapse
gsu_golfer said:
Just saw this. I didn't check the version on mine until now. It's on 8.3, and has been rooted since I brought it home on Wednesday. I did it Wednesday night and if it updates overnight it kept root.
If not, it was on 8.3 the whole time.
Click to expand...
Click to collapse
Thank you all! I will backup and go again tomorrow or the next dayand post the results
gunnyman said:
I rooted 8.3.0 with the same method I rooted 8.14 with.
It still works, because it's a bug in ICS that hasn't been patched.
Click to expand...
Click to collapse
+1 same here
bighead2k said:
+1 same here
Click to expand...
Click to collapse
Mine has not worked - I am using bin4ry tool v26. What did you use?
gooseacre said:
Mine has not worked - I am using bin4ry tool v26. What did you use?
Click to expand...
Click to collapse
I used bin4ry tool v25, It wasn't rooted, but I can install playstore, go laucher!
Went out of town and forgot to post back here. I did re-root with the original method and it DID work! I backed it up but I was surprised to find that all my data, apps, even passwords, etc were all still there after re-rooting (even after the supposed data restore) and were all working but I had regained root! The only thing missing were the kindle Books selections. Not a bad tradeoff!
gooseacre said:
Mine has not worked - I am using bin4ry tool v26. What did you use?
Click to expand...
Click to collapse
haovpi said:
I used bin4ry tool v25, It wasn't rooted, but I can install playstore, go laucher!
Click to expand...
Click to collapse
This is what I used on both firmware versions
http://forum.xda-developers.com/showthread.php?t=1886460
no such thing as a root keeper
Not f'realz anyways. I'm on 8.3.1; gotten used to rooting the same way, THAT is nice. I initially had to fiddle w/ADB, windows 8 doesn't initially allow unsigned drivers. There's a proceedure for that. After that was fixed, the b1nary root works like a boss ...
The kindle fire first aid works well for market installation (make sure to install busy box first, b1nary root didn't, and that's easy). OTA blocking works well, I forget what I used. My update to 8.3.1 was intentional
Seems a more stable update. In fact, all the updates seem worth-while: google maps didn't gps track w/1st version, with silk installed couldn't watch amazon vod. A lot of quirks seem to be fixed, google play store and amazon app store seem to be playing well together.
---------- Post added at 08:57 AM ---------- Previous post was at 08:47 AM ----------
ecopunk said:
Went out of town and forgot to post back here. I did re-root with the original method and it DID work! I backed it up but I was surprised to find that all my data, apps, even passwords, etc were all still there after re-rooting (even after the supposed data restore) and were all working but I had regained root! The only thing missing were the kindle Books selections. Not a bad tradeoff!
Click to expand...
Click to collapse
Hey, fyi when you reroot, go into app settings after and clear data on the Amazon apps like Kindle, Silk, or VOD. My stuff doesn't show up even on the "cloud" if I don't do that. You'll have to redownload media, so that might stink. Not really, imo.
Related
here is the amazon latest update 6.2.1
https://t.co/BRUE4vHR
Any expert wants to help out those have updated their kindle fire to 6.2.1?
My coworker bought a Kindle Fire for his mother and want's me to prepare it for her as a Christmas gift (she wants Android so we decided to install the Android Market). I took it home the other day and noticed a message saying that it was updating itself. The system version says "6.2_user_3003020"
Is this 6.2.1? It's doesn't say 6.2.0, so I don't want to make any assumptions.
have u tried zergrush from this post? not sure if its the same exploit or not, but try it
http://forum.xda-developers.com/showthread.php?p=20288923
sent from my kindle fire
CZroe said:
My coworker bought a Kindle Fire for his mother and want's me to prepare it for her as a Christmas gift (she wants Android so we decided to install the Android Market). I took it home the other day and noticed a message saying that it was updating itself. The system version says "6.2_user_3003020"
Is this 6.2.1? It's doesn't say 6.2.0, so I don't want to make any assumptions.
Click to expand...
Click to collapse
That is version 6.2
You need to make sure that WiFi is OFF until you protect it from getting further updates. There are a number of theads on how to do that.
o Modified hosts file to block: 127.0.0.1 s3.amazonaws.com
o Installed TWRP 2.0, FIREFIREFIRE and u-boot (was done via a package)
o Renamed /system/app/OTASilentInstall.apk to /system/app/OTASilentInstall.apk.bak
Any of which will prevent further updates. You needed to be rooted to do any of these however. One method that people are using is:
http://forum.xda-developers.com/showthread.php?t=1399889
Still, an exploit needs to be found for stock KF that will be coming with 2.6.1 and higher. I'm pretty sure we are going to be able to download and patch future stock Roms for those that don't want to go to cm7 or cm9 when it is ready.
And for people like me who had root, and got the silent update, not thinking I would lose root!
ATM, my guess is that a factory cable is required to put it into fastboot to restore root.
Yes, I would think Vashypooh is right. If you can get fastboot access, one could possibly gainroot, or maybe flash an already rooted Rom.
Have anybody tried to remove the OTASilenInstaller.apk from the system/app?
Aw damnit, it just updated on me. So I can't reroot using the old methods?
kweng_ca said:
Aw damnit, it just updated on me. So I can't reroot using the old methods?
Click to expand...
Click to collapse
No, nothing works at this point, until someone figures out a new way to gain root. No telling how long that could take. I'll say one thing, I'm putting CM7 on mine as soon as I get it rerooted. I don't like having a surprise lockdown on my device.
kweng_ca said:
Aw damnit, it just updated on me. So I can't reroot using the old methods?
Click to expand...
Click to collapse
Had you bychance renamed the OTA file or redirected a3.amazonaws.com?
Sent from my Kindle Fire using xda premium
Ectoplasmic said:
No, nothing works at this point, until someone figures out a new way to gain root. No telling how long that could take. I'll say one thing, I'm putting CM7 on mine as soon as I get it rerooted. I don't like having a surprise lockdown on my device.
Click to expand...
Click to collapse
this is why i did this yesterday!
sent from my kindle fire
borborpa said:
Had you bychance renamed the OTA file or redirected a3.amazonaws.com?
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
No sir, guess it's just a waiting game for me now
borborpa said:
Had you bychance renamed the OTA file or redirected a3.amazonaws.com?
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
I
I had the sneakyOTA.apk (or whatever it was called) UNINSTALLED!!! and still got updated to 6.2.1 Monday night. Many of those self-righteous folks who are sayin' 'ah, but I froze/renamed the .apk' will soon have a fancy e-reader. Just watch!
kweng_ca said:
No sir, guess it's just a waiting game for me now
Click to expand...
Click to collapse
I have faith in the brilliance of xda community members ... the rooting method will be available tomorrow
I had the same thing happened to me. Apparently renaming or freezing ota is not enough
Sent from my Kindle Fire using Tapatalk
charmainelooi said:
I have faith in the brilliance of xda community members The rooting method will be available tomorrow.
Click to expand...
Click to collapse
I agree with that 100%
charmainelooi said:
I have faith in the brilliance of xda community members ... the rooting method will be available tomorrow
Click to expand...
Click to collapse
Is it done yet? Why is it taking so long?
I bought two KFs for my kids, rooted, adw, happened, twrm. Froze otainstall.apk and one updated.
At least market still works and adw is still default.
Bummer is that I helplessly watched twrm flash the update.
Sent from my SCH-I510 using Tapatalk
Hi all,
I normally live over on the Xperia Arc forum but I have been trying to root my mums Kindle.
Last time I looked it was on 10.2.4 which, as far as I have read, is rootable.
However last night I checked the version again just before I commenced rooting and it was on 10.2.5!
I cant seem to find any reference of .5 anywhere.
Even on amazons website the latest update says 10.2.4
I tried the root methods but it didnt work unfortunately...
Any ideas? Anyone else been updated to .5 and successfully rooted?
yo-meister said:
Hi all,
I normally live over on the Xperia Arc forum but I have been trying to root my mums Kindle.
Last time I looked it was on 10.2.4 which, as far as I have read, is rootable.
However last night I checked the version again just before I commenced rooting and it was on 10.2.5!
I cant seem to find any reference of .5 anywhere.
Even on amazons website the latest update says 10.2.4
I tried the root methods but it didnt work unfortunately...
Any ideas? Anyone else been updated to .5 and successfully rooted?
Click to expand...
Click to collapse
Unlucky mate. Ur the first I've heard having .5 kf. Did u try over HD forum. More devas over there or the general chat forum
Sent from my Amazon Kindle Fire2 using xda app-developers app
willieboya said:
Unlucky mate. Ur the first I've heard having .5 kf. Did u try over HD forum. More devas over there or the general chat forum
Sent from my Amazon Kindle Fire2 using xda app-developers app
Click to expand...
Click to collapse
Really annoying ha
I literally cannot find a reference to it, and dont understand why the amazon website hasnt even documented it!
I would moan about the horrible launcher...but that seems to have been done many times lol
I will check back in a few days maybe, to see if others have been cursed with this.
yo-meister said:
Really annoying ha
I literally cannot find a reference to it, and dont understand why the amazon website hasnt even documented it!
I would moan about the horrible launcher...but that seems to have been done many times lol
I will check back in a few days maybe, to see if others have been cursed with this.
Click to expand...
Click to collapse
Does the root with restore method for 10.2.4 work for this?
fmkilo said:
Does the root with restore method for 10.2.4 work for this?
Click to expand...
Click to collapse
Already tried binarys root with restore and qemu
Both failed unfortunately
Going to have to wait i suppose!
yo-meister said:
Already tried binarys root with restore and qemu
Both failed unfortunately
Going to have to wait i suppose!
Click to expand...
Click to collapse
You could definitely restore to a rooted 10.2.4 if you had a fastboot cable...
This works for 10.2.4
I found the solution! If you try and install superuser.apk directly by copying over to downloads and clicking on it, it works. Then simply grant ES File Explorer su permissions and click to mount the file system.
Idk why it worked, but if it doesn't, try using Root_with_Restore_by_Bin4ry_v1**8 & QemuRoot combination. When you get permission denied, make sure you run it again and press 3 to jump steps, but make sure you run step 4 or your device will remain sluggish
If that doesn't work try this: Rooted 10.2.4
Hopefully after running the tf101 file and qemu you can manually install superuser.apk from the sdcard. If it worked make sure you mount the filesystem with ES, because tthe shell wont work. Next, make sure to rename /system/etc/security/otacerts.****(zip) so that the next software update wont deroot you.
Last week my kindle fire 2 randomly update to 10.2.5 after I had rooted it with root many android, by bin4ry and qemu root.
I decided I would try the root many android method again last night to try and re-root the device and it worked perfectly, installed rootchecker, definitely had root access. Left the kindle on overnight to charge using a wall socket.
Woke up this morning and somehow my kindle is now 10.2.6.. I even renamed otacerts.zip to something else and it still managed to update itself to a version which doesn't even exist as far as I am aware.
Am I missing something here? Does anyone have any input?
Wilkinsss said:
Last week my kindle fire 2 randomly update to 10.2.5 after I had rooted it with root many android, by bin4ry and qemu root.
I decided I would try the root many android method again last night to try and re-root the device and it worked perfectly, installed rootchecker, definitely had root access. Left the kindle on overnight to charge using a wall socket.
Woke up this morning and somehow my kindle is now 10.2.6.. I even renamed otacerts.zip to something else and it still managed to update itself to a version which doesn't even exist as far as I am aware.
Am I missing something here? Does anyone have any input?
Click to expand...
Click to collapse
Amazon will update a select few device with the newest version before they actually release to everyone. You should REALLY thank amazon for making you one of the new guinea pigs haha. Also renaming otacerts.zip doesn't seem to work with the newer software versions. I've disabled all ota portions of silk using Rom Tollbox, I'll let you know on the next update. Though I'm using the 8.9 but should be the same
onemeila said:
Amazon will update a select few device with the newest version before they actually release to everyone. You should REALLY thank amazon for making you one of the new guinea pigs haha. Also renaming otacerts.zip doesn't seem to work with the newer software versions. I've disabled all ota portions of silk using Rom Tollbox, I'll let you know on the next update. Though I'm using the 8.9 but should be the same
Click to expand...
Click to collapse
I find it hard to believe I've been a guinea pig twice in two weeks haha but I'll take your word for it. Should it be safe to try reroot using the 10.2.4 method on 10.2.6? I assume so but I'm skeptical
Wilkinsss said:
I find it hard to believe I've been a guinea pig twice in two weeks haha but I'll take your word for it. Should it be safe to try reroot using the 10.2.4 method on 10.2.6? I assume so but I'm skeptical
Click to expand...
Click to collapse
I would think its ok. Do you have a backup and factory cable incase?
onemeila said:
I would think its ok. Do you have a backup and factory cable incase?
Click to expand...
Click to collapse
Factory cable is in the post on its way to me now, the root worked fine in 10.2.5 so my assumption would be the same for 10.2.6.
Edit: Since I am a risk-taker, see:foolish, I just decided to go ahead and root again with bin4ry's root. All is well and I have root again. I'd very much like it if I didn't have to go through this procedure once again, is there any way I can foolproof my system not to update, since otacerts didn't work last time?
So I had downloaded ExynosAbuse APK v1.40 to pop root cherry well before I even consider updating to T889UVALL4 & wanted to make sure there were no issues to be aware of before proceeding.
1) ExynosAbuse APK v1.40 for rooting leaves it in unmodified status & is totally reversible-really no risk at all?
2) Recommended root method after update* to T889UVALL4 ?
Honestly with all the customization in GO Launcher & the respectable Note2 battery life I'm no longer as interested in ROMs but it's good to know I could if I need even longer battery life etc. I don't like artificial limitations so I'm still curious about rooting, what would you recommend to first do after rooting (Wi-Fi router, Titanium Backup, Avast advanced anti-theft options etc)?
I don't see why I can't use Wi-Fi router functionality on rare occasion with my data allotment & noticed T-Mobile blocked this when trying FoxFi so how difficult is this to set up following root on SGH-T889 ?
Recommendations for Wi-Fi router ( https://play.google.com/store/apps/details?id=com.googlecode.android.wifi.tether ? ), Titanium Backup, Avast root anti-theft options etc?
- Thnx
* Refs:
http://forum.xda-developers.com/showthread.php?t=1960784
http://www.androidayos.com/2013/01/17/root-t-mobile-galaxy-note2-t889uvall4-4-1-1-jelly-bean/ ?
If you've rooted and not updated yet I found the root saving feature in SuperSU Pro saved my root across the OTA update. I belive I've read from others that OTA rootkeeper also worked for them.
Baenwort said:
If you've rooted and not updated yet I found the root saving feature in SuperSU Pro saved my root across the OTA update. I belive I've read from others that OTA rootkeeper also worked for them.
Click to expand...
Click to collapse
Can anyone confirm any way to save root from ExynosAbuse APK v1.40 with T889UVALL4 update?
-Thnx
SMARTPHONEPC said:
Can anyone confirm any way to save root from ExynosAbuse APK v1.40 with T889UVALL4 update?
-Thnx
Click to expand...
Click to collapse
I'm trying to find out the same thing while keeping the phone status as normal. But from what i have been able to figure is that the only way to do this is by rooting using Mobile Odin. So really you are re- rooting the phone. It seems that you cannot maintain root if you used the exploit abuse because the update is what fixes the problem that enabled you to root by means of this method. Please correct me if I am wrong because I have been holding off from updating until I am sure of what I can do. as you can probably tell I don't want to go through the root process again and chance messing up anything that is already working flawlessly
Edit: I should clarify I am talking about updating via this method http://forum.xda-developers.com/showthread.php?t=1975560 using the info from around post 205 and on
Re: [Q] ExynosAbuse APK v1.40 for first root before T889UVALL4 & first things to do?
Just use ota rootkeeper and do the ota. The exploit is simply the vector which got root installed the first time. Rootkeeper is the easiest way to reestablish root after ota.
Even if there is an issue, being root back is ridiculously easy on this device.
Hastily spouted for your befuddlement
Coug76 said:
Just use ota rootkeeper and do the ota. The exploit is simply the vector which got root installed the first time. Rootkeeper is the easiest way to reestablish root after ota.
Even if there is an issue, being root back is ridiculously easy on this device.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
Oh okay thanks. Would you happen to know if the device status would remain normal? I need that in order to be able to continue to use the Allshare dongle
GMAN1722 said:
I'm trying to find out the same thing while keeping the phone status as normal. But from what i have been able to figure is that the only way to do this is by rooting using Mobile Odin. So really you are re- rooting the phone. It seems that you cannot maintain root if you used the exploit abuse because the update is what fixes the problem that enabled you to root by means of this method. Please correct me if I am wrong because I have been holding off from updating until I am sure of what I can do. as you can probably tell I don't want to go through the root process again and chance messing up anything that is already working flawlessly
Edit: I should clarify I am talking about updating via this method http://forum.xda-developers.com/showthread.php?t=1975560 using the info from around post 205 and on
Click to expand...
Click to collapse
We definitely would not be able to use the ExynosAbuse APK v1.40 after the T889UVALL4 update as it patches the exploit the apk uses but posters seem to be indicating that if done before then root could possibly be kept via https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper , anyone confirm scenario or suggest next best alternative? - Thnx
SMARTPHONEPC said:
Can anyone confirm any way to save root from ExynosAbuse APK v1.40 with T889UVALL4 update?
-Thnx
Click to expand...
Click to collapse
Yep, works fine using OTA rootkeeper.
GMAN1722 said:
Oh okay thanks. Would you happen to know if the device status would remain normal? I need that in order to be able to continue to use the Allshare dongle
Click to expand...
Click to collapse
Mine still shows normal.
kozmo21 said:
Yep, works fine using OTA rootkeeper.
Mine still shows normal.
Click to expand...
Click to collapse
You da man kozmo21..
So step1: Download ExynosAbuse APK v1.40 & run if haven't already.
Step2: Download-run https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper
Step 3: Install OTA T889UVALL4
Step 4: Run https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper again to restore root backup?
That easy? - Thnx
SMARTPHONEPC said:
You da man kozmo21..
So step1: Download ExynosAbuse APK v1.40 & run if haven't already.
Step2: Download-run https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper
Step 3: Install OTA T889UVALL4
Step 4: Run https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper again to restore root backup?
That easy? - Thnx
Click to expand...
Click to collapse
Yep, that's it. As long as you use rootkeeper to make a backup of root, you're good. I did another reboot after restoring root, not sure it was necessary, but figured it couldn't hurt.
Don't think it works if you try to use kies to update, has to be a OTA download. I just got my OTA notification about an hour ago, so just wait if you haven't got it yet.
kozmo21 said:
Yep, that's it. As long as you use rootkeeper to make a backup of root, you're good. I did another reboot after restoring root, not sure it was necessary, but figured it couldn't hurt.
Don't think it works if you try to use kies to update, has to be a OTA download. I just got my OTA notification about an hour ago, so just wait if you haven't got it yet.
Click to expand...
Click to collapse
Thanks kozmo21, just to be clear did you need to unroot with the apk after backup with OTA rootkeeper & before the OTA update (I do have the OTA download notification in my tray)?
Also any recommendations for Wi-Fi router ( https://play.google.com/store/apps/details?id=com.googlecode.android.wifi.tether ) or will T-Mobile still block it? - Thnx
Re: [Q] ExynosAbuse APK v1.40 for first root before T889UVALL4 & first things to do?
GMAN1722 said:
Oh okay thanks. Would you happen to know if the device status would remain normal? I need that in order to be able to continue to use the Allshare dongle
Click to expand...
Click to collapse
It did for me. I initially rooted using mrRobinson's root66 for the initial firmware. Rootkeeper worked great with both uvalk8 and uvall4. YMMV
Hastily spouted for your befuddlement
Re: [Q] ExynosAbuse APK v1.40 for first root before T889UVALL4 & first things to do?
I havent updated either and want to root before updating. Also not sure if I'm going to keep the phone so for the sake of returning, will rooting via apk change my Device Status to Modified? Someone mentioned theirs didnt change but need more confirmation. TIA.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
aznmode said:
I havent updated either and want to root before updating. Also not sure if I'm going to keep the phone so for the sake of returning, will rooting via apk change my Device Status to Modified? Someone mentioned theirs didnt change but need more confirmation. TIA.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
Reportedly the device status will be normal not modified, I'll further confirm when I do it. Why are you thinking about returning the handset & how do you like the ASUS Transformer Pad TF700T (how limited does it feel compared to full pc-can you install Ubuntu or WIn8 on it)?
SMARTPHONEPC said:
Thanks kozmo21, just to be clear did you need to unroot with the apk after backup with OTA rootkeeper & before the OTA update (I do have the OTA download notification in my tray)?
Also any recommendations for Wi-Fi router ( https://play.google.com/store/apps/details?id=com.googlecode.android.wifi.tether ) or will T-Mobile still block it? - Thnx
Click to expand...
Click to collapse
No, did not need to unroot to take the update.
Don't use wifi router, so can't help there... sorry.
Btw, just checked my status again for aznmode... still shows normal in Device status.
Re: [Q] ExynosAbuse APK v1.40 for first root before T889UVALL4 & first things to do?
kozmo21 said:
No, did not need to unroot to take the update.
Don't use wifi router, so can't help there... sorry.
Btw, just checked my status again for aznmode... still shows normal in Device status.
Click to expand...
Click to collapse
Thank you sir for the reconfirmation.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
---------- Post added at 04:52 PM ---------- Previous post was at 04:42 PM ----------
SMARTPHONEPC said:
Reportedly the device status will be normal not modified, I'll further confirm when I do it. Why are you thinking about returning the handset & how do you like the ASUS Transformer Pad TF700T (how limited does it feel compared to full pc-can you install Ubuntu or WIn8 on it)?
Click to expand...
Click to collapse
Thanks you as well. The reason I'm thinking of returning it is the size. I was aware it's not a one handed device but playing with it at the store it felt fine till I got around to really using it now that I have it. I feel like I'm fighting to hold on to it even when I have to pick it up off a table. But really love the speed of it compared to my s3.
Asus tf700t is another story. No way you can deal with it stock. You have to run custom rom and perhaps do the data2sd mod to eliminate some of the IO issue. If smoothness is what you're looking for, its not there yet. Transition in opening apps is choppy still. Swiping between home screens and app drawer not so much. IO issue still exist at time even with the data2sd mod. The only thing making me hold on to it is the keyboard dock. Cant live without the dock and its features. But really I just use it now as a replacement laptop so I'm ok with it. There's a Ubuntu beta for the tf700t but not really interested and windows 8 is probably impossible on it but Id rather sell it and get a win 8 rather than rely on a port but win8 is so limited right now that I dont wanna bother with it. But If you dont need the dock go for the Nexus 10 (I'm testing that as well). Otherwise wait for what asus comes up with or maybe the new sony z tablet. PM me if you have any other questions so we dont clog up the thread =).
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
---------- Post added at 05:39 PM ---------- Previous post was at 04:52 PM ----------
Ok I just did the apk and am now rooted. I didn't patch the exploit yet however. Device status still "Normal".
Going to DL the OTA rootkeeper to obtain root after I do the OTA. I assume I can still unroot using the ExynosAbuse app once I do the OTA?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
aznmode said:
---------- Post added at 05:39 PM ---------- Previous post was at 04:52 PM ----------
Ok I just did the apk and am now rooted. I didn't patch the exploit yet however. Device status still "Normal".
Going to DL the OTA rootkeeper to obtain root after I do the OTA. I assume I can still unroot using the ExynosAbuse app once I do the OTA?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
If you need to unroot, just go to SuperSU > settings > Full unroot.
See http://forum.xda-developers.com/showpost.php?p=37026912&postcount=10 for order of steps
Device status should remain normal as long as you don't use the apk to patch the exploit (only use the apk to root then back up root with OTA rootkeeper then install OTA update which will patch the Exynos exploit that the apk used to root & rerun OTA rootkeeper to restore root).
I can not confirm that you can still unroot using the ExynosAbuse apk after OTA as I will not likely do it until tomorrow (hopefully I can get a reply to http://forum.xda-developers.com/showthread.php?t=2113053 by then). Anyone confirm this?
Regarding size, I do consider it a one-handed device but I wear large size gloves, I do find the following helpful & may make it easier for you to handle:
I use this Seidio kickstand case & often also use the following: http://www.amazon.com/StickStand-wedgi-Smartphone-Kickstand-Navigation/dp/B004EVFO1G & at times http://www.amazon.com/CellHandle-Positive-Control-Your-Phone/dp/B0073G6OM2 on the Seidio kickstand case with Go Launcher. I'll PM you when I get a chance regarding tablets.
aznmode said:
Thank you sir for the reconfirmation.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
---------- Post added at 04:52 PM ---------- Previous post was at 04:42 PM ----------
Thanks you as well. The reason I'm thinking of returning it is the size. I was aware it's not a one handed device but playing with it at the store it felt fine till I got around to really using it now that I have it. I feel like I'm fighting to hold on to it even when I have to pick it up off a table. But really love the speed of it compared to my s3.
Asus tf700t is another story. No way you can deal with it stock. You have to run custom rom and perhaps do the data2sd mod to eliminate some of the IO issue. If smoothness is what you're looking for, its not there yet. Transition in opening apps is choppy still. Swiping between home screens and app drawer not so much. IO issue still exist at time even with the data2sd mod. The only thing making me hold on to it is the keyboard dock. Cant live without the dock and its features. But really I just use it now as a replacement laptop so I'm ok with it. There's a Ubuntu beta for the tf700t but not really interested and windows 8 is probably impossible on it but Id rather sell it and get a win 8 rather than rely on a port but win8 is so limited right now that I dont wanna bother with it. But If you dont need the dock go for the Nexus 10 (I'm testing that as well). Otherwise wait for what asus comes up with or maybe the new sony z tablet. PM me if you have any other questions so we dont clog up the thread =).
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
---------- Post added at 05:39 PM ---------- Previous post was at 04:52 PM ----------
Ok I just did the apk and am now rooted. I didn't patch the exploit yet however. Device status still "Normal".
Going to DL the OTA rootkeeper to obtain root after I do the OTA. I assume I can still unroot using the ExynosAbuse app once I do the OTA?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
kozmo21 said:
If you need to unroot, just go to SuperSU > settings > Full unroot.
Click to expand...
Click to collapse
Good to read confirmation that full unroot is still an option in this scenario.
So is this procedure the only way to root this handset wirelessly ATM (it seems the easiest while also correcting the Exynos exploit)? - Thnx
SMARTPHONEPC said:
Good to read confirmation that full unroot is still an option in this scenario.
So is this procedure the only way to root this handset wirelessly ATM (it seems the easiest while also correcting the Exynos exploit)? - Thnx
Click to expand...
Click to collapse
Yep, only way without using Odin. Couldn't be any easier to root... no computer needed.
BY mistake I made a thread in general note4 section.
http://forum.xda-developers.com/note-4/help/kingroot-fails-kingo-rooted-root-t3501476
Anyone willing to help out?
EDIT: was able to root once but then everytime it just reboots the phone - at first cause was I didn't accept the "installation of the application" battery is low so maybe that could be the the reason..
patt2k said:
BY mistake I made a thread in general note4 section.
http://forum.xda-developers.com/note-4/help/kingroot-fails-kingo-rooted-root-t3501476
Anyone willing to help out?
EDIT: was able to root once but then everytime it just reboots the phone - at first cause was I didn't accept the "installation of the application" battery is low so maybe that could be the the reason..
Click to expand...
Click to collapse
I had the same problem a few hours ago. Kingo Root refused to work at all, so I had to use the Kingroot app. It made my phone lag like crazy after it rooted it, but it eventually worked. When you use either Kingo Root or Kingroot, what's the exact error that you get? Are you using Root Checker to see if you achieved root?
I always did a factory reset before starting the root process, it just seemed to make things go smoother. At least it would stay stable long enough to get all the adb stuff done. (Barely though )
quinciebee said:
I had the same problem a few hours ago. Kingo Root refused to work at all, so I had to use the Kingroot app. It made my phone lag like crazy after it rooted it, but it eventually worked. When you use either Kingo Root or Kingroot, what's the exact error that you get? Are you using Root Checker to see if you achieved root?
Click to expand...
Click to collapse
I was able to root once and run the script and it changed the CID or whatever it was. Now I simply cannot get temp root at all to finish the bootloader unlock process. Tried PC version and Android version so many times now it just reboots and reboots.
kevintm78 said:
I always did a factory reset before starting the root process, it just seemed to make things go smoother. At least it would stay stable long enough to get all the adb stuff done. (Barely though )
Click to expand...
Click to collapse
did a factory reset actually :/
patt2k said:
I was able to root once and run the script and it changed the CID or whatever it was. Now I simply cannot get temp root at all to finish the bootloader unlock process. Tried PC version and Android version so many times now it just reboots and reboots.
did a factory reset actually :/
Click to expand...
Click to collapse
That sucks, to be honest it's been awhile since I did the unlock process. Maybe something changed with the way that app roots. Have you already tried an older version of kingroot? I know you've probably tried all this stuff but sometimes things get overlooked.
kevintm78 said:
That sucks, to be honest it's been awhile since I did the unlock process. Maybe something changed with the way that app roots. Have you already tried an older version of kingroot? I know you've probably tried all this stuff but sometimes things get overlooked.
Click to expand...
Click to collapse
Rooted once with the newest one and it didn't reset even once. But then it just resets everytime. I did another factory reset so we shall see. I'll keep on trying.
Sent from my iPhone using Tapatalk
quinciebee said:
I had the same problem a few hours ago. Kingo Root refused to work at all, so I had to use the Kingroot app. It made my phone lag like crazy after it rooted it, but it eventually worked. When you use either Kingo Root or Kingroot, what's the exact error that you get? Are you using Root Checker to see if you achieved root?
Click to expand...
Click to collapse
It worked once for me was able to use the unlock script but it was the part #1 of the process, so far I am unable to root again to fully unlock it. Been trying since yesterday the phone reboots when trying to root.
kevintm78 said:
That sucks, to be honest it's been awhile since I did the unlock process. Maybe something changed with the way that app roots. Have you already tried an older version of kingroot? I know you've probably tried all this stuff but sometimes things get overlooked.
Click to expand...
Click to collapse
Good news! Kingroot 5.0 worked on second try. Status: Developer
patt2k said:
Good news! Kingroot 5.0 worked on second try. Status: Developer
Click to expand...
Click to collapse
That's great! Did you have to do anything different or did kingroot just finally work long enough to get the job done?
kevintm78 said:
That's great! Did you have to do anything different or did kingroot just finally work long enough to get the job done?
Click to expand...
Click to collapse
The kingroot 5.0 worked on second try.. so no idea why the older ones didn't work.
Would you happen to know which rom supports more languages other then default ones? shipping this phone to Europe tomorrow, don't know how stable CM roms are.
Hellooo good peoples.
I rooted my fire tv 2 and installed twrp a couple years ago. I haven't bothered to update the OS. So yeah, it's like 2 years old
Now Prime videos won't play, cheeky bastiches at Amazon. So that was the catalyst to update but things have changed, it seems.
Can I just use TWRP to flash a rom, or will I need to switch to rbox? Any ideas on the easiest way forward? I don't want to lose root, just in case. I did the whole unplug ethernet at juuuuust the right time thing on a couple of these, so root was hard won.
All input is greatly appreciated. I'm hoping I don't have to redo a ton.
Fremontidae said:
Can I just use TWRP to flash a rom, or will I need to switch to rbox? Any ideas on the easiest way forward? I don't want to lose root, just in case. I did the whole unplug ethernet at juuuuust the right time thing on a couple of these, so root was hard won.
Click to expand...
Click to collapse
There is only one prerooted rom and thats from rbox. FireOS up to 5.2.6.9 is rootable. Amazon fixed this in 5.2.7.0 and higher.
It seems that the update procedere is a little tricky. There is an unbrick image but some people here on xda have bricked permanently.
So its better if you look carefull into the thread from rbox.
Sus_i said:
There is only one prerooted rom and thats from rbox. FireOS up to 5.2.6.9 is rootable. Amazon fixed this in 5.2.7.0 and higher.
It seems that the update procedere is a little tricky. There is an unbrick image but some people here on xda have bricked permanently.
So its better if you look carefull into the thread from rbox.
Click to expand...
Click to collapse
I was looking at the available ROMs and it says that you must flash 5.2.6.7 before flashing anything newer.
What I'm wondering is, can I just use TWRP to flash 5.2.6.7 and then the newest? Or do I need to use the newer rbox method?
Fremontidae said:
I was looking at the available ROMs and it says that you must flash 5.2.6.7 before flashing anything newer.
What I'm wondering is, can I just use TWRP to flash 5.2.6.7 and then the newest? Or do I need to use the newer rbox method?
Click to expand...
Click to collapse
Don't know. Maybe you have to update TWRP too, before you flash 5.2.6.7 and the newest? Take a look in the TWRP thread for your device. If you can't find an answer in the thread, I would ask @rbox.
Personally, I would flash not higher than 5.2.6.9. It's imho the latest OS that could be rooted, in case something gets wrong and/or you lost root.
Fremontidae said:
I was looking at the available ROMs and it says that you must flash 5.2.6.7 before flashing anything newer.
What I'm wondering is, can I just use TWRP to flash 5.2.6.7 and then the newest? Or do I need to use the newer rbox method?
Click to expand...
Click to collapse
I watched the vid on the ROM thread and it looks like I could just do as aforementioned. Only diff is I use adb to push the images because I'm too lazy to pull the micro sd. I have another rooted fire tv 2 at my parent's house that I gave them and they never used. I just don't want to brick, because it's my primary entertainment source and my parent's live an hour and change away. I'm halfway tempted to just let the thing update and lose root, but I'm not even sure that will work, IIRC I have the update addies blocked in my router. Ugh.
What a PITA.
I guess I'm wondering if 5.2.6.9 is even working with Prime video?
Fremontidae said:
I guess I'm wondering if 5.2.6.9 is even working with Prime video?
Click to expand...
Click to collapse
5.2.6.9 is almost the same as 5.2.7.0. Prime video is working fine.
---------- Post added at 03:37 PM ---------- Previous post was at 03:34 PM ----------
Fremontidae said:
I'm halfway tempted to just let the thing update and lose root, but I'm not even sure that will work, IIRC I have the update addies blocked in my router. Ugh.
What a PITA.
Click to expand...
Click to collapse
Don't do that, amazon fixed the vulnerable, so if you update the offical way, you lose root probably forever...