Related
Who is affected? All devices pre-gingerbread
Who should act? Users and developers using pre-gingerbread roms
How do I fix? Flash attached .zip at the bottom of this post
What if I think I was infected? Completely wipe your device, format sdard, go back to stock and re-apply rom, then flash the attached .zip (before installing any apps)
Why should I care? read below...
http://www.androidpolice.com/2011/0...your-phone-steal-your-data-and-open-backdoor/
Flash this with ClockWorkMod.... this is for any Pre Gingerbread ROM.... ie TNT anything, VEGAn 5.1.1 and below, Zpad anything, GAdam anything.
This is not necessary for any ROMS based off Gingerbread AOSP or CM7. Including VEGAn-TAB Experimentals.
Be Safe.
Even More Details here: http://www.androidpolice.com/2011/0...-android-nightmare-and-weve-got-more-details/
I checked out the zip and it just adds a blank text file (0 bytes) called profile to the /system/bin folder. So I am not sure what the fix is?
**EDIT** Nevermind it is a dummy file meant to prevent the virus. Thanks to the OP for providing this.
http://www.androidpolice.com/2011/0...your-phone-steal-your-data-and-open-backdoor/
Nasty stuff. I would say this patch is high priority and I'm already going through my own ROMs to add it in.
http://forum.xda-developers.com/showthread.php?t=977154
Link above has info on creating the file manually.
Jim
fyi -
http://www.pcworld.com/article/221213/keep_malware_off_your_android_phone_5_quick_tips.html
Lookout mobile security . In case you cannot find it via the market.
http://www.getjar.com/Lookout-Mobile-Security-with-Antivirus
Edit. I just installed the lookout app to scan my tab, everything was fine and then, i un-installed it since it was running on the background and taking 10% of the cpu..
Anyways, a nice app that can be used to do a quick scan..
I don't have a stock gtab but I'll ask anyways... how can our stock rom users be protected? Is there an alternate method?
Edit just saw the manual process. Im guess that's the way to go.
xmr405o said:
I don't have a stock gtab but I'll ask anyways... how can our stock rom users be protected? Is there an alternate method?
Edit just saw the manual process. Im guess that's the way to go.
Click to expand...
Click to collapse
I'd curious to see what all the vendors are going to do about this. Granted, they could just say that the Market is not there, but regardless the security hole is still there and needs to be plugged up.
Hi,
I hope that this isn't too offtopic, but I was trying to create /system/bin/profile using a term and su, and when i went into root explorer to make /system/bin R/W, root explorer showed the dir as R/W already, and as mounted on /dev/loop9.
Is that normal?
I haven't installed dataloop, at least intentionally, so it seems strange that /system/bin would be mounted there, plus it being R/W by default?
FYI, I use z4root to get temp root. Could that be why /system/bin is R/W?
Then again, that wouldn't explain the /dev/loop9 mount ...
Jim
jimcpl said:
Hi,
I hope that this isn't too offtopic, but I was trying to create /system/bin/profile using a term and su, and when i went into root explorer to make /system/bin R/W, root explorer showed the dir as R/W already, and as mounted on /dev/loop9.
Is that normal?
I haven't installed dataloop, at least intentionally, so it seems strange that /system/bin would be mounted there, plus it being R/W by default?
FYI, I use z4root to get temp root. Could that be why /system/bin is R/W?
Then again, that wouldn't explain the /dev/loop9 mount ...
Jim
Click to expand...
Click to collapse
Hi,
Creating the profile file manually, it wouldn't persist,i.e., it was gone after rebooting, so I installed gojimi's zip usung CWM, and that worked.
I also did a mount w/o getting temp root, and /system/bin is not on /dev/loop9, so I'm guessing that when z4root sets temp root, it might be remounting /system/bin on /dev/loop9 itself.
Jim
You would have to download one of those sketchy apps to really be affected anyways, right? Who would do that?!
Appreciate the patch. This highlights the two problems with android though, google fixed this security issue in 2.2.2, but most carriers still haven't released that update. And the market needs some oversight, not authoritarian apple like, but some.
Sent from my T-Mobile G2 using XDA App
Is it possible to sticky this thread
Mods is it possible to sticky this thread so that it is easily visible.
Thanks
Hello guys. Is there a way to find out if our tablet is infected or not?
I mean if we have installed any of the apps in the list that automatically means that we are infected or not?
If infected what is preferred to do wipe the tablet or go back to stock rom??
Is there any manual for windows 7 noobies users?
Thanks.
Doctor LeVa said:
Hello guys. Is there a way to find out if our tablet is infected or not?
I mean if we have installed any of the apps in the list that automatically means that we are infected or not?
If infected what is preferred to do wipe the tablet or go back to stock rom??
Is there any manual for windows 7 noobies users?
Thanks.
Click to expand...
Click to collapse
Please read the thread completely, it is stated you can download lookout security to run a scan to see if you are infected.
downloading.....see what happens
There is a DroidDreamKiller app that allows you to check to see if you are already infected and install the patch. There is also a beta test app that gives you other information. Just search the market for DroidDreamKiller.
To devs: Thank You
TO Everyone else DO THIS ASAP
How do I flash the zip file after downloading it?
Thanks
Start cwm using volume up while powering on.
Once menu comes up select install zip using vol buttons
Use home to select.
Navigate to where you saved zip file
Select it with home button
Once install complete reboot from cwmod
MODs Please make this a sticky . It is being overlooked.
THIS METHOD IS NO LONGER WORKS as of update version 2.0.5 and higher.
Please visit this thread instead for the current rooting method.
Posting in this thread will get you nowhere, let it RIP.
ANNOUNCEMENT:
If you have a new Nook HD/HD+ and want to root and get the GAPPS running, you should follow the guide at the All-in-One thread instead. That said, I won't copy all the information here to there, so you should continue to read on.
Let me start by saying that I didn't come up with the working root method. The original root instruction came from verygreen in this thread. And I am not a developer, I merely have a few linux background and even less so in the Android. I worked on this on my spare time by myself.
I merely take what was working, but unusable to make it usable. I found something that he is missed. This may actually be working on Nook HD (non-plus) also, but since I don't own one I can't say that it will.
Disclaimer:
If something gone wrong, it's all your fault. I take ZERO responsibility for what happen to your device, your life, your wife/husband, your kids, your unborn child and etc. You get the idea.
Background:
When I found out the root doesn't actually work past a reboot, I start looking what actually cause the Nook to be pissed and factory reset itself. Well, it seem that the /system and anything in there is basically coming from a /dev/block/mmcblk0p8 And if something got change, Nook get pissed and do a FULL FACTORY RESET(I'll explain in a moment). Well, at least I start investigated under that idea.
What I found:
What I found, or at least what I think I found is that, probably just adding file, or increase in the size(maybe there is a threshold for this), will cause it to do a full factory reset. What I also found is that there is a $PATH for /system/sbin but not pointing to anywhere. So I come up with the idea of making another ext4 file system in a file and loop mount it to /system/sbin I guess that work(very well). What I also found is that, there are two kind of factory resets. The one that you perform yourself, which is actually not a full factory reset and the one that Nook get pissed and do the full one.
A factory reset that you perform yourself, whether from the GUI or button combination will basically clean the partition /data while a full blown one will basically restore other partition such as /system
What is included:
basically a zip file, inside that zip file are 6 files.
boot_complete_hook.sh.bak this is basically a modified version of verygreen's
busybox & su are basically from his thread
superuser.apk well I found this one floating around and seem like a good idea to stick it in there (not even sure if it gonna work w/ Nook)
makeroot.bat this is basically what do most of the work. It's base on verygreen original rooting instruction.
sbin_mount This is basically an ext4 file system which have su and another version of busybox all setup nice and tidy for you all. This version of busybox is 1.20.2r2 which I grabbed from here.
Prerequisite:
ADB, it's your responsibility to have adb up and running, meaning not just have it install, but it can see your nook also.
leapinlar wrote a post to help you getting ADB to work here.
Now to get root:
all you have to do is unzip it and run makeroot.bat (obviously you run this in windows command prompt). Yub that's all. The batch file will do the rest, including reboot the nook and wait for it to reboot and stuff. Won't make a coffee for you though.
The manual and hard way:
well, I will only explain this in a summarize way. Basically this start with verygreen rooting method. It basically take advantage of the exploit and run /data/boot_complete_hook.sh which you adb push yourself(with correct permission) with root privilege. What you can run in there is basically up to your creativity. So obviously in this case, you mount the sbin_mount as an ext4 filesystem in the /system/sbin You can make this file yourself if you want to, in linux using dd and mkfs command. Basically using dd to create a file volume to the size you want and mkfs to format it to ext4. Mount it and start uploading stuff you want in there. You will have to correct all the file permission as well. Since all of this will be mounted to /system/sbin you should be aware what you gonna put in there. I guess I could make this thing 100MB, but for this specific purpose 10MB is enough. I my case, just the su and busybox and the symbolic links for the busybox. I'm doing this for the long term. I'm too lazy to point to busybox everytime I wanna do something.
What to do afterward:
Now that you have root, you can Enable Unknown Source to allow you to install app from within the device and install GAPPS. Follow the two guides below if you interested.
Enable Unknown Source: Again, I make an easy little tool for you here.
GAPPS: here.
Did I missed something:
Well, as I said I'm no coder so if I didn't do a clean job, you can refine it. If I didn't document or give proper credit, then I guess I missed that. Sorry about that, again I'm no coder and never done this. And finally:
If this thing work for you, feel free to hit that "THANKS" button. I spent many hours trying to come up with this solution.
FAQ:
Q: My so and so application when attempting to have root access get freeze up, or superuser doesn't work?
A: Well, I'm not sure if this is dued to how the Nook side-loading work or not, but it seem for some reason superuser won't start by itself. So you have to start it manually the first time.
Q: I type in "adb root" and I can't get in as root, it doesn't work?
A: yes it does, it's just not working with adb root. You can get in via "adb shell" once you get in, type in "su" and you can see that you now should have root access.
Thank you so much! This works perfectly. Survives reboot.
here's the Linux version.
Thanks someone0 for getting this started.
Haven't fully tested the linux version, but it loads and starts up, so should work.
extract, and open up terminal and navigate to the dir you extracted to, and type
./makeroot.sh and then enter.
This sounds like a good idea initially.
It is true that the B&N does not just check for /system/xbin/su directly like they did in the past.
This time they check for something else and I just had no time to look into it more deeply to find out what is it they are actually checking for. I plan to figure this out on Friday when I am back home.
Also wanted to tell you that having Linux background is a great thing when tinkering with Android (at a low level, anyway). I don't have much Android background to speak of as well.
This works really well, and thanks to Someone (and mad props too) for getting persistent root working on this.
I may be being very naive, but my suspicion on the reboot is around the manifest file that's present at root.
It seems to be generated by the boot process and it might provide a quick and dirty list of what's permitted on the device to check. With persistent root, lots of investigation becomes a lot less painful. I expect that by end of day we'll have install unsigned running.
Early in my experimenting with the HD+, I noted:
- some versions of the Google Services Framework can be installed via adb
- when I launched the native calendar app after installing gsf, it wanted to sync to a google account, and was able to add the google account
- one version of the Play store installed and launched as far as throwing the 'you must accept the terms of service' before crashing
What BN most likely does is calculating the hash value (or digest, if you prefer) of certain system files that they think shouldn't be tampered with, then during reboot, the values of these files must match, or they will do a factory reset.
The key point is to find out where they do these checks and fool the check.
This sound simple but it depends on how they implement it. If they use binary decisions (like if the hash_value == calculated), then it is easy to get around. If not (e.g. using white box algorithm to hide keys), then it get more complicated.
excellent and very elegant solution. Kudos!
I'm heading out to work, and if you think your theory is right, try poking around with it. Now that your have root, you can try to dd those bootloading partitions out to user area and upload them out to PC and inspect them.
looking at the vold.fstab
Code:
xloader -> /dev/block/mmcblk0p1
bootloader -> /dev/block/mmcblk0p2
recovery -> /dev/block/mmcblk0p3
boot -> /dev/block/mmcblk0p4
rom -> /dev/block/mmcblk0p5
bootdata -> /dev/block/mmcblk0p6
factory -> /dev/block/mmcblk0p7
system -> /dev/block/mmcblk0p8
cache -> /dev/block/mmcblk0p9
userdata -> /dev/block/mmcblk0p10
Be extra careful when touching those partition if you not sure, don't touch them. But making a block copy of them and taking them out should be relatively easy and safe. Obviously you gonna need a Linux box to do this. I setup a VM on one of my PC last night because I need to get a ext4 partition and put all the goodies in there.
krylon360 said:
here's the Linux version.
Thanks someone0 for getting this started.
Haven't fully tested the linux version, but it loads and starts up, so should work.
extract, and open up terminal and navigate to the dir you extracted to, and type
./makeroot.sh and then enter.
Click to expand...
Click to collapse
Just wonder why do use a zip file for the linux version? Wouldn't this kinda messup the permission when compress/uncompress? meaning, makeroot.sh may not have the proper permission when unzip. Please double check.
someone0 said:
Just wonder why do use a zip file for the linux version? Wouldn't this kinda messup the permission when compress/uncompress? meaning, makeroot.sh may not have the proper permission when unzip. Please double check.
Click to expand...
Click to collapse
works just fine.
I chmod a+x'd the script before putting it into the zip.
heh, yeah, it works. Forgot I had my touchpad pluged in and it rebooted it....
whoops.
thanks for posting the location of the /recovery partition. I want to put a copy of htat on ice to prevent BN from undoing any of my work in a future update - I may want some of the fixes they have, but I want to be able to roll them back if needed.
Someone0 are you around can you pm me, Your root works, I installed nook color tools ver .02 in system/app folder and was able to see it in my sideloaded launcher, was able to uncheck/check install non market apps which sets the setting for US to be able to install .apk files from the nook itself, ONLY ISSUE is since I put that file in the system/app folder and the nook didnt like it I got stuck in a bootloop and get to start this process all over again! (nook resetted to ground zero)
maybe we temporary can leave it there get us the permission to install non market apps then remove the file and we will be ok or maybe stuck in another bootloop.
---------- Post added at 09:20 PM ---------- Previous post was at 08:52 PM ----------
GOT IT WORKING NOW:
1. Once rooted, get a file manager with root support and enable read/write permission to /system
2. temporary copy nook tools ver .02 .apk to the system/app folder
3. have a sideloaded launcher and check the app drawer youll see nook tools, run it, first screen uncheck and check the install non market apps box couple of times make sure its checked afterwards
4. have a test .apk to run the BN installer on and see you can now install .apks from the NOOK HD and HD+
5. remove the nook tools.apk file from the system/app folder and quit your file explorer which should reset everything for the system folder back to the way it orginally is!
6. reboot, if you reboot successfully with no boot loop 8 times, your GOLDEN FOR NOW! once again load up a file manager go select an .apk file and see you can now install it! Next step is trying to get amazon market working! then google somehow, but for google you need files in system/app folder permanently!
7. YOU CAN NOW SUCCESSFULLY DOWNLOAD .APK FILES through web, email, any other app and install through the NOOK HD or HD+ BN installer for .apk files. Watch what you install, if it gets put into /system or /system/app folder DREADED BOOT LOOP which resets everything! AMAZON MARKET WORKS!!!! and apps from there install fine to the BUILT IN MEMORY.
** Hopefully amazon market dont install stuff to the system/app folder and if it does hopefully you do not get the dreaded boot loops where you got to start this whole process over again so be forwarned!!! you will loose all data on NOOK HD and HD+ if u get stuck in the bootloops! BACKUP STUFF before messing with root and this kind of thing! DEVELOPMENT!
Aside from moving the actual apk to /system/app/ temporary (since you only do it once), putting a symbolic link there may work also without creating a reset loop. But can't you just side load the apk and run it in other folder?
someone0 said:
Aside from moving the actual apk to /system/app/ temporary (since you only do it once), putting a symbolic link there may work also without creating a reset loop. But can't you just side load the apk and run it in other folder?
Click to expand...
Click to collapse
when you sidelaod it OR install or have it installed to another folder or ran from another folder it cant modify the setting to allow non market apps to install!!
has to be in the /system/app folder THEN RAN from app drawer then you can set the setting uncheck and check box quit program and for now YOU HAVE to remove the .apk from the system/app folder and then you can reboot and the setting sticks! I GOT AMAZON MARKET INSTALLED right now installing apps! NOW WE GOT A KINDLE ladys and gentleman!
Amazon apk installs in internal memory. Apps downloaded from Amazon get installed in internal memory. You can then move them to SD card or leave them in internal memory. System apps are provided in the ROMs by the developers or vendors. ALWAYS back up before making system changes.. Now rooted - use Titanium Backup. System/app should be static throughout ROM lifecycle unless modified by user.
skyhawk21 said:
7. YOU CAN NOW SUCCESSFULLY DOWNLOAD .APK FILES through web, email, any other app and install through the NOOK HD or HD+ BN installer for .apk files. Watch what you install, if it gets put into /system or /system/app folder DREADED BOOT LOOP which resets everything! AMAZON MARKET WORKS!!!! and apps from there install fine to the BUILT IN MEMORY.
** Hopefully amazon market dont install stuff to the system/app folder and if it does hopefully you do not get the dreaded boot loops where you got to start this whole process over again so be forwarned!!! you will loose all data on NOOK HD and HD+ if u get stuck in the bootloops! BACKUP STUFF before messing with root and this kind of thing! DEVELOPMENT!
Click to expand...
Click to collapse
This is why I put the /system back to ro, at least that is what I think I did.
Amazon Store working on ROOTED Nook HD
Proof of Concept:
http://youtu.be/wCyd730L74Y
skyhawk21 said:
Proof of Concept:
http://youtu.be/wCyd730L74Y
Click to expand...
Click to collapse
LOL, your internet is slow. Could have cut the video time by 1/2 if not 2/3 if you switch to faster ISP.
skyhawk21 said:
Someone0 are you around can you pm me, Your root works, I installed nook color tools ver .02 in system/app folder
Click to expand...
Click to collapse
What exactly did you install? I cannot find "nook color tools" in Google Play or on APKTOP. Thanks for your hard work!
NEVERMIND! I found the thread that has the link for the app: http://forum.xda-developers.com/showthread.php?t=868366 Thanks again.
does this root method work on Nook HD+2.0.2?
if not how I can downgrade to 2.0.0?
Hello everyone, I recently purchased the Desire 816 for Virgin Mobile, and could not find anything on rooting this device.
So... I figured it out on my own! I decided to write out a tutorial since there isn't anything out there about rooting this phone!
I'm also including a nandroid backup of my stock rooted rom if you don't want to go through all of the steps. You will still need custom recovery.
1. Unlock your bootloader, install custom recovery, and flash superuser. I used v_superuser's guide for this, so thanks to him!
Use his guide to install custom recovery and root: http://forum.xda-developers.com/showthread.php?t=2775801
The custom recovery he links to isn't made for the VM variant of this phone, but it works!
Now you can restore my clean install, rooted nandroid backup (link at end of post) if you don't want to do the following steps and still have full root.
2. Hopefully you were able to successfully install custom recovery and root.
Now this part is a bit tricky. Even with root HTC is stopping us from writing to system. For this we need to apply the wp_mod.ko module.
Download it here: http://forum.xda-developers.com/showthread.php?t=2707378
Copy this file to the root of your internal storage.
Now download Terminal Emulator from play store, run it and enter the following commands (you only need to do this once):
su
insmod /sdcard/wp_mod.ko
Once you do this go into your favorite root explorer and mount as R/W. Copy the wp_mod.ko file to /system/lib/modules
Now go to /system/etc and find install-recovery.sh. Open it with a text editor and add a new line at the end with the following:
insmod /system/lib/modules/wp_mod.ko
Reboot! If all went well the wp_mod module will run at boot every time so you won't have to do it manually each time!
Congratulations, you now have a fully rooted Desire 816!
Download my nandroid backup here (place the contained folder into the CWM backup directory):
https://drive.google.com/uc?id=0B0bhyG2E55hXaWtpeGVQaEpOVzA&export=download
Hope this helped anyone wondering how to root the device!
I just get md5 mismatch error when I try to restore
Never mind found out my phone wasn't downloading the whole back up
jcrt2000 said:
I just get md5 mismatch error when I try to restore
Click to expand...
Click to collapse
I'm not trying to offend with my answer. Just going for the easiest solution first...
Did you unzip the backup nandroid onto your PC? I imagine he zipped the actual Nandroid folder as it would have a date and time as the name.
If you unzip VM_HTC_Desire_816_Rooted_NandroidBackup.zip you SHOULD see a folder with a date and time. That is the actual nandroid that you'd copy to your Clockwordmod backup folder.
sirrx7 said:
I'm not trying to offend with my answer. Just going for the easiest solution first...
Did you unzip the backup nandroid onto your PC? I imagine he zipped the actual Nandroid folder as it would have a date and time as the name.
If you unzip VM_HTC_Desire_816_Rooted_NandroidBackup.zip you SHOULD see a folder with a date and time. That is the actual nandroid that you'd copy to your Clockwordmod backup folder.
Click to expand...
Click to collapse
^ this. And restore that from clockworkmod. I know it should work because I already had someone confirm it working.
Kontrary said:
^ this. And restore that from clockworkmod. I know it should work because I already had someone confirm it working.
Click to expand...
Click to collapse
It does work. I had to download on my pc to get the whole file downloaded.
jcrt2000 said:
It does work. I had to download on my pc to get the whole file downloaded.
Click to expand...
Click to collapse
Oh nice! Glad you got it working.
Kontrary said:
^ this. And restore that from clockworkmod. I know it should work because I already had someone confirm it working.
Click to expand...
Click to collapse
Also...
The act of unlocking the phone clears out your data so you might notice that your flashlight and calculator apps are missing. For some reason HTC didn't make those 2 system apps.
If you'd like them back, here you go.
http://forum.xda-developers.com/showthread.php?t=2699906
sirrx7 said:
Also...
The act of unlocking the phone clears out your data so you might notice that your flashlight and calculator apps are missing. For some reason HTC didn't make those 2 system apps.
If you'd like them back, here you go.
http://forum.xda-developers.com/showthread.php?t=2699906
Click to expand...
Click to collapse
Thank you, I sold the phone but never noticed that.
Thanks for this, I had deleted my stock backup
problems with the mod.ko
everything works until I get to the wp_mod.ko command when using the terminal command. It just says cannot open. I tried countless times but it says the same thing. Is there any other way?
dwest3784 said:
everything works until I get to the wp_mod.ko command when using the terminal command. It just says cannot open. I tried countless times but it says the same thing. Is there any other way?
Click to expand...
Click to collapse
If you're having too much trouble and are about to give up you can always download Kontrary's Nandroid backup. I didn't use it but I did look through it and it looks like he already did the write protect mod in it.
Just unzip it on your PC and put the dated folder in your clockworkmod/backup folder. Boot into CWM recovery and restore from his nandroid.
Out of curiosity... Are you hitting enter after SU and before insmod???
Also...
The command insmod /sdcard/wp_mod.ko is only good if you have wp_mod.ko sitting on the root of the internal sd. If its on your micro sd card you'll obviously have to change the path after insmod or just move it to the internal sd..
thanks
sirrx7 said:
If you're having too much trouble and are about to give up you can always download Kontrary's Nandroid backup. I didn't use it but I did look through it and it looks like he already did the write protect mod in it.
Just unzip it on your PC and put the dated folder in your clockworkmod/backup folder. Boot into CWM recovery and restore from his nandroid.
Out of curiosity... Are you hitting enter after SU and before insmod???
Also...
The command insmod /sdcard/wp_mod.ko is only good if you have wp_mod.ko sitting on the root of the internal sd. If its on your micro sd card you'll obviously have to change the path after insmod or just move it to the internal sd..
Click to expand...
Click to collapse
Thanks I figured it out last night. I put in the internal memory and it worked but thanks for the reply!
dwest3784 said:
Thanks I figured it out last night. I put in the internal memory and it worked but thanks for the reply!
Click to expand...
Click to collapse
Right on. Glad you got it working.
driver issue
ive downloaded and installed and uninstalled and rebooted and done everything i can think to do...ive tried on my PC and on my laptop...ive tried with every usb cable i have...including the one that came with the phone...i can not get windows to recognize my phone...so i cant even unlock the bootloader to begin this process...any suggestions or hints on what i could try?
any help??
dragonclaw88 said:
ive downloaded and installed and uninstalled and rebooted and done everything i can think to do...ive tried on my PC and on my laptop...ive tried with every usb cable i have...including the one that came with the phone...i can not get windows to recognize my phone...so i cant even unlock the bootloader to begin this process...any suggestions or hints on what i could try?
Click to expand...
Click to collapse
i really really need to get this phone rooted any help??
dragonclaw88 said:
i really really need to get this phone rooted any help??
Click to expand...
Click to collapse
Have you plugged it in while in Fastboot? Which OS are you running? I'm on Win 7 x64 and have it set to download drivers from Windows update, I didn't have any problems going that route.
Have you downloaded HTC Sync Manager? It has the drivers required for your PC to recognize your phone.
Kontrary said:
Download my nandroid backup here (place the contained folder into the CWM backup directory):
https://drive.google.com/uc?id=0B0bhyG2E55hXaWtpeGVQaEpOVzA&export=download
Hope this helped anyone wondering how to root the device!
Click to expand...
Click to collapse
I installed your CWM Backup after I couldn't figure out your steps... but now there's an ANNOYING notification that says, "Smith disabled... Click here to open." I open it, and no matter what settings I choose, this notification keeps POPPING UP! Is this your doing, or a known issue with this "Mod." All I wanted to do was uninstall all the Google/VM Bloatware. Now going back to stock might be the only fix... ????
That Smith app is a problem for most recent HTC phones. It has nothing to do with the CWM backup. It happens with the M8 and our 816.
I just long press the notification, click App Info and force close. It's usually good until you reboot your phone.
Either HTC or Sprint is supposed to be looking for a fix but who knows.
https://community.sprint.com/baw/thread/169142?start=0&tstart=0
jayblaze406 said:
I installed your CWM Backup after I couldn't figure out your steps... but now there's an ANNOYING notification that says, "Smith disabled... Click here to open." I open it, and no matter what settings I choose, this notification keeps POPPING UP! Is this your doing, or a known issue with this "Mod." All I wanted to do was uninstall all the Google/VM Bloatware. Now going back to stock might be the only fix... ????
Click to expand...
Click to collapse
I was able to stop this annoyance by simply going to Titanium Backup (root needed) and freezing the process.
I typed in Smith in the search bar of TB and it came back with this process/app called
"Smith 4.21-plat_4.4.2-KOT49H"
I believe it happens to come up when a specific "bloatware" app is unaccessible by the device when removed but I have not singled out which app is it so far.
I backed up the app first then froze it and it stopped the Smith popup error permanently even after reboots and power offs.
(You could possibly delete it but until the stock bloatware app that causes this pinpointed i wouldn't recommend it.)
Tested running everything is good no errors rebooted fine checked bootloader and recovery and both are fine as well.
Sent from my 710C using XDA Free mobile app
I have here, two packages.
The twrp one is meant for those who have already flashed twrp, the other is for first time root via EDL.
Both flash System RW, updated TWRP and magisk.
TWRP package will not wipe Data, You will loose no data
NOTE - You may have to mount the system RW.
NOTE - The above will be fixed via a future custom rom.
Without further ado, here are the instructions.
Initial Root Instructions
Prep: You must have a Pin screen lock set on your device to prevent data loss.
On your phone go to
Settings>Security>Screen Lock>PIN
and set a pin.
USB Debugging and OEM Unlocking have to be enabled to make this work.
On Your phone go to
Setting>About phone
Then tap on build number 10 time to unlock Developer Settings
Now go to
Settings>Developer Options
Then toggle usb debugging and oem unlocking.
1. Download this package B20 Via QFIL
2. Unzip the file to your desktop.
3. Right click on RunasAdmin_TestSignON.bat and run as administrator.
4. Let your machine reboot.
5. Run Run This.bat
6. Install everything it tells you to install.
NOTE Select WWAN-DHCP when asked
7. RTFM and flash (All the files your need for qfil are in the B20 Folder!!!!)
8. Profit
Then
9.Press and hold Vol+ and Power
10.Once the ZTE screen shows, let go of power while continuing to hold vol+
This will get you into twrp
11.Plug you phone into your computer and from your adb directory, run these commands.
12.adb shell
13.setenforce 0
14.exit
Now on your phone, in twrp
15.Swipe to allow midification
16.Tap Backup
17.check data
18.tap select storage
19.Select microsdcard
20.tap ok
21.Swipe to backup
22.Tap home
23.Tap wipe
24.Tap Format Data
25.Enter yes and tap the blue checkmark
26.Tap home
27.Tap Power off
28.Turn your phone on.
For those who have TWRP already on their device, follow these instructions.
1. Download this package. B20 via TWRP
2. Extract it to your desktop
3. Run "Flash full B25.bat"
4. Profit
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Update 5/253/19
Updated boot.img z982_boot_magisk.img
Update Magisk root "Already obsolete"
Fixes ADB not authorized issues
Update twrp recovery.img z982_recovery_twrp.img
Fixes selinux enforcing related issues related to /data folder
Fixes backup related issues
Fixes zip install related issues
Do you think this will work with my hard bricked phone?
so if our system is still ro, all we have to do is mount rw every time? I was hoping that we would only need to mount it like one time, because im basically doing the same thing I was doing before.
https://drive.google.com/file/d/1YsOFbKcca2GTc6K77vD6-hh4qtk5O3mv/view?usp=sharing
test this. you might need to rename the zip file to bootanimtion.zip.
Chickenaa said:
https://drive.google.com/file/d/1YsOFbKcca2GTc6K77vD6-hh4qtk5O3mv/view?usp=sharing
test this. you might need to rename the zip file to bootanimtion.zip.
Click to expand...
Click to collapse
will do. are all the files already in place.
bootanimation worked, but sound still didnt
evtoofly said:
will do. are all the files already in place.
bootanimation worked, but sound still didnt
Click to expand...
Click to collapse
Upload the build.prop
Chickenaa said:
Do you think this will work with my hard bricked phone?
Click to expand...
Click to collapse
As long as you get the driver working, it should no problem.
xxMoon said:
As long as you get the driver working, it should no problem.
Click to expand...
Click to collapse
Im thinking about reinstalling windows. Do you think i should give it a try?
Chickenaa said:
Im thinking about reinstalling windows. Do you think i should give it a try?
Click to expand...
Click to collapse
I would.
Before you reinstall.. if ur able try on another PC.
xxMoon said:
1. Download this package. B20 via TWRP
2. Extract it to your desktop
3. Run "Flash full B25.bat"
4. Profit
Click to expand...
Click to collapse
Appreciate the update, same problem as before though RO /system and a mount -o rw,remount /system command results in the phone freezing and then restarting.
JasonSec said:
Appreciate the update, same problem as before though RO /system and a mount -o rw,remount /system command results in the phone freezing and then restarting.
Click to expand...
Click to collapse
thought I was the only one, I just stopped trying, if I need to go mount rw, i just use root explorer . Even that freezes sometimes though smh. Some people just got it better than we do
B25
Hello sir,
My phone is running B25. Will this cause issues? Do I need to downgrade?
AjtheLAF said:
Hello sir,
My phone is running B25. Will this cause issues? Do I need to downgrade?
Click to expand...
Click to collapse
No issues for me.
Emerl said:
No issues for me.
Click to expand...
Click to collapse
Did your system become rw?
evtoofly said:
Did your system become rw?
Click to expand...
Click to collapse
I use ES File Explorer. Open the app, wait for su to grant it access, then change the system to RW. I've noticed that the phone will freeze if I tried to switch to RW before the File Explorer was granted su access.
Emerl said:
I use ES File Explorer. Open the app, wait for su to grant it access, then change the system to RW. I've noticed that the phone will freeze if I tried to switch to RW before the File Explorer was granted su access.
Click to expand...
Click to collapse
I noticed that too. I also tried to see if root explorer would mount rw after I used es to mount rw, and it turns out that u still have to mount system separately in both file managers. Bummer because I was looking for a way to always have my system mounted as rw between both file managers.
evtoofly said:
I noticed that too. I also tried to see if root explorer would mount rw after I used es to mount rw, and it turns out that u still have to mount system separately in both file managers. Bummer because I was looking for a way to always have my system mounted as rw between both file managers.
Click to expand...
Click to collapse
I'm guessing once a custom rom is available, the whole system RW situation will be situated. Is there an advantage of root explorer over es explorer?
Emerl said:
I'm guessing once a custom rom is available, the whole system RW situation will be situated. Is there an advantage of root explorer over es explorer?
Click to expand...
Click to collapse
I personally use root explor to chmod files, I dont think es can do it, however es has its own perks as well, so I just keep both just in case
Emerl said:
I'm guessing once a custom rom is available, the whole system RW situation will be situated. Is there an advantage of root explorer over es explorer?
Click to expand...
Click to collapse
Lol, actually you can put init.d scripts in /sbin/.magisk/img/.core/service.d/ and they will do it on boot.
Try my attachment.
I
I've looked all over and I'm unable to find a solution or even what's stopping me from modifying the /system folder in the root directory. I can remove files from that folder and all of it's subfolders but I'm unable to add any files into that directory. I am rooted on the T-mobile OnePlus 6t that has been converted to the international ROM. I know my root works cause I can perform other root functions. I also cannot modify the /system folder from TWRP either which is really strange to me. Also, when TWRP prompts me to install the app, it just reboots recovery since it's trying to install it as a system app which I can't do for this odd reason I have yet to find out. This issue all of a sudden showed up after an OTA update and re-rooting after. I have tried reinstalling TWRP, Magisk and Oxygen OS itself but the issue persists. I have also tried running "reboot disemmcwp" as root in a terminal window AND using adb but I guess that command no longer works. Any suggestions welcome as this is the last place I can find an answer to this issue.
Edit: found out I'm unable to uninstall system apps for some reason. So the issue isn't space related.
Toilet Clauger said:
I've looked all over and I'm unable to find a solution or even what's stopping me from modifying the /system folder in the root directory. I can remove files from that folder and all of it's subfolders but I'm unable to add any files into that directory. I am rooted on the T-mobile OnePlus 6t that has been converted to the international ROM. I know my root works cause I can perform other root functions. I also cannot modify the /system folder from TWRP either which is really strange to me. Also, when TWRP prompts me to install the app, it just reboots recovery since it's trying to install it as a system app which I can't do for this odd reason I have yet to find out. This issue all of a sudden showed up after an OTA update and re-rooting after. I have tried reinstalling TWRP, Magisk and Oxygen OS itself but the issue persists. I have also tried running "reboot disemmcwp" as root in a terminal window AND using adb but I guess that command no longer works. Any suggestions welcome as this is the last place I can find an answer to this issue.
Click to expand...
Click to collapse
Known issue that in the Newer OxygenOS versions there is no free space in /system. I'd download Solid Explorer and check the Free Space in the Root Directory.
Sent from my OnePlus6T using XDA Labs
Mannan Qamar said:
Known issue that in the Newer OxygenOS versions there is no free space in /system. I'd download Solid Explorer and check the Free Space in the Root Directory.
Click to expand...
Click to collapse
I've thought about that before. I use root explorer and can see there's more space than needed for the files I want to insert. Is there some buffer space needed in there and how much?
Toilet Clauger said:
I've thought about that before. I use root explorer and can see there's more space than needed for the files I want to insert. Is there some buffer space needed in there and how much?
Click to expand...
Click to collapse
Well, if you go to magisk and select core only mode then reboot you will be able to modify system
toolhas4degrees said:
Well, if you go to magisk and select core only mode then reboot you will be able to modify system
Click to expand...
Click to collapse
I was actually able to find the issue. Space was the issue. I guess there's a space buffer needed from what a file explorer says is left and what's actually left. I uninstalled a couple system apps I disable anyway and was able to insert files/apps into system again.
I made space easy I have the new OnePlus camera apk 125mb the old one is 67mb