***Note: this is a "for noobs by noobs" post: meant to guide people step-by step. The only needed info I don't cover is BASIC dos commands like "cd" (the only one you really need for this). I didn't post this in development b/c I've added basically nothing except more thorough instructions for noobs like me. Hope this helps!!!***
If Temp Root was worth messing with at all, IMO it was worth messing with in order to do a titanium backup. That's what I was able to successfully with the method below.
I haven't seen this thread's equal here in the 3D forums, so I figured I would repost. All credit where credit is due! Teamwin and then Joel.bourquard for this write-up/slight modification to teamwin's solution.
SO: basically follow the write-up below exactly. I downloaded Titanium Backup and Superuser directly from the market before beginning. Also, after you've finished his steps you can simply click to open Titanium Backup (no need to fool with Superuser) and it'll recognize root, find all your programs(including system data/programs), etc etc. Works like a charm!
NOTE for NOOBS: Download the attached zip --I've included the needed ADB files as well. Attach your EVO 3D using a USB cord and make sure USB debugging is turned ON (check in Settings-->Applications-->Development) and also make sure you aren't letting your PC access your SD card (go to Settings-->Connect to PC and change default to "Charge Only")
Once you've downloaded and unzipped them, open a command prompt (start menu, type "cmd" and type enter). Once in the command prompt, navigate to wherever you downloaded/extracted the zip. FROM THERE, type in each command in the writeup below EXACTLY AS WRITTEN (with quotation marks and everything). Once you've done the last ste (adb shell "/data/bin/root.sh") you can grab your device and open Titanium Backup and VOILA!
----
THE WRITE-UP
Type these commands AS WRITTEN into your cmd prompt after you've (1) downloaded superuser and Titanium Backup from the market (2) downloaded and extracted the zip and (3) navigated your command prompt to the location where you extracted those files.
adb push fre3vo /data/local/tmp/
adb shell "cd /data/local/tmp ; chmod 755 fre3vo ; ./fre3vo"
adb shell "mkdir /data/bin ; mv /data/local/tmp/fre3vo /data/bin/"
adb push su /data/bin/
adb push root.sh /data/bin/
adb shell "chmod 4555 /data/bin/su ; chmod 755 /data/bin/root.sh"
adb shell "/data/bin/root.sh"
BINGO! Now open Titanium Backup and you're good to go!
For more info, PLEASE see the sources!
http://forum.xda-developers.com/showthread.php?t=1151735
http://therootofallevo.com/forums/viewtopic.php?f=8&t=76
sweet havent gotten it to work for me but ill keep on trying haha guess im a hardcore noob
No worries, me too! As long as you can change directories is dos you should be fine
Sent from my PG86100 using XDA App
panamaniac said:
***Note: this is a "for noobs by noobs" post: meant to guide people step-by step. The only needed info I don't cover is BASIC dos commands like "cd" (the only one you really need for this). I didn't post this in development b/c I've added basically nothing except more thorough instructions for noobs like me. Hope this helps!!!***
If Temp Root was worth messing with at all, IMO it was worth messing with in order to do a titanium backup. That's what I was able to successfully with the method below.
I haven't seen this thread's equal here in the 3D forums, so I figured I would repost. All credit where credit is due! Teamwin and then Joel.bourquard for this write-up/slight modification to teamwin's solution.
SO: basically follow the write-up below exactly. I downloaded Titanium Backup and Superuser directly from the market before beginning. Also, after you've finished his steps you can simply click to open Titanium Backup (no need to fool with Superuser) and it'll recognize root, find all your programs(including system data/programs), etc etc. Works like a charm!
NOTE for NOOBS: Download the attached zip --I've included the needed ADB files as well. Attach your EVO 3D using a USB cord and make sure USB debugging is turned ON (check in Settings-->Applications-->Development) and also make sure you aren't letting your PC access your SD card (go to Settings-->Connect to PC and change default to "Charge Only")
Once you've downloaded and unzipped them, open a command prompt (start menu, type "cmd" and type enter). Once in the command prompt, navigate to wherever you downloaded/extracted the zip. FROM THERE, type in each command in the writeup below EXACTLY AS WRITTEN (with quotation marks and everything). Once you've done the last ste (adb shell "/data/bin/root.sh") you can grab your device and open Titanium Backup and VOILA!
----
THE WRITE-UP
Type these commands AS WRITTEN into your cmd prompt after you've (1) downloaded superuser and Titanium Backup from the market (2) downloaded and extracted the zip and (3) navigated your command prompt to the location where you extracted those files.
adb push fre3vo /data/local/tmp/
adb shell "cd /data/local/tmp ; chmod 755 fre3vo ; ./fre3vo"
adb shell "mkdir /data/bin ; mv /data/local/tmp/fre3vo /data/bin/"
Click to expand...
Click to collapse
Looks great, yet i have a question..... In your instructions.....you make a command which I believe means to create a new folder.... You use "mkdir"........ I have a lot of
Or school DOS commands in my head and it reminds me of the MD make directory command... Is mkdir correct ?
mkdir is the long version of md, IIRC....
at first i wasn't gonna bother with temp root, but one of the things i did need was titanium backup to restore a bunch of data.
this worked absolutely perfect!
thanks for the great write up
Related
Here comes the latest rooting method that works with 2.0.2.A.0.24 firmware.
Credits to Scotty2 for his psneuter exploit!
1. Download and unpack rootme.tar.bz2
2. Execute ./rootme (linux) or rootme.bat (windows)
3. Done.
---
You may also want to try SuperOneClickv1.5.5-ShortFuse.zip (modified by batman_112 to use the latest exploit).
Cheers,
z
Stop for me at Point 4)
I got back
./ratc: Permission denied
Click to expand...
Click to collapse
after
./ratc
i get ... permission denided
Wow, actually it seems that copying files with adb push via script messes thing up I corrected the instructions, so now it will work for you, but need to copy the files manually.
zdzihu said:
Wow, actually it seems that copying files with adb push via script messes thing up I corrected the instructions, so now it will work for you, but need to copy the files manually.
Click to expand...
Click to collapse
Your link is broken
Try now, I got rid of installation scripts
EDIT: Now it works flawlessly. I still have no clue why copying files with .bat file messes everything up, but manual copying does the job.
why the superone reach the root sometimes so slow?
your method uses the same exploit, and works at first try
check the files plz: Invalid or Deleted File
can't download the ratc-pack --> Invalid or Deleted File
please reup - THX
EDIT: Link is OK now --> THX
Link is OK. Downloading at the moment.
Tried it manually (as described)...
But same problem... :-(
UserX10 said:
Tried it manually (as described)...
But same problem... :-(
Click to expand...
Click to collapse
I just reflashed my phone and it worked for me at 1st attempt.
Could you please got rid of the old files and retry from the beggining?
Cheers!
meta96 said:
after
./ratc
i get ... permission denided
Click to expand...
Click to collapse
Same thing for me
:-( Same Problem
I flashed my X10 with nordic FW and tried it again Step by Step... but "permission denied"... even if i remove and make the tmp directory as described...
Ok, last thing to try... After you copy the files, go with:
Code:
adb shell
chmod 777 /data/local/tmp/*
I added some screenshots to show how the process works for me.
is this a full root? i mean, is root+shell root?
zdzihu said:
Hi guys, I've noticed some people still can't get their phones rooted with SuperOneClick method. So do I, never managed to get it working Here is a simple method of rooting, using the same exploit (rageagainstthecage - credits to author). This is quick and 100% guaranteed to work but I'd rather recommend it to advanced users.
1. Install Android Terminal Emulator from the market http://bit.ly/9B46Nl
2. Download and unpack http://www.mediafire.com/?s0428zxc7n50i28
3. Plug in the phone (usb debugging mode), copy the following files with adb and change permissions:
Code:
adb push ratc /data/local/tmp/ratc
adb push busybox /data/local/tmp/busybox
adb push su /data/local/tmp/su
adb push rootme /data/local/tmp/rootme
adb push superuser.apk /data/local/tmp/superuser.apk
adb shell
chmod /data/local/tmp/*
4. Start Terminal Emulator on your phone and issue those commands:
Code:
cd /data/local/tmp
./ratc
5. Exit out of Terminal Emulator using BACK button.
6. Start any other application and exit out of it using BACK button.
7. Start Terminal Emulator again - note that you're running it as root (#)
8. Issue those commands:
Code:
cd /data/local/tmp
./rootme
Your phone will reboot - and it's done. I suggest installing Busybox from the Market. Hope it helps.
Cheers!
EDIT: Fixed.
Click to expand...
Click to collapse
Finally I was able to root my phone
just one correction, you got to use chmod 777 /data/local/tmp/*
it was not allowing to root otherwise
i kept breaking my head using the "simple" SuperOneCLick but could not show my rage against the machine
thank you for explaining this process for Root.
zdzihu said:
Ok, last thing to try... After you copy the files, go with:
Code:
adb shell
cd /data/local/tmp
chmod 777 *
I added some screenshots to show how the process works for me.
Click to expand...
Click to collapse
chmod 777 *
did it. thanx. btw like your oldstyle-skills
Just saw this thread and wanted to root my phone also...I downloaded the files provided in the first post and extracted onto my PC. When I tried running the adb application, I only get a command window only for a split second and then it disappears. Am I doing something wrong?
Everything works fine until the final step where I write ./rootme in the emulator.
Before the phone reboots, it says something right after, something about superuser.apk.
Once the phone is back on the emulator goes back to $. As well as not being able to download Busybox.
Appreciate your efforts
EDIT: No worries, I managed to get root using SuperOneClick (finally!). It was rather sketchy, would've preferred your way tbh.
(Copy/Paste the following commands into command window)
adb push busybox /data/local/
adb push psneuter /data/local/
adb push misc.img /data/local/
adb shell chmod 777 /data/local/busybox
adb shell chmod 777 /data/local/psneuter
adb shell /data/local/psneuter
(After you run psneuter ADB is killed but restart itself. This is not a problem.
Copy/Paste into command window)
adb shell /data/local/busybox md5sum /data/local/misc.img
The command window MUST display the following checksum value:
c88dd947eb3b36eec90503a3525ae0de
If it does not match, DO NOT PROCEED! You must redownload the file to your sd card and rename to continue.
(Copy/Paste into command window)
adb shell dd if=/data/local/misc.img of=/dev/block/mmcblk0p17
adb reboot bootloader
Once you do this your phone will reboot into the Bootloader. When your phone loads the Bootloader you can unplug the USB cable from your computer. Leave the command prompt window open, we will need it later.
Bootloader should be highlighted in blue. Press the power button to start. (Don’t hold, just press)
The screen will change and Fastboot will be selected. About 10 seconds later it will continue to the next step.
You should see some files loaded and checked. Don’t worry about the warnings, this is normal. Your screen will eventually clear and you will see “checking pg05img.zip.
did all of the above. Confirmed the check sum was correct. when going into fastboot and checking pg05img.zip it stated no image file. I dont want to re boot my phone in case i mess something up. can someone please help? How do i get the image on there correctly from this point?
this is the same step i am stuck at and i narrowed out that its not a spelling error in the file name. It seems that the pg05img.zip removes itself from my SD card everytime i get into the bootloader thats y i cant get to the next step which is to update. Very frustrating. I am going to try another SD card tomorrow.
Depending on how you have your OS configured, it may not show known file extensions. So if you renamed the file to PG05IMG.zip, it may actually be saved as PG05IMG.zip.zip This will not affect the MD5 sum as they are independent of filename, however the bootloader will not recognize this as a PG05IMG file.
Also, I'm not certain about the TB, but most phones do not charge will in the bootloader, so if you let it stay on too long, do not proceed without a bump charge first.
Are you using the most recent rooting method by jcase? And the 5 files required to root? It doesn't sound like the exploits did what they should. What RUU version are you starting with?
I'm looking at what you've said your doing as far as your method and its not the latest jcase method. That said, just copying and pasting big blocks of commands doesn't work. And if you're not using the latest jcase method, I don't know what downloads you've been using and I don't think older ones would work. There's a number of outdated methods on various dev's own websites that won't work. Looks like that's what you've got here. This is the thread you should be following. http://forum.xda-developers.com/showthread.php?t=996616 jcase and the other dev's who've worked on this can also be found on IRC at chat.andIRC.net channel #thunderbolt for live help.
Here's a more detailed explanation than you're likely to find elsewhere, which I wrote:
***Note: this is a "for noobs by noobs" post: meant to guide people step-by step. The only needed info I don't cover is BASIC dos commands like "cd" (the only one you really need for this). I didn't post this in development b/c I've added basically nothing except more thorough instructions for noobs like me. Hope this helps!!!***
If Temp Root was worth messing with at all, IMO it was worth messing with in order to do a titanium backup. That's what I was able to successfully with the method below.
I haven't seen this thread's equal here in the 3D forums, so I figured I would repost. All credit where credit is due! Teamwin and then Joel.bourquard for this write-up/slight modification to teamwin's solution.
SO: basically follow the write-up below exactly. I downloaded Titanium Backup and Superuser directly from the market before beginning. Also, after you've finished his steps you can simply click to open Titanium Backup (no need to fool with Superuser) and it'll recognize root, find all your programs(including system data/programs), etc etc. Works like a charm!
NOTE for NOOBS: Download the attached zip --I've included the needed ADB files as well. Attach your EVO 3D using a USB cord and make sure USB debugging is turned ON (check in Settings-->Applications-->Development) and also make sure you aren't letting your PC access your SD card (go to Settings-->Connect to PC and change default to "Charge Only")
Once you've downloaded and unzipped them, open a command prompt (start menu, type "cmd" and type enter). Once in the command prompt, navigate to wherever you downloaded/extracted the zip. FROM THERE, type in each command in the writeup below EXACTLY AS WRITTEN (with quotation marks and everything). Once you've done the last ste (adb shell "/data/bin/root.sh") you can grab your device and open Titanium Backup and VOILA!
----
THE WRITE-UP
Type these commands AS WRITTEN into your cmd prompt after you've (1) downloaded superuser and Titanium Backup from the market (2) downloaded and extracted the zip and (3) navigated your command prompt to the location where you extracted those files.
adb push fre3vo /data/local/tmp/
adb shell "cd /data/local/tmp ; chmod 755 fre3vo ; ./fre3vo"
adb shell "mkdir /data/bin ; mv /data/local/tmp/fre3vo /data/bin/"
adb push su /data/bin/
adb push root.sh /data/bin/
adb shell "chmod 4555 /data/bin/su ; chmod 755 /data/bin/root.sh"
adb shell "/data/bin/root.sh"
BINGO! Now open Titanium Backup and you're good to go!
For more info, PLEASE see the sources!
http://forum.xda-developers.com/show....php?t=1151735
http://therootofallevo.com/forums/vi...c.php?f=8&t=76
That's a good write up, but if you want easy, download the script by Jeremy found here: http://forum.xda-developers.com/showthread.php?t=1152101 and run it. Install titanium backup and your all set. No need for all the adb commands and he includes SU and busybox for you.
cruise350 said:
That's a good write up, but if you want easy, download the script by Jeremy found here: http://forum.xda-developers.com/showthread.php?t=1152101 and run it. Install titanium backup and your all set. No need for all the adb commands and he includes SU and busybox for you.
Click to expand...
Click to collapse
This is the same thing. It was made not to long after J.eremy released his method. It suppose to stick and not lose root until reboot. That's why its called better temp root.
My ''xDU4L C0R3 SH00T3Rx'' shot you down in 3D!
r0cky0790 said:
This is the same thing. It was made not to long after J.eremy released his method. It suppose to stick and not lose root until reboot. That's why its called better temp root.
My ''xDU4L C0R3 SH00T3Rx'' shot you down in 3D!
Click to expand...
Click to collapse
Tried both methods, J.eremy's and this one. While i'm able to get the almighty root access. Wifi Tether and Titanium do not recognize it. Although they do request it. guess I'll keep playing with my shell
Hello,
I am having a major problem... earlier today i made a backup of my ics'd out v8 rom in order to try the new CM7 Kang. I got the kang running but needed to install gapps. For some reason rom manager was not letting me install it from there because it wasn't an updated version of rom manager and i couldn't get an updated version. So i figured I would go back to my ics'd rom, download gapps on the sdcard, and then go back to cm7 to install... NOPE.
Every time I try to restore my backup I get md5 mismatch error. I went through a bunch of different threads for different phones and tried all the adb stuff it said and nothing worked. For some reason when I ran the command (given here http://forum.xda-developers.com/showthread.php?t=714114) "cd /sdcard..." the pound # changed to a > and everything I typed would just be repeated back at me. The phone never even asked for superuser permission. I am pretty sure that I have the adb stuff right since when I type in "adb devices" in command I see the device, but I just have no clue how to fix this. Maybe the instructions given on this page only applies to that particular phone?
I would really like to be able to recover this backup and if anyone has instructions on how to fix this error on this phone it would be very much appreciated.
Thanks!
ADB was working if you got a # prompt
Custom kernels are almost all "insecure" kernels - ADB sessions automatically have root permissions.
This was the case for you - a # prompt means you have root privileges.
A $ prompt means you don't
A > prompt means that something you typed on the previous line made the shell decide you wanted to type more before executing the command. Control-C will break out of this. So if you got a > prompt after the "cd /sdcard/clockworkmod/backup/blahblah" command - you mistyped something on that line. Possibly you put a ; in there by accident, or you have opening quotes without closing quotes
There is a comment later in that thread "the folder name for your backup couldn't have spaces in it" - Weird characters in the directory name would be a possible cause of your cd command failing.
CWM should never have created a folder name that behaves like this, unless you did a nandroid backup using ROM Manager. If you did - another reason NOT to use ROM Manager.
Did you change the file name of the backup? make sure there is no spaces in file name. hope this help.
I would just download gapps to computer then move the file to phone. Then reboot into cwm and flash galls.
Sent from my SAMSUNG-SGH-I777 using XDA App
Artimus009 said:
I would just download gapps to computer then move the file to phone. Then reboot into cwm and flash galls.
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
Code:
adb push
is your friend - great way to put a file on the phone when it's in recovery
Entropy512 said:
ADB was working if you got a # prompt
Custom kernels are almost all "insecure" kernels - ADB sessions automatically have root permissions.
This was the case for you - a # prompt means you have root privileges.
A $ prompt means you don't
A > prompt means that something you typed on the previous line made the shell decide you wanted to type more before executing the command. Control-C will break out of this. So if you got a > prompt after the "cd /sdcard/clockworkmod/backup/blahblah" command - you mistyped something on that line. Possibly you put a ; in there by accident, or you have opening quotes without closing quotes
There is a comment later in that thread "the folder name for your backup couldn't have spaces in it" - Weird characters in the directory name would be a possible cause of your cd command failing.
CWM should never have created a folder name that behaves like this, unless you did a nandroid backup using ROM Manager. If you did - another reason NOT to use ROM Manager.
Click to expand...
Click to collapse
Thanks for the reply! Yeah that would make sense but I copied the file path directly from windows explorer and I checked for spaces too... Yeah I only do backups straight from CWM.
getbuzzin said:
Did you change the file name of the backup? make sure there is no spaces in file name. hope this help.
Click to expand...
Click to collapse
I did change the name from the original name, I added like "ics'doutv8siyah2.6.1blahblahblah" to the beginning so that I could distinguish which backup was which. Could this make a difference? I mean I have done this before without issue.
Shadow12347 said:
Thanks for the reply! Yeah that would make sense but I copied the file path directly from windows explorer and I checked for spaces too... Yeah I only do backups straight from CWM.
I did change the name from the original name, I added like "ics'doutv8siyah2.6.1blahblahblah" to the beginning so that I could distinguish which backup was which. Could this make a difference?
Click to expand...
Click to collapse
Change it back and see if it works
Only letters, numbers and periods. the ' is probably to blame.
Sent from my SAMSUNG-SGH-I777
Well I deleted the beginning and it looked like it was going to work because it was checking md5 sums for a while and then it said md5 mismatch. But it wasn't instant like the other times.
I think I read on one of the pages that you could take the nandroid.md5 from another backup and replace it with the one in the nonworking backup, is this true and would it work?
Ok nevermind, I forgot to do the ADB thing again xD it worked... THANK YOU SO MUCH!
karth500 said:
Only letters, numbers and periods. the ' is probably to blame.
Sent from my SAMSUNG-SGH-I777
Click to expand...
Click to collapse
Most likely.
I usually rename my backups manually to something like romname_date in ADB
e.g.
villainrom_1224
I NEVER put spaces or other characters in the rom name
Right now I think I have:
modstock_1128
villainrom_1224
uckk6_1224
one other ROM...
Ok guys I'm sorry, it happened again... except this time I think it may be a problem with ADB. When I am in adb shell, it shows up as "~ #" instead of just "#", however, typing "su" changed it to just "#". However, in both instances ("~ #" and "#") it gets an error:
~ # cd /sdcard/clockworkmod/backup/2012-01-22.18.04.05
cd /sdcard/clockworkmod/backup/2012-01-22.18.04.05
/sbin/sh: cd: can't cd to /sdcard/clockworkmod/backup/2012-01-22.18.04.05
and
# cd /sdcard/clockworkmod/backup/2012-01-22.18.04.05
cd /sdcard/clockworkmod/backup/2012-01-22.18.04.05
cd: can't cd to /sdcard/clockworkmod/backup/2012-01-22.18.04.05
This is the original name, there are no spaces, I checked the driver for the phone, etc.
Anyone got any ideas?
Oops double post -_-
Try tab-completion (type part of a directory name and hit tab - sometimes it works and sometimes it doesn't, usually should work when ADBing into CWM), and use "cd" and "ls" to navigate through directories instead of just pasting the whole path.
ls = same thing as dir in DOS
Alright so I did that and found out the sdcard isn't mounting...
C:\android-sdk-windows\platform-tools>adb shell
~ # su
su
# ls
ls
acct fota.rc recovery.rc
app-cache init res
cache init.goldfish.rc sbin
config init.rc sdcard
customkernel init.smdkc210.rc sys
d init.smdkv310.rc system
data init_kernel_only.rc tmp
dbdata lib ueventd.rc
default.prop lpm.rc ueventd.smdkc210.rc
dev misc ueventd.smdkv310.rc
efs mnt vendor
etc proc
# cd /mnt
cd /mnt
# ls
ls
asec obb sdcard secure usb
# cd /sdcard
cd /sdcard
# ls
ls
#
I also went into root explorer and it said "SD card is not currently mounted"
...uhhh I feel like a noob to ask this but, how do you mount it? xD
The thing is, though, that it dismounts when I plug it into the computer to transfer files/adb, but it is mounted afterwards...
my NT is not working, if you can please click here to help me
anyway, before that - when it was working, i tried to root it by using this method:
http://forum.xda-developers.com/showthread.php?t=1354487
at debloat menu, i chose "extreme" because i want to delete all of B&N content. i just want a normal android tablet, i know i can still read books by using the NOOK app for android.
so i chose extreme mode. and the command prompt window closed right after that.
so my NT was rooted, but not successfully, it was even worse than it was before i rooted.
i open the batch file (NookandZergy.bat) to see what the command lines are to find the reason why it didn't work. and i saw this:
adb shell rm -r /system/app/Accessories.apk
Click to expand...
Click to collapse
i opened command prompt, and typed this. and i got something like "failed because the file is not exist." -> i knew the batch script was wrong in some ways. i was going to unroot and root again with the option "full debloat" (not extreme), but before i do that, i was trying to remove netflix, i wanted to type this to the command line to see what will happen.
adb shell rm -r /system/app/netflix.apk
Click to expand...
Click to collapse
but i accidentally type adb shell rm -r /system/app/, and then it removed everything in /system/app/
i got the error in the nook tablet's screen, i don't remember what the error is, but when i pressed "force close", it kept showing me that error, i tried about 20 times but still not work.
i turned off my NT, and when i boot it, it stuck at "read forever",
that's why i created this thread.
my question is: how do i do "extreme debloat"? i want to remove everything from B&N. can you please give me the correct "command lines" to do this? and how to use that "command lines"?
prepare a sdcard to boot into ClockworkMod (CWM) which is a custom recovery (replaces stock recovery). And from there flash this ROM, for extreme-debloat is easy you can modify the script just to debloat or i can make it for you. First focus in restore your system.
As i said in my last post in your other thread read my FAQ and you will find your what you need there, if you have any question me or any other user will try to help.
PS: here is post i made for a user about how to re-bloat but the thing is that i post the list of all the B&N apps for reference to you so it might be helpfull.
~ Veronica
i have a little knowledge about batch file, so i think i can edit the script
(just edit the wrong file name -> make it become correct file name)
but i don't know what files are inside the folder /system/app/
for example: the file Accessories.apk is not exist, so how should i edit the script
nooktablet said:
i have a little knowledge about batch file, so i think i can edit the script
(just edit the wrong file name -> make it become correct file name)
but i don't know what files are inside the folder /system/app/
for example: the file Accessories.apk is not exist, so how should i edit the script
Click to expand...
Click to collapse
Well you got the error probably 'cause when you ran the script it removed that file so when you typed the same command again it won't remove it because is already gone.
In the link i provided is the list of all the B&N applications that are removed in the extreme debloat option. So you basically have keep that part of the code plus the intro to get in adb shell.
In that post you will also find a link to the complete system/app folder just in case you by "playing around" with adb remove any important system app, so you can push it back.
~ Veronica
lavero.burgos said:
Well you got the error probably 'cause when you ran the script it removed that file so when you typed the same command again it won't remove it because is already gone.
In the link i provided is the list of all the B&N applications that are removed in the extreme debloat option. So you basically have keep that part of the code plus the intro to get in adb shell.
In that post you will also find a link to the complete system/app folder just in case you by "playing around" with adb remove any important system app, so you can push it back.
Click to expand...
Click to collapse
no, when i chose extreme debloat, it closed the command prompt window, before it closed, i saw something "failed...". when i typed the command again it showed "failed...", i'm sure it's exactly what it said before,
and i know after debloat, it should go back and do other command like "thank you for using" (i read the batch file). i also saw B&N apps were still on my NT, debloat didn't work because of the missing file -> the script stopped.
btw, you said i can use adb to push the apps back. so that means i can also use adb to remove apps? can i not debloat when rooting, and after root, i use adb to remove apps later? will adb work at that time?
and can i use adb to explore what files are in the /system/app/ folder? or any other program?
nooktablet said:
no, when i chose extreme debloat, it closed the command prompt window, before it closed, i saw something "failed...". when i typed the command again it showed "failed...", i'm sure it's exactly what it said before,
and i know after debloat, it should go back and do other command like "thank you for using" (i read the batch file). i also saw B&N apps were still on my NT, debloat didn't work because of the missing file -> the script stopped.
btw, you said i can use adb to push the apps back. so that means i can also use adb to remove apps? can i not debloat when rooting, and after root, i use adb to remove apps later? will adb work at that time?
and can i use adb to explore what files are in the /system/app/ folder? or any other program?
Click to expand...
Click to collapse
Yes adb works at anytime even in dockworkers (CWM) .
To know how to use adb go to my FAQ (link below in my signature) and look in the how-to's made by me section for the how to use and install adb.
"adb shell rm -r" is one of the adb commands and is used for remove files.
adb shell = is to get superuser permissions (root/su)to run advanced commands.
rm = remove
-r = recursive
~ Veronica
Sent from my Nook Tablet using xda premium