Read up on this in my Google New reader app.
Just installed it to see if it works on our tabs, and it appears to.
What I believe it does is make a backuo of your root.
Before you do an OTA, you uninstall root (after you've backed up root) through the app, then after OTA you restore your root.
For those of you that like to stay stock, but have root, here's the link.
https://market.android.com/details?id=org.projectvoodoo.otarootkeeper
interesting But i bet acer is Already working on patching this... I also think that is what takes them so long to push updates.. Patching holes. to prevent dev. on There devices that we PAID For ...APPLE Ceo did not die He Quit and it working with Elvis at Acer... Giggles..
erica_renee said:
interesting But i bet acer is Already working on patching this... I also think that is what takes them so long to push updates.. Patching holes. to prevent dev. on There devices that we PAID For ...APPLE Ceo did not die He Quit and it working with Elvis at Acer... Giggles..
Click to expand...
Click to collapse
I guess you didn't understand what it does?
Doesn't your sig say "reading is power"?
yes i read what it does.. Just not sure how long it will remain valid and i d/loaded it will check it out give it a try
erica_renee said:
yes i read what it does.. Just not sure how long it will remain valid and i d/loaded it will check it out give it a try
Click to expand...
Click to collapse
It does nothing to the bootloader, merely retains root. After you backup root with the app, you get your OTA, then restore your root through the app.
OK What i do not understand.. is IF it can retain root thru the OTA.. ota updates change they system file permissions and protects them. The use some type of exploit to root the device. This app is doing the same Am i correct.. And if i am acer can plug that exploit. Also.. is this works to reroot afer a ota unrootes the device.. why will this not just root the tablet as well. looks like someone could take it apart and create a new way to root the tablet without DOWNGRADING or flashing a new rom..
IS the above true or am i just STUPID For thinking all of this... the dev might know something that is not known on the a500 forums ...
I can tell you exactly how it works.
In Linux there is a command called chattr which allows you to change the attributes on a file like in Windows (readonly for example). However, in Linux it is much more powerful. So, what you do, is set the chattr bit so NOBOBY can modify a file. Not even root. If root wants to change it, then root has to remove that bit first.
So, if you want to keep root you chattr it. Then when the update.zip runs and walks through the /system folder it cannot remove the su sticky bit because it has been chattr'ed.
However, some updates delete everything in the /system/xbin folder therefore the tool makes a backup to another folder called /system/backupsu. This backup usually remains. Usually, that is, unless ACER loads a NEW /system image. Like they need to expand the size, or want to reload everything, then they lay down a NEW system image and it's gone. ALL GONE.
Some ask, why don't you chattr to another folder other then system, well most other mount points have su sticky bit turned off, therefore making su not work from another mount.
So will ACER plug the chattr hole? I don't think so, this in the kernel and part of the file system. They could walk the system mount and un-chattr everything, but then again you can just use another approach.
The chattr trick normally only works on simple OTA's. For example, I think when ACER went to 3.2 they relaid down system. I could be wrong, I'd have to check my notes. But thankfully, most vendors don't reload system that often so you'r find that chattr'ng the su file works 99% of the time.
Hope this helps,
TD
---------- Post added at 06:25 PM ---------- Previous post was at 06:10 PM ----------
Also, 411 on rooting.
To root, you find a hole and then set the 'sticky bit' on an executable so it now runs as root for example: rwsr-xr-x. Notice the 's' in the owner permissions. When this file is executed it runs with the owners permissions on the file system. So to make a simple root, just copy the ash shell to /system/xbin make the file owned by root and then set the sticky bit. Now, if you are not root, you just run /system/xbin/ash and because this version of ash is owned by root and has the sticky bit set, you get the root(#) because the ash shell is now running as root.
So, you use the exploit to gain root and then set up a program to give you root anytime you want it. Usually that program is named su. Now, when an update runs, it walks the entire /system tree resetting all files to rwxr-xr-x which removes the sticky bit and breaks root.
What is heartbreaking, is you now need to use the exploit to get root so you can set back your sticky bit. If the update patched your exploit then you have find another one.
So, the question is, once you get root, how do you keep it. Using chattr is one way therefore if the update removes your exploit, hopefully it doesn't matter because you 'locked in' your sticky bit with chattr.
This is why once any version is rooted you can root most any other version. It now becomes possible to move back and forth through OTA's while allowing you to keep root. But time traveling a root OTA is only possible into the future, you can never go back in time prior to the invention of the root. But you can always travel forward with root. This is exactly how we root the 3.2.1. We take a tablet that has 3.0.1 on it and use iconia root exploit to root it. Then we lock it, add other backdoors, and roll forward in time through the minefields of the OTA's until it stops. Hopefully, you still have root. In other words, it's the flux capacitor and is what makes future rooting possible.
So it doesn't matter, as long as you chattr (chatter), because who cares if ACER's heart goes pitter patter <<== Sounds like a Roll'n Stone lyrics <lol>
"Don't you know the crime rate is going up, up, up, up, up
To live on this forum you must be tough, tough, tough, tough, tough
You got rats at ACER dreaming of the west side
Software bugs on upgrades
What a mess, this forum says chatter (chattr), so my root won't be shattered
My brains been battered, splattered all over this forum
but what's that matter.
Ah look at me, my root is chattr'ed
I'm not wanting my root shattered
Look at me- I'm a chattr'ed, look at me
Man time to go drink heavily.
"SOFTMOD" app
SORRY PPL COMPLETELY CONFUSED 2 DIFFERENT TOPICS IN 2 DIFFERENT THREADS - ALZHEIMER's RULES OK!! - Deleted this response
timmyDean your making my head spin. Thanks for the info.
ok as I was thinking this works unless acer pushes a full os.So I will continue to stay on custom roms.giggles
erica_renee said:
ok as I was thinking this works unless acer pushes a full os.So I will continue to stay on custom roms.giggles
Click to expand...
Click to collapse
Actually, I went back to 3.1 today to test it out. It worked through all updates, including full updates
kjy2010 said:
Actually, I went back to 3.1 today to test it out. It worked through all updates, including full updates
Awesome.
It seems interesting
Click to expand...
Click to collapse
kjy2010 said:
Actually, I went back to 3.1 today to test it out. It worked through all updates, including full updates
Click to expand...
Click to collapse
You the man. I could not recall if 3.0.1 to 3.1 to 3.2 did a system reload. What some OEM's do is erase /system. Lenovo did that when they went from 11 to 12 and then from 12 to 13. But, I could not recall if ACER did. You'll find that chattr works 99% of the time, maybe 100% on an ACER. That's why I turn off OTA's so they don't occur automatically. Then when one becomes available, I download and look at what they're changing before allowing it. This is really important now that they've locked the bootloader. If you take an OTA and it patches your root exploit, removes chattr, deletes your backup su, and breaks root then you might be stuck in the future with no root. If this happens you have to hope there's a way back without root.
So thanks.
---------- Post added at 03:28 PM ---------- Previous post was at 03:15 PM ----------
erica_renee said:
ok as I was thinking this works unless acer pushes a full os.So I will continue to stay on custom roms.giggles
Click to expand...
Click to collapse
Not a full system, it's how they load it is the key. They push full systems all the time and they really just copy over all new which keeps chattr'ed files. They really have to reformat /system (or destructively destroy it). They'll do this if they need to increase the size, change from ext3 to ext4, etc.
Hope this helps
TD
Thanks sirs for this if we get the doubtful ota I might do this n sell the tap to my little brother or keep it who knows lol
Sent from my HTC Inspire 4G using Tapatalk
timmyDean said:
You the man. I could not recall if 3.0.1 to 3.1 to 3.2 did a system reload. What some OEM's do is erase /system. Lenovo did that when they went from 11 to 12 and then from 12 to 13. But, I could not recall if ACER did. You'll find that chattr works 99% of the time, maybe 100% on an ACER. That's why I turn off OTA's so they don't occur automatically. Then when one becomes available, I download and look at what they're changing before allowing it. This is really important now that they've locked the bootloader. If you take an OTA and it patches your root exploit, removes chattr, deletes your backup su, and breaks root then you might be stuck in the future with no root. If this happens you have to hope there's a way back without root.
So thanks.
---------- Post added at 03:28 PM ---------- Previous post was at 03:15 PM ----------
Not a full system, it's how they load it is the key. They push full systems all the time and they really just copy over all new which keeps chattr'ed files. They really have to reformat /system (or destructively destroy it). They'll do this if they need to increase the size, change from ext3 to ext4, etc.
Hope this helps
TD
Click to expand...
Click to collapse
Yes i do understand. Maybe i did not explain what i was saying correctly.. Acer's update is not aware or looking for those files. There for they do not touch them. as they are just scanning and updating files to reflect there changes.. I to agree that its likely this will remain valid.Atleast we know it is for the os updates and release that are available up to now..
erica_renee said:
Yes i do understand. Maybe i did not explain what i was saying correctly.. Acer's update is not aware or looking for those files. There for they do not touch them. as they are just scanning and updating files to reflect there changes.. I to agree that its likely this will remain valid.Atleast we know it is for the os updates and release that are available up to now..
Click to expand...
Click to collapse
Exactly, so much for being blonde <lol>
Related
Alright, I'm unbanned so now I can post the latest iteration of how your phone should be rooted by batch script.
Note: This script is actually still being developed so if I break something in the script by adding something else it will be fixed. I don't have a shift to test on and I don't have any money. From what I know, my friend did indeed test this and it's working 100% so now lets move on to features.
FEATURES:
Wimax backup and restore - after the root process/misc.img flash
MD5 hash check for misc.img before and after.
Temproot
Hboot flash
Choices to ask what you want (Y/N questions)
asks if you already rooted with fre3vo and if so, takes you to the reroot script.
Credits?
OTAking71 and scaryghoul. (Hboot patch)
Otaking again just for beta testing my script on his spare shift.
Agrabren for releasing fre3vo
Me for writing this batch file from nothing but the instructions in the hboot downgrade thread.
Download link?
http://dl.dropbox.com/u/15069134/fre3atlast_v_2.7.2.zip
Github:https://github.com/xIndirect/Fre3atlast
Note: This script is made by me and may not be modified, reposted, or shared without my permission.
Reason I don't want you to modify it is because of the fact that I don't want anyone to break the script which can break the phones! Remember: Batch is very particular about function calling!
Code:
Changelog:
Updated to 2.7.2
Corrected output for link thats echoed into a text file.
Changed how it provides download links due to wget not cooperating correctly.
Added automatic function of checking MD5
added install.bat script for post-downgrade install of z4root and visionary
added automatic downloading of misc.img if bad md5
added downloading of choice between PG06IMG.zip or the exe RUU to downgrade
added wget to allow for downloading of the aforementioned files.
added device check
maybe some other slight things I'm forgetting
Quick developers note:
Everyone, I wrote Fre3AtLast as an improvement on the original script since it had some un-needed lines in it. I am not going to tolerate anyone else acting childish over this and the difference between devnull's and my script. It's just a more efficient way other than his and I still give him credit for giving me the original idea to create/improve on his script.
Click to expand...
Click to collapse
Wanna buy me a coffee or something pretty for christmas?
NOICE
Flawless victory.
---------- Post added at 02:54 PM ---------- Previous post was at 02:46 PM ----------
Wimax Backup script doesn't quite work, but everything else seems golden.
Add a `mkdir /sdcard/WiMax;` before the DD and you'd probably be good to go.
Figured I mucked up somewhere in the wimax backup script. I''ll add it really quick
Awesome!!!!! worked great!
what are the steps on running this other than having a GB shift that's not rooted temp or perm ?
You just have to extract to your desktop *in its own folder preferably* then you just run the Fre3atlast.bat and poof; you're rooted.
VIDEO
You wouldn't have a video or a step by step guide going through this would you.
Thanks! Worked flawlessly! Unlike a different one I fought with for two days. lol
Cheers!
Syanptic, you dont need one. It tells you what you do by asking you. Just be honest to the script and your rooted
sent by breaking the sound barrier
sounds easy...
It sounds easy, but personally when possible I like to see what I'm about to do, yah know see the step by step to make sure I know whats going on before I dive in.
In the end, I'm just paranoid I'm gonna brick my phone. and hearing "its just that simple" isn't all that comforting for something that took a long time for people to work out.
Also does this requires froyo?
it tells you what its about to do by confirming if you want to do it. Perhaps if you ended up using the script or even reading it, you would have learned that. Im not being a **** but people need to learn to read. Also, it is just that simple. It had to be figured out but the implication of it is much easier than having to find it as is true with everything else.
Sent by breaking the sound barrier
Indirect said:
it tells you what its about to do by confirming if you want to do it. Perhaps if you ended up using the script or even reading it, you would have learned that. Im not being a **** but people need to learn to read. Also, it is just that simple. It had to be figured out but the implication of it is much easier than having to find it as is true with everything else.
Sent by breaking the sound barrier
Click to expand...
Click to collapse
Yeah, I got that, in fact I opened the .bat in notepad.
lets see what instructions it outputs.
-have you rooted before? y/n
-clearing cache
-if the misc.img MD5 as well as the the original MD5. (I am assuming its outputting a code sum to check if the file is good)
-there are only 2 times this will stop... run? y/n
-if you want to continue hit y, if not n
-this is happening if you want to flash Hboot misc.img to be able to downgrade. -this is from saying N to the first choice (i assume this references the have you rooted before question
-congrats, your rooted, thank people
now I may have missed something, but that's not exactly explanation. Also no where in this thread does it say if you can or can't use this in gingerbread.
Your response is why I typically avoid forums and rooting, people offer help and then chastise you and or call you stupid for asking questions. If you think its a dumb question that you don't feel you need to answer just don't respond. Its better off that way than insulting people that came to you for help.
Clearly, I am hesitant about rooting my phone. I know enough to know that if you do something wrong when trying to root a device you can brick it. You can't really blame me for wanting to understand what I'm about to do. Also, saying I would know if I ran it is pointless, the reason I asked the question is because I wanted to know what it did BEFORE I ran it.
I am a little confused at this point from all the different posts saying you need this or you need that or beware if your using this so on and so forth. Yeah, I'm not a master programmer, its not my field. I don't have all the time in the world to figure this out on my own. If HTC would just open up root I would probably use that. But that's not the case so I'm here. Have some freaking courtesy.
what am I missing//? "error: device not found"
AllanGreg said:
what am I missing//? "error: device not found"
Click to expand...
Click to collapse
I had to install HTC Sync before it would work.
http://dl3.htc.com/application/HTCSyncv3.0.5579.exe
SynapticMeltdown said:
It sounds easy, but personally when possible I like to see what I'm about to do, yah know see the step by step to make sure I know whats going on before I dive in.
In the end, I'm just paranoid I'm gonna brick my phone. and hearing "its just that simple" isn't all that comforting for something that took a long time for people to work out.
Also does this requires froyo?
Click to expand...
Click to collapse
With all due respect to Indirect read this thread:
http://forum.xda-developers.com/showthread.php?t=1277448
VICODAN said:
With all due respect to Indirect read this thread:
http://forum.xda-developers.com/showthread.php?t=1277448
Click to expand...
Click to collapse
I agree that anyone rooting should read the downgrade information provided by scary, but tbh i wish i would have used the one click root when i first started. I have neither the time nor inclination to learn anymore about rooting than what it take to make my phone to run awesomely, and there are many root-users just like me.
im not going to run a batch on my phone unless its been tested and verified on an actual shift.
SynapticMeltdown said:
Yeah, I got that, in fact I opened the .bat in notepad.
lets see what instructions it outputs.
-have you rooted before? y/n
-clearing cache
-if the misc.img MD5 as well as the the original MD5. (I am assuming its outputting a code sum to check if the file is good)
-there are only 2 times this will stop... run? y/n
-if you want to continue hit y, if not n
-this is happening if you want to flash Hboot misc.img to be able to downgrade. -this is from saying N to the first choice (i assume this references the have you rooted before question
-congrats, your rooted, thank people
now I may have missed something, but that's not exactly explanation. Also no where in this thread does it say if you can or can't use this in gingerbread.
Your response is why I typically avoid forums and rooting, people offer help and then chastise you and or call you stupid for asking questions. If you think its a dumb question that you don't feel you need to answer just don't respond. Its better off that way than insulting people that came to you for help.
Clearly, I am hesitant about rooting my phone. I know enough to know that if you do something wrong when trying to root a device you can brick it. You can't really blame me for wanting to understand what I'm about to do. Also, saying I would know if I ran it is pointless, the reason I asked the question is because I wanted to know what it did BEFORE I ran it.
I am a little confused at this point from all the different posts saying you need this or you need that or beware if your using this so on and so forth. Yeah, I'm not a master programmer, its not my field. I don't have all the time in the world to figure this out on my own. If HTC would just open up root I would probably use that. But that's not the case so I'm here. Have some freaking courtesy.
Click to expand...
Click to collapse
Indirect is just mad that he broke his hand
If you haven't already I'd read this thread: http://forum.xda-developers.com/showthread.php?t=1255474 Scary does a good job of explaining what you're doing. You might actually find that you prefer to do the whole process manually. It's not hard, it's just a matter of following the instructions. It's very satisfying to root manually, you really feel that you've earned it.
And to answer your question, the actual perm rooting does require you to be on Froyo but the downgrade from Gingerbread to Froyo is part of this process.
jesusice said:
Indirect is just mad that he broke his hand
Click to expand...
Click to collapse
lol
10char...
Jesusice is right, I'm pissed that i broke my hand. He's mad thats hes married and not getting laid as much as me. :3
Anyway, this has been tested and verified on a shift, multiple actually. I think that if you cant use this script, it's user-error as it does a decent job in explaining. It asks if you rooted before, if no, it roots, flashes hboot (after confirmation for flashing hboot as well) then it even backs up wimax for you.
SynapticMeltdown said:
It sounds easy, but personally when possible I like to see what I'm about to do, yah know see the step by step to make sure I know whats going on before I dive in.
In the end, I'm just paranoid I'm gonna brick my phone. and hearing "its just that simple" isn't all that comforting for something that took a long time for people to work out.
Also does this requires froyo?
Click to expand...
Click to collapse
If i'm not mistaken this downgrades you and also roots you. Also you have to take risk if you wanna root your phone. Its a big plunge yes but out of all the comments not one person has bricked their phone and also this has been tested many times before. If you too scared to do this than you might not want to root your phone in the first place
I have a Touch rooted with Touchnooter. My touch doesn't seem to want to update to 1.1 (I know doing so will kill GAPPS, but I'm okay with that). I've waited for the update to be pushed and I've also put the update file in my Nook directory. Is there something about Touchnooter that prevents the Touch from updating?
I haven't tried to update after using touchnooter, dont really know if it blocks nothing, OTA or prevents from updates, OTA or manullay, but you should restore a copy of your nook if you have it, or use nookrestore and then force a reset to also delete /data.
Or use adb to force restore
adb shell
echo -n -e "\x08\x00\x00\x00" > /rom/devconf/BootCnt
reboot
Click to expand...
Click to collapse
and then reset normally and if it dosnt let you, force reset, force it shutting down your nook, then starting it up, and when the screen flickers press right and left bottom buttons, hold for 5+ seconds.
That will erase /system (restore) and /data (reset), and you should be able to update.
I do have a backup copy, but I was hoping I wouldn't have to do a restore to get the update. I mean, I'd really like to avoid that.
Have others been able to update their Touchnooter Touches to 1.1 without reverting?
kunchers said:
I do have a backup copy, but I was hoping I wouldn't have to do a restore to get the update. I mean, I'd really like to avoid that.
Have others been able to update their Touchnooter Touches to 1.1 without reverting?
Click to expand...
Click to collapse
Updating a TouchNootered NST have caused troubles in the past and is likely to do so with this update as well.
Even if it worked for other users it might not work for you as people do different things to their rooted NST.
I know it's a hassle, but you should really restore+reset your NST before updating if you want to avoid problems.
The OP's post has given me some hope as I do not wish to unroot/re-root-/update at this time, but have kept my NST's wireless off as I'm afraid of getting the update.
Am I to understand that a TouchNooter'd unit (1.6.24 on an NST1.0.1) will not get updated and there is nothing to fear?
TJay99 said:
Am I to understand that a TouchNooter'd unit (1.6.24 on an NST1.0.1) will not get updated and there is nothing to fear?
Click to expand...
Click to collapse
There's nothing in TN 1.6.24 that will block updates.
If you want to make sure, here's the cleanest way of doing so:
Block BN OTA Updates the EASY way
Yes, it's a Nook Color thread but it would work for Nook ST aswell.
TJay99 said:
The OP's post has given me some hope as I do not wish to unroot/re-root-/update at this time, but have kept my NST's wireless off as I'm afraid of getting the update.
Am I to understand that a TouchNooter'd unit (1.6.24 on an NST1.0.1) will not get updated and there is nothing to fear?
Click to expand...
Click to collapse
Blocking updates is also covered here http://forum.xda-developers.com/showthread.php?t=1346748 but with adb and sqlite.
Search for Blocking OTA updates: on the thread.
Yeah, I hear you. I gotta just do it. Strange though, why my Nook won't update.
ros87 said:
Updating a TouchNootered NST have caused troubles in the past and is likely to do so with this update as well.
Even if it worked for other users it might not work for you as people do different things to their rooted NST.
I know it's a hassle, but you should really restore+reset your NST before updating if you want to avoid problems.
Click to expand...
Click to collapse
Thanks ros87 and eded333 for the information.
As regards the adb/sqlite method, I just reviewed that thread and the specific "Blocking OTA Updates" section. Looks easy,... assuming one thing: that -- other than installing java JKD and the android SDK on my PC -- my NST (TouchNooter'd 1.6.2.4 on B&N1.0.1) already is set up to receive those commands listed. If it is, then I can simply connect the NST and type only those commands listed in the "Blocking OTA Updates" section. Right?
If that's not the case, what other procedures must I do in order to get it done? For instance, there are sections entitled "Setting up adb on the nook touch" and "Setting up root access on NST through adb and installing busybox". Would I need to do any part of those processes?
Much obliged if you can clear up that one matter for me!
I couldn't get my rooted 1.0.1 nook to update even manually. It silently deleted the update file and did nothing every time I tried.
Kralik said:
I couldn't get my rooted 1.0.1 nook to update even manually. It silently deleted the update file and did nothing every time I tried.
Click to expand...
Click to collapse
Hi, Kralik.
I wonder if it would keep downloading/deleting the update file in a perpetual cycle, though. Isn't that what would happen?
TJay99 said:
Thanks ros87 and eded333 for the information.
As regards the adb/sqlite method, I just reviewed that thread and the specific "Blocking OTA Updates" section. Looks easy,... assuming one thing: that -- other than installing java JKD and the android SDK on my PC -- my NST (TouchNooter'd 1.6.2.4 on B&N1.0.1) already is set up to receive those commands listed. If it is, then I can simply connect the NST and type only those commands listed in the "Blocking OTA Updates" section. Right?
If that's not the case, what other procedures must I do in order to get it done? For instance, there are sections entitled "Setting up adb on the nook touch" and "Setting up root access on NST through adb and installing busybox". Would I need to do any part of those processes?
Much obliged if you can clear up that one matter for me!
Click to expand...
Click to collapse
Touchnooter has adb enabled over wifi (If i'm not wrong), so you wouldnt have to enable it again, go directly into the OTA.
TJay99 said:
As regards the adb/sqlite method, I just reviewed that thread and the specific "Blocking OTA Updates" section. Looks easy,... assuming one thing: that -- other than installing java JKD and the android SDK on my PC -- my NST (TouchNooter'd 1.6.2.4 on B&N1.0.1) already is set up to receive those commands listed. If it is, then I can simply connect the NST and type only those commands listed in the "Blocking OTA Updates" section. Right?
Click to expand...
Click to collapse
You should be good to go if you install jdk + android sdk.
With TouchNooter 1.6.24 you should allready have adb access enabled via wifi.
---------- Post added at 08:34 PM ---------- Previous post was at 08:33 PM ----------
Kralik said:
I couldn't get my rooted 1.0.1 nook to update even manually. It silently deleted the update file and did nothing every time I tried.
Click to expand...
Click to collapse
Interesting, I need to take a closer look at the update process some day
Yep, same behavior with mine.
Kralik said:
I couldn't get my rooted 1.0.1 nook to update even manually. It silently deleted the update file and did nothing every time I tried.
Click to expand...
Click to collapse
TJay99 said:
Hi, Kralik.
I wonder if it would keep downloading/deleting the update file in a perpetual cycle, though. Isn't that what would happen?
Click to expand...
Click to collapse
That is my guess. Without knowing for sure you're left with two unpleasant options:
1) Your nook tries to update continuously: downloading, deleting, and wasting battery life,* or
2) Your nook actually updates and destroys everything!
So you might take the time to "block" OTA updates as other have mentioned. But then there's option...
3) You go through the rigors and just get the 1.1.0 firmware upgrade over and done with, rerooting afterwards.
*I wonder if this is related to the "I rooted my nook and now my battery life is toast" thread?
This is an excellent point. I've also experienced pretty sad battery life since applying Touchnooter.
I'll just bite the bullet and restore/re-root.
Kralik said:
1) Your nook tries to update continuously: downloading, deleting, and wasting battery life,* or
*I wonder if this is related to the "I rooted my nook and now my battery life is toast" thread?
Click to expand...
Click to collapse
kunchers said:
This is an excellent point. I've also experienced pretty sad battery life since applying Touchnooter.
I'll just bite the bullet and restore/re-root.
Click to expand...
Click to collapse
This is the best time to do that, finally got Gapps to work on 1.1 manully, at last!
If you wish to try it, here is my post:
http://forum.xda-developers.com/showthread.php?t=1346748
Kralik said:
That is my guess
1) Your nook tries to update continuously: downloading, deleting, and wasting battery life,* or
Click to expand...
Click to collapse
A good and interesting guess.
There are intervals defined for the update checks, but maybe if it finds an update but are unable to apply it, it end up in a loop..
GApps aren't actually that hard to enable if you use TouchNooter 1.6.24 and manually replace /nooter/boot/uRamdisk and /system/framework/framework.jar with the updated versions. Other than that step, very little difference in the rooting processes. If one is going to restore to factory and build up from there, what is the advantage to wading through all the manual steps?
Kralik said:
GApps aren't actually that hard to enable if you use TouchNooter 1.6.24 and manually replace /nooter/boot/uRamdisk and /system/framework/framework.jar with the updated versions. Other than that step, very little difference in the rooting processes. If one is going to restore to factory and build up from there, what is the advantage to wading through all the manual steps?
Click to expand...
Click to collapse
At this moment, fun, learning, and stability (for the moment it allways works, but I need more feedback from people that tried it) eventually, when I delete all the blob that Gapps dosn't need for them to work, and is installed on the default package of Touchnooter (Don't get me wrong I really think its a great method) you will get a cleaner install.
Anyway, If you don't want to go through all the steps you can use the new 1.1 Touchnooter to get root, and then use my GApps method.
Hello all, I found a method to Root and get a custom recovery on our cricket variant, no donations required! You need to find a copy of sugar qct with a username and password, I don't remember exactly where I found it but it shouldn't be too difficult to find. Then you need to let it update to the latest build, which includes the programmer for our phone. If you don't see 6055u in the list it's not up to date. From there, Hook up your phone (may need to manually put it in download mode. Press upgrade and then navigate to the install directory, look in /bin and find where it downloads all the mbm files. Replace the one that starts with an r with the TWRP recovery for 6055. You may have to overwrite it multiple times during the process. If you did it correctly you will be able to boot into TWRP, if not try again. If you don't close sugar I believe it won't overwrite the firmware files, but I haven't messed with it much. I will try to write a tool to make it easier when I have the time but I'm pretty busy. Feel free to pm me with any questions and I will help the best I can.
To get root just install supersu
F
dbgr said:
Hello all, I found a method to Root and get a custom recovery on our cricket variant, no donations required! You need to find a copy of sugar qct with a username and password, I don't remember exactly where I found it but it shouldn't be too difficult to find. Then you need to let it update to the latest build, which includes the programmer for our phone. If you don't see 6055u in the list it's not up to date. From there, Hook up your phone (may need to manually put it in download mode. Press upgrade and then navigate to the install directory, look in /bin and find where it downloads all the mbm files. Replace the one that starts with an r with the TWRP recovery for 6055. You may have to overwrite it multiple times during the process. If you did it correctly you will be able to boot into TWRP, if not try again. If you don't close sugar I believe it won't overwrite the firmware files, but I haven't messed with it much. I will try to write a tool to make it easier when I have the time but I'm pretty busy. Feel free to pm me with any questions and I will help the best I can.
To get root just install supersu
Click to expand...
Click to collapse
Did a Google search for "sugar qct" and I see a couple of million hits for "The Sugar Act"... :laugh:
Tried Root Genius, and it, of course doesn't work...
If you happen to find a link for the app or method you stated, I would be eternally grateful... My lovely wife and I upgraded our phones to the Cricket 6055U, and, since, while not an Android developer, per se, can find my way around the device without being scared off...
So, with due respect, I'd ask if you have the app or name correct?
Thanks, friend, and best respect.
--- edit ---
Oops... was premature... found it and am giving it a try... I'll post my results after I give it a shot...
http://forum.gsmhosting.com/vbb/f606/vf-895n-smart-prime-6-stock-rom-flash-tool-2033867/
This should help with setting up sugar. The only difference here is to update it and you also need a username and password that I don't have on me at the moment. It will be a few hours until I get home but I will update asap.
Edit: nevermind lol, good luck friend. You may need a decent battery percentage as well
pauljulian said:
F
Did a Google search for "sugar qct" and I see a couple of million hits for "The Sugar Act"... :laugh:
Tried Root Genius, and it, of course doesn't work...
If you happen to find a link for the app or method you stated, I would be eternally grateful... My lovely wife and I upgraded our phones to the Cricket 6055U, and, since, while not an Android developer, per se, can find my way around the device without being scared off...
So, with due respect, I'd ask if you have the app or name correct?
Thanks, friend, and best respect.
--- edit ---
Oops... was premature... found it and am giving it a try... I'll post my results after I give it a shot...
Click to expand...
Click to collapse
----- edit 2 -----
OK... apparently I'm an idiot... Running Windows 10 Pro, and the installer says it's going to install to an appropriate folder on C:\... yet, trying to find it, it really is weird.... I'm going to try on a VMWare Win 7 virtual PC, and see if I'm able to find it there, and move it to my actual C: drive...
If it works, I'll be grateful for your contribution and praise you to the highest heaven! :laugh:
pauljulian said:
----- edit 2 -----
OK... apparently I'm an idiot... Running Windows 10 Pro, and the installer says it's going to install to an appropriate folder on C:\... yet, trying to find it, it really is weird.... I'm going to try on a VMWare Win 7 virtual PC, and see if I'm able to find it there, and move it to my actual C: drive...
If it works, I'll be grateful for your contribution and praise you to the highest heaven! :laugh:
Click to expand...
Click to collapse
Can't seem to get the beast to work...
If you would be so kind, would there be any way you'd be able to write up a concise step-by-step thing, if you've made it work... I've got the .chm file open on my desktop, and have spent a few hours trying to make it work to no avail.
Again, if it worked for you, your process would be welcome.
Cricket Alcatel Idol 4, 6055U
---------- Post added at 03:36 PM ---------- Previous post was at 02:40 PM ----------
pauljulian said:
Can't seem to get the beast to work...
If you would be so kind, would there be any way you'd be able to write up a concise step-by-step thing, if you've made it work... I've got the .chm file open on my desktop, and have spent a few hours trying to make it work to no avail.
Again, if it worked for you, your process would be welcome.
Cricket Alcatel Idol 4, 6055U
Click to expand...
Click to collapse
My point is that the site recommended seems to insist on Lollipop on the small beast... and there doesn't seem to be a recommendation for the .bin files, and, when installing on Win 10, it seems to install the Sugar app into some directory on my C: drive that is really not that accessible... Did it using a VMWare Win 7 32-bit virtual, and was able to access the directory, copy and paste to my regular C: drive (old Windows geek since Win 3.11... and DOS 3), and it seemed to run... (of course, running as Administrator), but it really doesn't seem to work for me... Again, I freely admit that I'm likely not doing something right, but even after some research and the included .chm file, I seem to be missing something.
Again, and begging your indulgence for seeming like a noob or a rube, but if I'm not making it happen, I rather think that the tips would be lost on someone for whom this is their first Android device...
Kinda frustrating, as, even though I've been a tech-support guy and database developer for more than 30 years, this thing has me stymied...
I found it fascinating for the *#*# command, earlier, from another noble soul, and, obviously, I also found that the device as configured says, basically... "Don't give a damn... you can turn this sucker on, but as soon as you exit this menu, I'm gonna turn it off again."
Just a little frustrating, and it seems that most of the tips and tricks elsewhere seem to be thinking that new owners of the 6055U are running Lollipop.... aaarrrgggghhh....
If it needs Lollipop to work, and if there's a relatively painless way to downgrade, and then upgrade from a ROM, I'm good with that... the Idol 3 seemed to require that, and it worked well for me, with just an evening's work. This one? Cricket seems to have had a warped sense of humor about it... I seriously dig the device, and, since my Idol 3 broke, and my lovely wife's LG G-Stylo (which was a pain in the ass, and next-to-impossible to root, and then be just perpetually stuck at the logo screen with an unfixable boot loop, if one screwed it up, and just required sending the beast back to LG, as long as one took out Cricket's warranty plan... <sigh>), we took the plunge on this one...
Not much for which I require root, but, since I spent good money on some legit apps (and lucked into a few ... ahem... not legit apps that worked for me), these things require root... I know there's a way to do it, and the Sugar app seems promising, but, mildly autistic guy that I am (and 60 years old, with a memory that doesn't work as it used to), a slimmed-down step-by-step doc would be helpful... should some noble soul put such together...
Apparently, the root method has worked for at least one member here.... But this weird old Jewish hippie doesn't see the mental diagram....
Any help would be welcome, my friends and mishpocheh... ("dear family" --- been here enough years, albeit a relatively quiet member, that y'all might as well be family... )
Hey everyone, sorry about the confusion. I installed on Windows 10 pro with no issues. As far as the page I linked you can disregard everything but the app itself. The update that downloads is marshmallow, and I've had no issues overwriting the latest version. I may have gotten sugar from a different location though, as soon as I get a chance I will do a better write up with everything. A helpful way to find the install directory would be right click on the shortcut from the start menu and click find Target / open file location. If it brings you to the folder with the shortcuts do it again and you will have the install directory. The app should be in (install dir)/tool and the downloaded updates go in (install dir)/bin under a folder that only shows up once you start the process within sugar. I will try to compile the information into a more user friendly format tonight but I can't make any promises on that.
Also just to clarify, I didn't use any chm file
I'm wondering if you could upload your version you have on your pc. I just spent the last month in jail here in Orlando fighting a case and the only proof I've got is on my phone on a phone that I deleted my videos on. I really need the videos back too get a not guilty if I gotta pay for it it's cool but I'm out on bond and all the recover videos apps require root
I got this to work last night. Typed up some instructions but didn't get them posted. They're on my PC at home and I'm at work.
Basically use the copy of sugar in the download package in this thread and then start it and let it update https://forum.xda-developers.com/android/development/recovery-vodafone-prime-tab-7-t3548560
Those are the basic instructions too except we don't need to swap out bout and use the TWRP from deckersu thread.
Once flashed it'll automatically reboot. I found you had to make sure you caught this and booted into TWRP right away don't let the phone boot. Then transfer SuperSU in TWRP and flash.
---------- Post added at 11:29 AM ---------- Previous post was at 11:23 AM ----------
Asadullah said:
I'm wondering if you could upload your version you have on your pc. I just spent the last month in jail here in Orlando fighting a case and the only proof I've got is on my phone on a phone that I deleted my videos on. I really need the videos back too get a not guilty if I gotta pay for it it's cool but I'm out on bond an ind all the recover videos apps require root
Click to expand...
Click to collapse
FYI this root method wipes your phone so I don't know if this will help your situation or not.
In sugar there is an option to not wipe, it's under session settings or something to that effect
dbgr said:
In sugar there is an option to not wipe, it's under session settings or something to that effect
Click to expand...
Click to collapse
Wish I had noticed that!! Oh well, stoked to have root and it's good to start fresh. Got Xposed installed today and finally got that annoying charging light turned off. Working on getting wifi tetherng working. Then if I can figure out how to get the dialer to be friends with Google voice this phone will have all its annoyance fixed
Thanks so much for figuring this out and sharing!!
dbgr said:
In sugar there is an option to not wipe, it's under session settings or something to that effect
Click to expand...
Click to collapse
Appreciate the help
woodi5359 said:
https://forum.xda-developers.com/android/development/recovery-vodafone-prime-tab-7-t3548560.
Click to expand...
Click to collapse
Thank you for finding this thread, it is the same one I found but I couldn't remember where it was the other day when I started this thread. Hopefully this will help the people who have been having issues, although I will admit a more painless method would be preferable. I'm currently working on modifying a dirtycow exploit to simply flash the recovery and reboot into twrp, if I get it to work I will zip it all up and post it here.
woodi5359 said:
Wish I had noticed that!! Oh well, stoked to have root and it's good to start fresh. Got Xposed installed today and finally got that annoying charging light turned off. Working on getting wifi tetherng working. Then if I can figure out how to get the dialer to be friends with Google voice this phone will have all its annoyance fixed
Thanks so much for figuring this out and sharing!!
Click to expand...
Click to collapse
I got wifi tethering working I did a lot of things but I believe that did it was adding net.tethering.noprovisioning=true to my build.prop then I went into system/app and changed serviceentitlement.apk into serviceentitlement.oat using es file Explorer
Asadullah said:
I got wifi tethering working I did a lot of things but I believe that did it was adding net.tethering.noprovisioning=true to my build.prop then I went into system/app and changed serviceentitlement.apk into serviceentitlement.oat using es file Explorer
Click to expand...
Click to collapse
I just tested this and it indeed does work. Great find friend!
Asadullah said:
I got wifi tethering working I did a lot of things but I believe that did it was adding net.tethering.noprovisioning=true to my build.prop then I went into system/app and changed serviceentitlement.apk into serviceentitlement.oat using es file Explorer
Click to expand...
Click to collapse
Thanks for figuring this out!!! I'd been messing with it for a few days. The renaming the apk to .oat was the piece I was missing. That and a reboot got it working!!
dbgr said:
Hello all, I found a method to Root and get a custom recovery on our cricket variant, no donations required! You need to find a copy of sugar qct with a username and password, I don't remember exactly where I found it but it shouldn't be too difficult to find. Then you need to let it update to the latest build, which includes the programmer for our phone. If you don't see 6055u in the list it's not up to date. From there, Hook up your phone (may need to manually put it in download mode. Press upgrade and then navigate to the install directory, look in /bin and find where it downloads all the mbm files. Replace the one that starts with an r with the TWRP recovery for 6055. You may have to overwrite it multiple times during the process. If you did it correctly you will be able to boot into TWRP, if not try again. If you don't close sugar I believe it won't overwrite the firmware files, but I haven't messed with it much. I will try to write a tool to make it easier when I have the time but I'm pretty busy. Feel free to pm me with any questions and I will help the best I can.
To get root just install supersu
Click to expand...
Click to collapse
so im getting ready to purchase this device so there is root and twrp for it or no
Dude, did you read the thread at all? I don't mind helping but you gotta do your part. Yes there is TWRP and Root
dbgr said:
Hello all, I found a method to Root and get a custom recovery on our cricket variant, no donations required! You need to find a copy of sugar qct with a username and password, I don't remember exactly where I found it but it shouldn't be too difficult to find. Then you need to let it update to the latest build, which includes the programmer for our phone. If you don't see 6055u in the list it's not up to date. From there, Hook up your phone (may need to manually put it in download mode. Press upgrade and then navigate to the install directory, look in /bin and find where it downloads all the mbm files. Replace the one that starts with an r with the TWRP recovery for 6055. You may have to overwrite it multiple times during the process. If you did it correctly you will be able to boot into TWRP, if not try again. If you don't close sugar I believe it won't overwrite the firmware files, but I haven't messed with it much. I will try to write a tool to make it easier when I have the time but I'm pretty busy. Feel free to pm me with any questions and I will help the best I can.
To get root just install supersu
Click to expand...
Click to collapse
do you hold volume down when it reboots
link22534 said:
do you hold volume down when it reboots
Click to expand...
Click to collapse
It's volume up and power
Just got an update at 2:30CST.
Oh great...now what. Kingroot updated today. It keeps telling me I have root. I don't. But I did fool around with permissions in ADB...I was trying to issue it permissions it didn't have. It only started to tell me I had root after I did that. Though ADB gave me an error when adding some of them.
updated too, no chancelog
This is great! People - use No root Firewall to block OTA so you won't get it because this must mean there is an exploit in 5.3.3.0
savvytechwinner said:
This is great! People - use No root Firewall to block OTA so you won't get it because this must mean there is an exploit in 5.3.3.0
Click to expand...
Click to collapse
Or NetGuard. I bought a license a while back so it can resolve hostnames. I have every Amazon app on wifi lockdown and all of their current known servers and IPS blocked. It takes a bit to get used to and to figure out what apps use what IPs. But I finally got it set up pretty darn good. Still in 5.3.3.0 as well.
---------- Post added at 01:50 PM ---------- Previous post was at 01:42 PM ----------
savvytechwinner said:
This is great! People - use No root Firewall to block OTA so you won't get it because this must mean there is an exploit in 5.3.3.0
Click to expand...
Click to collapse
BTW look out for exploits of the CVE type. Those seem to be what a lot of Android exploits are written from. I managed to get a dirtycow cow sript to run, unfortunately all I got out of it was a wiped internal sdcard and no SuperUser. But it was the first time I've been able to execute a dirtycow script successfully on fireOS. Successful as in at least it ran.
savvytechwinner said:
This is great! People - use No root Firewall to block OTA so you won't get it because this must mean there is an exploit in 5.3.3.0
Click to expand...
Click to collapse
Doubtful - more likely extended feature/functionality (especially around Alexa), optimizations and bug fixes.
Davey126 said:
Doubtful - more likely extended feature/functionality (especially around Alexa), optimizations and bug fixes.
Click to expand...
Click to collapse
It might be Cast Screen. I just noticed they added an option in developers options for the wireless display certification. Also now have access to some Accessibility features that were hidden, almost like usage access but not quite.
DragonFire1024 said:
Or NetGuard. I bought a license a while back so it can resolve hostnames. I have every Amazon app on wifi lockdown and all of their current known servers and IPS blocked. It takes a bit to get used to and to figure out what apps use what IPs. But I finally got it set up pretty darn good. Still in 5.3.3.0 as well.
---------- Post added at 01:50 PM ---------- Previous post was at 01:42 PM ----------
BTW look out for exploits of the CVE type. Those seem to be what a lot of Android exploits are written from. I managed to get a dirtycow cow sript to run, unfortunately all I got out of it was a wiped internal sdcard and no SuperUser. But it was the first time I've been able to execute a dirtycow script successfully on fireOS. Successful as in at least it ran.
Click to expand...
Click to collapse
When you ran C0ward/DirtyC0W/moo it gave you temp root? Interestingly my tablet updated to Fire 5.4 >: | I don't know how. Also KingRoot used a different stragity in the new update - I think they released a few security patches
savvytechwinner said:
When you ran C0ward/DirtyC0W/moo it gave you temp root? Interestingly my tablet updated to Fire 5.4 >: | I don't know how. Also KingRoot used a different stragity in the new update - I think they released a few security patches
Click to expand...
Click to collapse
I never saw a #. All I know it the script ran, finished but I didn't have su so far as I could tell. I tried sudo and su and got "not found". Rootchecker said no root as well. But the internal sdcard storage was completely erased.
EDIT: this is the one I ran: https://github.com/timwr/CVE-2016-5195 It was updated recently to fix the exploit couldn't be downloaded error. It ran for a while too. All the way. At the end said done. I guess it meant done erasing your card lol.
DragonFire1024 said:
It might be Cast Screen. I just noticed they added an option in developers options for the wireless display certification. Also now have access to some Accessibility features that were hidden, almost like usage access but not quite.
Click to expand...
Click to collapse
Quite possible. Amazon and other distributors have been working through ridiculous DRM restrictions in the US and elsewhere. One reason you see additional content now available for download on standard Android devices. Possible they have secured agreements around generic casting. Obviously shameless speculation but I can see those dots being connected.
DragonFire1024 said:
I never saw a #. All I know it the script ran, finished but I didn't have su so far as I could tell. I tried sudo and su and got "not found". Rootchecker said no root as well. But the internal sdcard storage was completely erased.
EDIT: this is the one I ran: https://github.com/timwr/CVE-2016-5195 It was updated recently to fix the exploit couldn't be downloaded error. It ran for a while too. All the way. At the end said done. I guess it meant done erasing your card lol.
Click to expand...
Click to collapse
Here is a question. When an actual SDcard is placed into the slot, what are the permissions? Are they set the same across all devices?
I have 5.4.0.0 waiting in system updates. It's trying to get past my firewall.
I got my 7" 7th gen already updated to 5.3.3.0 rigjt after first power on I went out 10 mins and it updated while I was outside... I'm so unlucky
The firmware is available for download now, so I got it, and extracted the bootloader files.
Surprisingly, the preloader_prod.img and lk.img files haven't changed since 5.3.3.0 (which seems to suggest that a rollback might be possible???) but tz.img and preloader.img have.
The build.prop file contains
Code:
ro.build.mktg.fireos=Fire OS 5.4.0.0
ro.build.version.name=Fire OS 5.3.4.0 (579225620)
They must have been in a hurry... also what about the size? They lost more than 10%...
steve8x8 said:
The firmware is available for download now, so I got it, and extracted the bootloader files.
Surprisingly, the preloader_prod.img and lk.img files haven't changed since 5.3.3.0 (which seems to suggest that a rollback might be possible???) but tz.img and preloader.img have.
The build.prop file contains
Code:
ro.build.mktg.fireos=Fire OS 5.4.0.0
ro.build.version.name=Fire OS 5.3.4.0 (579225620)
They must have been in a hurry... also what about the size? They lost more than 10%...
Click to expand...
Click to collapse
A rollback won't do any good if there's no root.
It's a damn shame when Amazon won't even let you run Live Wallpapers. They really know how to take all the fun out of it. A real shame.
DragonFire1024 said:
It's a damn shame when Amazon won't even let you run Live Wallpapers. They really know how to take all the fun out of it. A real shame.
Click to expand...
Click to collapse
Although I agree with your sentiments Amazon is not alone in that choice. Seen several custom ROMs omit the necessary underpinnings for live wallpapers citing resource consumption (dubious claim IMO) and additional complexity/size for a service that only serves one purpose. Latter might be Amazon's motivation.
Davey126 said:
Although I agree with your sentiments Amazon is not alone in that choice. Seen several custom ROMs omit the necessary underpinnings for live wallpapers citing resource consumption (dubious claim IMO) and additional complexity/size for a service that only serves one purpose. Latter might be Amazon's motivation.
Click to expand...
Click to collapse
I have had a few of the several Live Wallpapers on my XT907 for sometime now. It drains little if any noticable resources and or battery power. Amazon has it set so you can only have wallpapers if the images are uploaded to prime photos.
DragonFire1024 said:
I have had a few of the several Live Wallpapers on my XT907 for sometime now. It drains little if any noticable resources and or battery power. Amazon has it set so you can only have wallpapers if the images are uploaded to prime photos.
Click to expand...
Click to collapse
Well that's a dart in the ass. Really no call for such a restriction IMHO.
Davey126 said:
Well that's a dart in the ass. Really no call for such a restriction IMHO.
Click to expand...
Click to collapse
I can get the wallpapers to run...just not as wallpapers. Activity Launcher brings them out, but They run over the top of everything. And they aren't gifs so I can't upload them and even if I could i would need to register back with Amazon.
Hey i had two Fire HD 10 2019 (9th Gen) Devices.
With one i was playing around, using it casually. I used Amazon Fire toolbox for some personalization, mostly debloating and running it on Nova launcher but as an passionate Android User i wanted Root of curse. Well long story short this Device updated to FireOS 7.3.1.1 because i was not careful enough. But i still have the second (never used or turned on) Device with the not-updated firmware.
Now according to this Post: https://forum.xda-developers.com/showpost.php?p=81211523&postcount=228 it is somehow possible to gain root even if its only temporary (that would be enough for me atm and very nice if accomplishable) but i am actually a bit scared to turn it on and disable OTA with ADB because firstly i am not sure if that is a permanent fix or if i have to apply the command every time i turn the phone on (could possibly be done with tasker or something somilar?) and secondly if the update could be faster than me blocking it (maybe i'm to paranoid right now but i want to make sure i get root on that device and really dont want to miss my chance for it because of OTA updates.
Also i tried to root it but without sucess (well i didn't know there was another hard button combination when the white triangle was showing so i was really close away from the finish line it feels like) then i went to sleep and the next morning i had the new update applied.. really unfortunate. Well thatswhy i want to make a better job with the second device!
Thanks in advance for any help! Have a wonderful day and excuse any typings
M4XXX said:
Hey i had two Fire HD 10 2019 (9th Gen) Devices.
With one i was playing around, using it casually. I used Amazon Fire toolbox for some personalization, mostly debloating and running it on Nova launcher but as an passionate Android User i wanted Root of curse. Well long story short this Device updated to FireOS 7.3.1.1 because i was not careful enough. But i still have the second (never used or turned on) Device with the not-updated firmware.
Now according to this Post: https://forum.xda-developers.com/showpost.php?p=81211523&postcount=228 it is somehow possible to gain root even if its only temporary (that would be enough for me atm and very nice if accomplishable) but i am actually a bit scared to turn it on and disable OTA with ADB because firstly i am not sure if that is a permanent fix or if i have to apply the command every time i turn the phone on (could possibly be done with tasker or something somilar?) and secondly if the update could be faster than me blocking it (maybe i'm to paranoid right now but i want to make sure i get root on that device and really dont want to miss my chance for it because of OTA updates.
Also i tried to root it but without sucess (well i didn't know there was another hard button combination when the white triangle was showing so i was really close away from the finish line it feels like) then i went to sleep and the next morning i had the new update applied.. really unfortunate. Well thatswhy i want to make a better job with the second device!
Thanks in advance for any help! Have a wonderful day and excuse any typings
Click to expand...
Click to collapse
Try it to use NoRoot Firewall (VPN firewall) from Google Play, enable Stat on Boot, create VPN connection, select APPS tab, find DeviceSoftwareOTA app from list and set the check box to X (deny any internet access) on Wi-Fi and mobile data
Check boxes:
√ = Allow from internet access
X = Deny from internet access
@Supersonic27543 @dr_docdoc @diplomatic @DB126
Can somebody please confirm this? I can not trust this dude anymore regarding his latest posts. I think he is a troll in some sort..
I was thinking about adb shell pm hide but yeah as i said i have the concerns mentioned above.
M4XXX said:
@Supersonic27543 @dr_docdoc @diplomatic @DB126
Can somebody please confirm this? I can not trust this dude anymore regarding his latest posts. I think he is a troll in some sort..
I was thinking about adb shell pm hide but yeah as i said i have the concerns mentioned above.
Click to expand...
Click to collapse
I simply followed this post (below), and so far . . . no updates. As the OP suggests, others have suggested to him this *MAY NOT* be permanent. However, as the OP also reports, he had another device for 7 months with no update or even check for update. On all seven of my Fire HD 10 2019 devices, no update has occurred or even been checked - just the same:
https://forum.xda-developers.com/showpost.php?p=81095517&postcount=147
As for the adb shell stuff, that is beyond my current understanding. Learning about the bootless root that @diplomatic put together, I'm wondering that perhaps there is a script method that can be loaded after boot to ensure OTA is disabled every time. But then again, I'm not aware if it would still be considered permanent or what could re-enable the OTA (as the OP to post 147 above had said in the following post 149).
dr_docdoc said:
I simply followed this post (below), and so far . . . no updates. As the OP suggests, others have suggested to him this *MAY NOT* be permanent. However, as the OP also reports, he had another device for 7 months with no update or even check for update. On all seven of my Fire HD 10 2019 devices, no update has occurred or even been checked - just the same:
https://forum.xda-developers.com/showpost.php?p=81095517&postcount=147
As for the adb shell stuff, that is beyond my current understanding. Learning about the bootless root that @diplomatic put together, I'm wondering that perhaps there is a script method that can be loaded after boot to ensure OTA is disabled every time. But then again, I'm not aware if it would still be considered permanent or what could re-enable the OTA (as the OP to post 147 above had said in the following post 149).
Click to expand...
Click to collapse
Thank you very much for the help. I know I can not speed things up, from a development standpoint but I also wanted to use it until there is a viable root option available
M4XXX said:
Thank you very much for the help. I know I can not speed things up, from a development standpoint but I also wanted to use it until there is a viable root option available
Click to expand...
Click to collapse
Yo - I think you missed it!
This sucka HAS BEEN ROOTED!
https://forum.xda-developers.com/hd8-hd10/general/fire-hd10-2019-t3979343/post81211523#post81211523
dr_docdoc said:
Yo - I think you missed it!
This sucka HAS BEEN ROOTED!
https://forum.xda-developers.com/hd8-hd10/general/fire-hd10-2019-t3979343/post81211523#post81211523
Click to expand...
Click to collapse
I've seen that Post and i was REALLY excited about it but i couldn't get it to work.. Could you eventually guide me on the way?
Need help with Step 9 !?!?
https://forum.xda-developers.com/showpost.php?p=79626434&postcount=135
I am stuck at Part 9 !!
when i restart at this point nothing happens and when i start init.d scripts support app and "run scripts now"" i get the following execution results:
Code:
[COLOR="Red"]Can't aquire root privileges (date)[/COLOR]
[B]Executing scripts from /storage/emulated/0/init.d (date)[/B]
suboot.sh
[COLOR="red"]/storage/emulated/0/init.d/suboot.sh[121]: ./mtk-su: No such File or Directory[/COLOR]
In Magisk Manager i see that Magisk is not installed (and i can't without TWRP, right?)
I'm just stuck at this Point. I have read in some other Forum that there is a button combination that i can press while seeing that white triangle when trying to enter recovery mode to actually be able to enter it. and yeah from there on it would be easy i guess to install magisk and maybe init.d will recognize it then?
Thanks for helping
I got it to work! Thanks to the incredible help of @dr_docdoc :good:
I picked arm64. By changing to arm it worked
Very happy about it. thanks again!
I guess no luck when you are on 7.3.1.1?
BXM500 said:
I guess no luck when you are on 7.3.1.1?
Click to expand...
Click to collapse
not for now as far as I know it. my other device isn't working either
x
Try this:
Code:
adb shell pm disable-user com.amazon.device.software.ota
adb shell pm disable-user com.amazon.device.software.ota.override
adb shell pm disable-user com.amazon.kindle.otter.oobe.forced.ota
adb shell pm disable-user com.amazon.settings.systemupdates
Remove Amazon's crappy and stubborn Fire launcher (you must have another launcher installed before you do this):
Code:
adb shell pm disable-user com.amazon.firelauncher