Related
All,
I have an HD+ running 2.0.5 and its rooted. When I've turned on wifi, half the time it tries to update to 2.0.6. It always goes through its process then dies at 99% and drops back telling me that something is wrong. The first time I freaked out and thought something really WAS wrong.
Boy was I relieved to see that I still had my stock root.
I was just thinking that maybe I should update to 2.0.6 just to keep it current. I use the Nook side for reading and stuff as it is. Can I just rerun the root process like I did for 2.0.5?
Also what is the best way to make it not fail the update?
I did the white-on-white fix, but changed it back.
Please don't tell me I need to do the 8 boot factory reset.
Thanks,
-Jeff
How did you change back the white on white? I suspect that is what is wrong.
Sent from my Nook HD+ running CM10 on Hybrid SD
Since the fix made a backup of the original file, I just renamed the original back to it's proper name.
I moved the orig to a new temp name. Then I copied the active "fixed" one to a something.bak or something like that.
Then I renamed the original one (with the temp name) back to the original/active name.
Upon renaming it crashed, and rebooted. The w-o-w fix was gone.
BTW, looking back at that description it's a bit messy. If it doesn't make sense I'll just put the commands down (as I recall them)
-Jeff
js5752 said:
Since the fix made a backup of the original file, I just renamed the original back to it's proper name.
I moved the orig to a new temp name. Then I copied the active "fixed" one to a something.bak or something like that.
Then I renamed the original one (with the temp name) back to the original/active name.
Upon renaming it crashed, and rebooted. The w-o-w fix was gone.
BTW, looking back at that description it's a bit messy. If it doesn't make sense I'll just put the commands down (as I recall them)
-Jeff
Click to expand...
Click to collapse
No, I understand what you did. You left the symlink in /system and just manipulated the files in /data. That works to get rid of white on white, but does not put framework-res.apk back in /system. And the update zip needs framework-res.apk there. That is why it was failing.
Did you do a back up of your system before you added white on white like I recommended? If so, restore that and then update. If you did not, you can try putting that original framework-res.apk back in /system/etc via ADB. Doing it with ADB prevents that crashing you experienced the first time.
As a last resort go back to 2.0.0 with my plain stock zip in my HD/HD+ CWM thread. You can flash that and it will not erase your media files. You should backup your system with CWM first. Then wipe /data, then flash the zip. Then sign on, register and it will update you to 2.0.6. Then go to CWM and do an advanced restore of /data. Then flash again the zips you want, like root or gapps. Then you should be ok.
Edit: If you want to keep 2.0.5 and not be bothered by those attempts to update, I just added to both my Tips thread and my CWM thread linked in my signature a method to stop those updates.
Sent from my Nook HD+ running CM10 on Hybrid SD
Thanks for the reply.
I expected the crash from what I had read. I just decided that ADB was more hassle than it was worth for a quick change. That and I like to live dangerously
Ok, the symlink vs the data file makes sense. Now I understand why it wasn't working. Thank you, because I thought all was back where it should be.
As for backups, I did one before rooting, and I've done a couple since just to make sure I've got backups. That plus titanium, I figured I should be able to recover if the worst happens.
Thanks for the tips, and for all the work you've done on rooting these devices. It was the option to root that tipped me over the edge to buy one, and I'm glad I did.
-Jeff
I rooted my HTC One M7 yesterday and I tried to modify the screen dpi from the build.prop via different apps and text editors. But everytime I rebooted the phone, the saves were lost.
Marsustorm said:
I rooted my HTC One M7 yesterday and I tried to modify the screen dpi from the build.prop via different apps and text editors. But everytime I rebooted the phone, the saves were lost.
Click to expand...
Click to collapse
/system partition is write protected by the kernel. Use an unsecured kernel or push your modified build.prop file from a custom recovery.
Btw modifying files in /system will cause issue with future ota updates.
Would you mind giving me a step by step instructions for the easier one? I'm pretty new to the Android scene.
Edit: I'm doing this to play HS on my phone (on the regular setting it says that a 6'' screen is required)
Marsustorm said:
Would you mind giving me a step by step instructions for the easier one? I'm pretty new to the Android scene.
Edit: I'm doing this to play HS on my phone (on the regular setting it says that a 6'' screen is required)
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=57570982&postcount=2
Hello
I've got the Note 5 SM-N9208 and I am trying not to root (tripped Knox tho as I but Phillippines system.img on it) it as the annoying Barclays App doesn't work.
I am however, trying to add my custom CA certificate into the /system/etc/security/cacerts folder. This is what I used to do in my rooted devices before and worked fine.
I have flashed TWRP and taken a full backup (thank God!) and then mounted the system as RW, copied the file, rebooted and voila, boot loop on the Samsung Note 5 screen.
The only fix is to reflash the system partition from the original TAR file which makes me wonder - is there a mechanism that prevents system from being modified if the device is unrooted? Something like Samsung's system protection or something.
Could anyone try to reproduce the issue on an unrooted phone just to see if it's just me being unlucky? Or is is simply not possible to modify system without root? If so, how come TWRP allows me to do so?
Let me know what you think guys
Looking forward to hear someone else's opinion.
mateuszd said:
Hello
Let me know what you think guys
Looking forward to hear someone else's opinion.
Click to expand...
Click to collapse
You must be rooted to make system changes.
You need to make some changes in ramdisk : remove support_scfs,verify from the fstab files for system partition
Im running truepure Rom. Would love to have android pay working, but just cant get it going. Assuming will have to live without for a while...
I have it installed on the stock rooted MM (soak test) and my card is loaded. I have not had a chance to actually use it yet. There aren't many retailers that accept it yet. If I get a chance to use it I'll report back.
rsmiff said:
I have it installed on the stock rooted MM (soak test) and my card is loaded. I have not had a chance to actually use it yet. There aren't many retailers that accept it yet. If I get a chance to use it I'll report back.
Click to expand...
Click to collapse
As I understand, Android pay pretty much only works works with stock ROM due to system system Partition Modifications made on custom Rom's. I understand some devices have had limited luck with Custom Roms but for the most part, Stock only. All that said, I just upgraded to MM 6.0 on Friday and then Rooted using the Beta System less Root method from the forum and Android Pay works like a charm, added cards no problem and works perfect at the retailers that accept it. Most recently, RiteAid in my area. This root is not a full root as I understand but the apps I use get permissions without an issue , Quick Boot is my must have and it works just fine. (Did notice ES File Explorer wont' allow full access to my device but Root Browser did. Adding XPOSED would still disable Android Pay since it modifies the partititons , I really wish that was not the case but I really love Android pay so for now, I might just have to do without it. I am sure you saw the Root Method but just in case, the link is below. Follow the instructions carefully and don't forgot to hit the Do Not Install button in TWRP (Your device does not appear to be rooted) every time you reboot from there . You'll know what I am talking about as soon as you get to that point.
Anyway, good luck!
Mike
http://forum.xda-developers.com/moto-x-style/development/wip-systemless-root-t3263405
EDIT: And I broke pay somehow... So I guess this is not a great guide...
I am having Android pay working on a slightly modded stock rooted MM.
- I did the OTA process (back to stock and side loaded the OTA)
- Installed and setup Android Pay (including cards)
- Installed TWRP 2.8.7.1 in fastboot (link)
- Rooted with Chainfire's systemless autopatcher (link)
- Renamed system\recovery-from-boot.p to .bak in TWRP
- Installed No increased ringtone in TWRP (link)
- Installed and setup AdAway
- Android Pay is still working, I tested it at the vending machine at work.
I have not tried to add the new Google dialer (link), someone in the thread say it doesn't break Android pay.
timeToy said:
I am having Android pay working on a slightly modded stock rooted MM.
- I did the OTA process (back to stock and side loaded the OTA)
- Installed and setup Android Pay (including cards)
- Installed TWRP 2.8.7.1 in fastboot (link)
- Rooted with Chainfire's systemless autopatcher (link)
- Renamed system\recovery-from-boot.p to .bak in TWRP
- Installed No increased ringtone in TWRP (link)
- Installed and setup AdAway
- Android Pay is still working, I tested it at the vending machine at work.
I have not tried to add the new Google dialer (link), someone in the thread say it doesn't break Android pay.
Click to expand...
Click to collapse
I have Android pay working here. stock MM and systemless root. I did try flashing the dialer zip and it did break Android pay. However I moved the required files into place using root explorer and set the correct permissions, and Android pay works no problem.
So it seems that flashing zips that modify the system partition in any way will break Android pay, but not if you modify it while in the OS itself. I've been using the cigital safteynet playground app to check each time I make a modification. Definitely make a backup of /system so you can always restore Android pay functionality if a mod breaks it.
Also using Xposed WILL break Android pay. I try not to miss it much, but honestly I've got my MXPE pretty much perfect for me, and what apps I use that require root are all working well with systemless root.
Sent from my XT1575 using Tapatalk
timeToy said:
- Renamed system\recovery-from-boot.p to .bak in TWRP
Click to expand...
Click to collapse
What does this do?
EVR_PR said:
What does this do?
Click to expand...
Click to collapse
This prevent the stock recovery from overwriting TWRP
I actually have TWRP in read only mode, which allows stock to overwrite it, and the file ends in .p.
Will changing it to .bak allow me to remove the read-only status?
bb12489 said:
However I moved the required files into place using root explorer and set the correct permissions, and Android pay works no problem.
Click to expand...
Click to collapse
Any chance you'd be willing to elaborate on this a little? (i.e. which files, where and the correct permissions)
Thanks!
innoman said:
Any chance you'd be willing to elaborate on this a little? (i.e. which files, where and the correct permissions)
Thanks!
Click to expand...
Click to collapse
Well the flashable zip as the folder structure laid out inside it, so just use that to know where to move the files. Usually the permissions are rw-r-r in most folders, but just check other files in the directories to make sure what permissions to set. That's all I've done to get the dialer working at least. I imagine it works for other things as well.
bb12489 said:
I have Android pay working here. stock MM and systemless root. I did try flashing the dialer zip and it did break Android pay. However I moved the required files into place using root explorer and set the correct permissions, and Android pay works no problem.
Click to expand...
Click to collapse
That didn't work for me, I was able to install the 3.2 dialer just fine using root explorer, but it break Android Pay (Fail Cigital Safteynet Playground)
I try step by step install, testing with Cigital after every step, it fail when I copy the Google Dialer folder to pri-app. How did you do?
timeToy said:
That didn't work for me, I was able to install the 3.2 dialer just fine using root explorer, but it break Android Pay (Fail Cigital Safteynet Playground)
I try step by step install, testing with Cigital after every step, it fail when I copy the Google Dialer folder to pri-app. How did you do?
Click to expand...
Click to collapse
I followed the same steps that bb did and am getting the same results you are. Android Pay was working just fine with systemless root and Adaway, but so far, DPI changes and the Google Dialer have both broken Android Pay for me.
I lost it manually installing the new emoji font pack and google keyboard. I manually copied the files over and fixed the permissions.
I'm stock UK, but I keep getting a popup saying Android Pay isn't available in the UK
Jay794 said:
I'm stock UK, but I keep getting a popup saying Android Pay isn't available in the UK
Click to expand...
Click to collapse
That's because it isn't but it should be coming to the UK in the next few weeks according to rumours.
Sent from my LG-D855 using Tapatalk
Hello!
So I have become a crazy cat collector with Nougat. But I recently switched roms so I dont have my beautiful cats anymore. :crying: What files can I copy from my old rom to get them back into my new one?
I found this article:
https://www.reddit.com/r/Android/comments/4tualq/what_i_know_about_cats_the_android_nougat_easter/
It didn't specifically say that cats can be restored but i tried copying the xml file from directory below. But it was a no-go
/root/data/data/com.android.egg/shared_prefs/mprefs.xml
Is there anyway I can be reunited with my cats. Please let me know.
God Bless
-The Cat Lady
You could try backing up the android easter egg app in tibu and restoring data when you flash the rom. I haven't tried it, so if you feel like taking a risk go for it.
CollinsB said:
Hello!
So I have become a crazy cat collector with Nougat. But I recently switched roms so I dont have my beautiful cats anymore. :crying: What files can I copy from my old rom to get them back into my new one?
I found this article:
https://www.reddit.com/r/Android/comments/4tualq/what_i_know_about_cats_the_android_nougat_easter/
It didn't specifically say that cats can be restored but i tried copying the xml file from directory below. But it was a no-go
/root/data/data/com.android.egg/shared_prefs/mprefs.xml
Is there anyway I can be reunited with my cats. Please let me know.
God Bless
-The Cat Lady
Click to expand...
Click to collapse
This might work but it also might crash your phone. Proceed at your own risk.
I was wondering if you ever figured out a way. I'm using a Nexus 5X so it's only a matter of time before the bootloops plague my device. Was hoping to back them up before then.
EDIT:
Would using ADB work?
Code:
adb backup -f "C:\CatsBackup20161229.ab" -apk com.android.egg
EDIT 2:
I was so close. Thanks to this Reddit post, I have used the following in a Windows Batch File to backup my Cats with a timestamp. Hope this helps any Googlers.
Code:
adb root
adb backup -f C:\CatsBackup_%date:~-4,4%%date:~-10,2%%date:~-7,2%.ab com.android.egg -system
What I'd done was long press the cat when one came up then just shared it to my Drive folder. I've also found duplicates will most likely come up (number of the cat) but the cat will be different color.
I've personally flashed numerous different nougat ROMs and different versions (7.0, 7.1, 7.1.1) in no particular order, and the Easter egg cat collection got backed up and restored on each and every ROM I've tried and used.
The way I go about this is, before I decide to switch ROMs or update using clean flash, I use titanium backup to backup the Easter egg app. Once I clean install an update or a different nougat ROM, I first unlock the nougat Easter egg in settings (tap the Android version a bunch and long press on the N animation to find the cat icon). Then head over to quick toggles, hit edit, find the cat toggle and add it to a desired slot. Finally, in titanium backup, find the Easter egg app, hit restore. It will ask what to restore, make sure you select "data only," do NOT restore "app + data," this may or may not cause system UI issues.
Requirements: Nougat ROM of your choice (any version) and root access.
This method works for restoring chrome tabs and possibly a few other system apps' data. Restoring system app(s) + data, however, will usually break things, so make sure to only restore the respective system apps' data only.
okay so i got the easteregg.ab file to back up onto my local disk, but i cannot get my phone to restore the .ab file through ADB.
ADB will say that i must unlock my device and allow the restore to complete however the phone is completely unresponsive to the request to restore, it as if nothing is happening.
what am i missing here :
adb backup -f easteregg.ab com.android.egg -system
(that puts an easteregg.ab file into c\users\xxxx)
then : adb restore c\users\xxxx
(adb then tells me "Now unlock your device and confirm the restore operation)
.....but nothing has happened and it asks for nothing on my phone and the cats are not loaded =(
Permissions. Were they set on the file when you restored it?
Strephon Alkhalikoi said:
Permissions. Were they set on the file when you restored it?
Click to expand...
Click to collapse
im not sure if i know which permissions your refering too, but the easteregg.ab file permissions are currently set to allow full control for the System, Administrator and the User.
How do i ensure the permissions are correct ?>
The permissions were likely completely stripped from the file when it was sent via ADB. You'll need to root and do one of the following.
*Use a terminal app to set permissions.
*Use a file manager with root access, navigate to the file's location, and set permissions manually.
The correct permissions are likely rw-r--r--, which uses the number 644.
Strephon Alkhalikoi said:
The permissions were likely completely stripped from the file when it was sent via ADB. You'll need to root and do one of the following.
*Use a terminal app to set permissions.
*Use a file manager with root access, navigate to the file's location, and set permissions manually.
The correct permissions are likely rw-r--r--, which uses the number 644.
Click to expand...
Click to collapse
My s7 edge is not rooted.
Is there anyway to restore the easteregg kitties with out root ? i thought that was possible.
Did you downgrade from a Nexus 6 to a S7? Sorry to hear that if true, because the S7 has a locked bootloader. The file likely never transferred to where you wanted it to go, as the locked bootloader would prevent that. Thus you need to unlock the bootloader to even transfer the file. ADB may have commands to set file permissions, but my recollection on that is hazy. It would also be irrelevant if the bootloader cannot be unlocked.
Strephon Alkhalikoi said:
Did you downgrade from a Nexus 6 to a S7? Sorry to hear that if true, because the S7 has a locked bootloader. The file likely never transferred to where you wanted it to go, as the locked bootloader would prevent that. Thus you need to unlock the bootloader to even transfer the file. ADB may have commands to set file permissions, but my recollection on that is hazy. It would also be irrelevant if the bootloader cannot be unlocked.
Click to expand...
Click to collapse
oh wow! i pulled up this thread last night and didn't even realize i was on the nexus 6 groups forums haha, boooooo on me =(
no i didnt down grade lol, i never had the nexus, i am just a s7 edge owner who doesn't want to loose their kitties in a phone swap =(
and yeah i had some real difficulties getting the .ab file to even save to my computer after messing around with a bunch of variations on commands through adb.
now im getting depressed again
..hey i REALLY appreciate all this help btw =\
Sorry to hear that. But unfortunately, unless you can unlock the bootloader, you're not going to be able to use ADB to transfer the file back. With a locked bootloader you can pull files, but not push them.
I shoulda realized that cause im not new to the rooting process at all and i hate having a phone with a locked bootloader but i really do like the s7 edge, it grew on me,....... alas my kittens will have to wait till the bootloader becomes available.....
Check the S7 Edge forums. I'm sure they have something that may help.