Database Develop

cat /sdcard/su > su

I am using the PRS complete rooting guide. And when it tells me to type cat /sdcard/su > su, i am getting this error message - cat: can't open '/sdcard/su': No such file or directory.
Can anyone help with this?

Do you have su on your sdcard?

use unrevoked. one click root

just use the one click method by unrevoleved its easier

Su is not on the SD card. The sd card is a brand new PNY card. I have Su in the sdk/tools folder.

Then obviously, that command will not work. Use the unrevoked method if you are unsure what these commands do/how they work. Less headache on your end.

where is it located?

maybe i'm missing something obvious, but why pipe the text rather than just copy the file?
Sorry if this is the wrong place, but that command is curious.

This is what it's asking me to do.
From PRS Complete Rooting Guide
Now type the following commands to make it persistent through reboot
Code:
adb shell
su
export PATH=$PATH:/system/bin
cd /system/app
cat /sdcard/Superuser.apk > Superuser.apk
cd /system/bin
cat /sdcard/su > su
ln -s /system/bin/su /system/xbin/su /* IF YOU GET AN ERROR HERE DO rm /system/xbin/su THEN REDO */
chmod 06755 su

k_flan said:
maybe i'm missing something obvious, but why pipe the text rather than just copy the file?
Sorry if this is the wrong place, but that command is curious.
Click to expand...
Click to collapse
I don't know what that guide does, but it doesn't seem right --- it'll mess up the privs, that's why the old root was written as an update-payload.
It's redirected I/O since you can't copy across filesystem boundaries -- ie /sdcard to a different mountpoint.

So if I reboot my phone now, do you think I'll lose root and have to start over?

csills said:
So if I reboot my phone now, do you think I'll lose root and have to start over?
Click to expand...
Click to collapse
Either way, it shouldn't matter much. If it didn't work or you lost root for any reason, just go to http://unrevoked.com/ and click on the image for the Incredible. Today unrevoked released version 3 of their tool. This will root your phone and flash the custom recovery all without your needing to do anything in a shell.

askwhy said:
Either way, it shouldn't matter much. If it didn't work or you lost root for any reason, just go to and click on the image for the Incredible. Today unrevoked released version 3 of their tool. This will root your phone and flash the custom recovery all without your needing to do anything in a shell.
Click to expand...
Click to collapse
AND - if you appreciate unREVoked's work - please donate. They do amazing work and they do it all for free! We're the lucky ones to have such [email protected] developers out there who do this kind of stuff so that we don't have to figure out the exact second to push in our SD cards, push files to the SD card, and then push them to the phone at exactly the right time...... just download, run, and you're done.

Just use the unrevoked 3 you will save plenty of pain and struggle

unrevoked3 worked! Thanks for the help guys.

No problem were glad to be of assistance

adb commands nexus one-read only error

I have been trying for some time now,pushing files via adb commands onto nexus one but keep getting cannot copy file read only file error.I am fully rooted and unlocked.I have also reinstalled the android sdk but always get the same error when I push the image file.has anyone experienced this with their phone. I have a feeling its something to do with the SD card but can't be sure.any help would be appreciated. Thanks.
I know you must be thinking "Jedi"how can he can he call himself an androidjedi when he can't sort this simple problem (to some of you),but I must say even a Jedi needs to learn!

try adb remount before your command

Dunno if this will help but have tried changing the system to rw then try to push

Tried that no cigar

are you trying to push it into your sdcard or the phone system??
and remember the whole folder name has to be in the push so it woul have to look like
C:\Users\Android>ad push "C:\Users\Android\Downloads\Android\Nexus 1\Phone.apk" /sdcard/files
has to have full path of where you are pushing it from/too.. i have mine sdk setup to use adb in any directory as well why you dont see it in the sdk directory

@ilostchild
Thanks i will try that later today and let you know
As for pushing the file - i am trying to push it to the sd card - but i am not really sure as i am following instructions in the [HOW-TO] Revert HBOOT 0.35.0017 to 0.33.0012 thread in the forum
as i need to downgrade my Hboot from #17 to 12
are the commands different for pushing a file to the phone?

the more i think about i think i need to flash the file to the phone - but i will try your adb command format of specifying the location of the file in the comp

androidjedi said:
the more i think about i think i need to flash the file to the phone - but i will try your adb command format of specifying the location of the file in the comp
Click to expand...
Click to collapse
Ooo you want to push to sdcard.. ok then yea, you would type it like this
C:\android-sdk-windows\tools> adb push C:\Users\Android\Downloads\Android\signed-passion-FRF50-from-
ERE27.1e519a24.zip /sdcard*
if you dont have the option to use adb in any directory, then you have to be in the android sdk directory and in tools
cd android-sd-windows
cd tools
adb push(drag the file you want to push in the command prompt window) /sdcard*
sorry i know its detailed and im sure you know all these things.. but it kinda gets the questions out of the way for future problems to come

ilostchild said:
Ooo you want to push to sdcard.. ok then yea, you would type it like this
C:\android-sdk-windows\tools> adb push C:\Users\Android\Downloads\Android\signed-passion-FRF50-from-
ERE27.1e519a24.zip /sdcard*
if you dont have the option to use adb in any directory, then you have to be in the android sdk directory and in tools
cd android-sd-windows
cd tools
adb push(drag the file you want to push in the command prompt window) /sdcard*
sorry i know its detailed and im sure you know all these things.. but it kinda gets the questions out of the way for future problems to come
Click to expand...
Click to collapse
thanks for spending time on this-i am new to the android world so any help is welcome-however detailed or not
thanks will try that

ilostchild said:
Dunno if this will help but have tried changing the system to rw then try to push
Click to expand...
Click to collapse
how do i change the system to read write as i am still getting cannot copy file read only file error

androidjedi said:
how do i change the system to read write as i am still getting cannot copy file read only file error
Click to expand...
Click to collapse
do adb shell
su
Mount -o remount,rw /dev/block/mtdblock3 /system
then exit and exit
then do push

ilostchild said:
do adb shell
su
Mount -o remount,rw /dev/block/mtdblock3 /system
then exit and exit
then do push
Click to expand...
Click to collapse
tried that did the push and all i got was 950 KB/s <0 bytes in 76044.000s>
looks like its not pushing the file not sure what to do now

androidjedi said:
tried that did the push and all i got was 950 KB/s <0 bytes in 76044.000s>
looks like its not pushing the file not sure what to do now
Click to expand...
Click to collapse
Umm if you got that mesage you may have pushed it in right..

ilostchild said:
Umm if you got that mesage you may have pushed it in right..
Click to expand...
Click to collapse
does not seem to have worked for some reason as after flashing it should reboot in htc mode and then i would be able to flash a rom with the hboot12

May i ask what are you trying to push into your phone/sdcard?

ilostchild said:
May i ask what are you trying to push into your phone/sdcard?
Click to expand...
Click to collapse
I am trying to follow the instructions on the thread which can be found in the the following link forum.xda-developers.com/showthread.php?t=726258
basically trying to flash two image files that enable downgrading the Hboot from 0.35.0017 to 0.33.0012

androidjedi said:
I am trying to follow the instructions on the thread which can be found in the the following link forum.xda-developers.com/showthread.php?t=726258
basically trying to flash two image files that enable downgrading the Hboot from 0.35.0017 to 0.33.0012
Click to expand...
Click to collapse
managed to do it after just following the instructions and inoring what i thought was an error i managed to downgrade my happy days have a good weekend
will no doubt ask you for help another time cheers and thanks a lot

Welcome and congratz
Sent from my Nexus One using XDA App

[TOOL] Perma-Temp-Root Solution [Mac/Linux/Windows]

Remember, This is still a Temp Root & any Changes made will be Rest back to stock on a Reboot
Its stable & works 100%
I personally have not lost root with this method in over 48 hours.
Zero com.noshufou.android.su crashes.
Before Using!!
HTC Sync Must be Turned OFF
Put the Phone into Charge Mode only ( Not Disk Drive )
USB Debugging Must be Turned on
Restart your phone!
Lastly, if you're getting com.noshufou.android.su force close errors
Uninstall superuser prior to running scripts.​
If you Lose Root, all you have to do is open Terminal Emulator & type fixsu
No More Rebooting & running the exploit again for R/W on system to get Root back in place!​
Q. Is this permanent?
A. no, it's a temp root method..
Q. Will I lose SU Access at some point while running the OS?
A. You might, but open terminal and type fixsu to get root back.
Q. What about apps that need a reboot to use superuser?
A. Use Fast Reboot form the market for app that need a reboot.
Q. Can I push & remove items to system and will it work?
A. Yes, but all changes are reset on a reboot.
~~~~~~~~~
For Mac/Linux users
Once downloaded, extract vividtemproot.zip to your home/root folder.
(Typically named after your login, has a house icon in Finder's sidebar of places)
Open folder vividtemproot, double-click run_me_mac (or run_me_linux)
and thats is all!
Click here to download for Mac/Linux
(Updated 11/14 - 23:50)
~~~~~~~~~
For Windows Users
Once downloaded, extract where ever you please.
Double click _RUN_ME
and enjoy!
Click here to download for Windows
(Updated 11/14 - 23:50)​

Link for Windows is the Mac file...

CharlieMurphyIVXX said:
Link for Windows is the Mac file...
Click to expand...
Click to collapse
Thank you :]
Fixed

Looks interesting, but my method of using a bind mount from /data/local/bin to /system/xbin (apparently I could have used /vendor/bin instead) doesn't loose root after any time unless you reboot.
Bind mounts stay in memory, and aren't like symlinks that get flushed away when the system tries to re-read the filesystem, hence why I suggest using it rather than symlinks.
The bind mount eliminates the need for a 'fixsu' script at all, since there's no links that could potentially dissolve.
With that said, nice work!

thecubed said:
Looks interesting, but my method of using a bind mount from /data/local/bin to /system/xbin (apparently I could have used /vendor/bin instead) doesn't loose root after any time unless you reboot.
Bind mounts stay in memory, and aren't like symlinks that get flushed away when the system tries to re-read the filesystem, hence why I suggest using it rather than symlinks.
The bind mount eliminates the need for a 'fixsu' script at all, since there's no links that could potentially dissolve.
With that said, nice work!
Click to expand...
Click to collapse
I haven't lost root in going on ~60 hours, as as a newbie here, you definitely know far more than I do!
As you'll see in the fixsu, I redundantly copy su from /vendor/bin
to /system/xbin/ from which I hardlink (as you'd know is virtually the same as bind mounting in this case) to /system/bin
I added the fixsu, as a last resort, in case the something would dissolve, but unless someone really fudges something up, the fixsu shouldn't be needed
As my programming teacher once told me: the code doesn't need to be pretty as long as it works.
And through that philosophy I've used a lot of redundancies, that may or may not need to be there,
but they'll definitely keep anyone from having any sort of issues using the scripts!
P.S. Thank you :]

Thanks, I'll try this out and report back.
Sent from my HTC PH39100 using xda premium

It worked fine, I've got root access -- Thank you!
However, there's this error message at the end of the _RUN_ME.bat script:
"The syntax of the command is incorrect" -- please take a look at the attached image.
Thank you again for the root!

http://pastebin.com/MkGHWadW
appears to have failed for me
Drew

The device rebooted itself -- the "root" is lost

guys i cannot get this to work for me
i get thefollowing error
Congrats, zergRush worked! Moving on...
Mounting file system as writeable
Installing Busybox
2759 KB/s (777216 bytes in 0.275s)
1518+0 records in
1518+0 records out
777216 bytes transferred in 0.187 secs (4156235 bytes/sec)
Installing Superuser
1808 KB/s (22228 bytes in 0.012s)
rm failed for /system/xbin/su, No such file or directory2852 KB/s (785801 bytes in 0.269s)
All done!
Exiting...
Press any key to continue . . .

rinnycoop121 said:
guys i cannot get this to work for me
i get thefollowing error
Congrats, zergRush worked! Moving on...
Mounting file system as writeable
Installing Busybox
2759 KB/s (777216 bytes in 0.275s)
1518+0 records in
1518+0 records out
777216 bytes transferred in 0.187 secs (4156235 bytes/sec)
Installing Superuser
1808 KB/s (22228 bytes in 0.012s)
rm failed for /system/xbin/su, No such file or directory2852 KB/s (785801 bytes in 0.269s)
All done!
Exiting...
Press any key to continue . . .
Click to expand...
Click to collapse
The rm failed for /system/xbin/su, No such file or directory is not actually an error, that's my fault. In my original script, I try to remove that file in case it exists, but if it doesn't exist, it'll just do nothing. So there's no worries there!

drewdatrip said:
http://pastebin.com/MkGHWadW
appears to have failed for me
Drew
Click to expand...
Click to collapse
Tends to be what occurs when the files aren't extracted to the correct place.
You can change the opening line in the script to the direct path to the folder 'resources' and you won't have any issues.

3f62011 said:
It worked fine, I've got root access -- Thank you!
However, there's this error message at the end of the _RUN_ME.bat script:
"The syntax of the command is incorrect" -- please take a look at the attached image.
Thank you again for the root!
Click to expand...
Click to collapse
I don't own a Windows box, an had to write the Windows bat file
without giving it a test run for errors.
I'm sure I did mess up the syntax, an probably left some command that isn't windows relavent at the end of the script.
No worries, you've got root, and shouldn't loose it.

bjg222 said:
The rm failed for /system/xbin/su, No such file or directory is not actually an error, that's my fault. In my original script, I try to remove that file in case it exists, but if it doesn't exist, it'll just do nothing. So there's no worries there!
Click to expand...
Click to collapse
I tried to pipe all errors out to null, as I took a mash up of your code, my code, and and another guys code, and left a lot of "in case it exists" type of lines in the code, to make sure no one would have any issues.
Apparently I didn't pipe it all to null well enough
The mac/linux version you only see 'starting' and 'finished' haha

rpendrick said:
Tends to be what occurs when the files aren't extracted to the correct place.
You can change the opening line in the script to the direct path to the folder 'resources' and you won't have any issues.
Click to expand...
Click to collapse
I thought the same with the read out.
Your recommending to place them at the root of the user correct?
Drew
Sent from my SGH-I777 using xda premium

drewdatrip said:
I thought the same with the read out.
Your recommending to place them at the root of the user correct?
Drew
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
PM's were sent, I uploaded the wrong zip to megaupload for macs.
All is fixed now.

rpendrick said:
PM's were sent, I uploaded the wrong zip to megaupload for macs.
All is fixed now.
Click to expand...
Click to collapse
Yes, works much better with something in the folder.

Scrog said:
Yes, works much better with something in the folder.
Click to expand...
Click to collapse
Yup. Im registering root now. However Superuser is crashing and im able to use the fixsu command
Im looking into it more now
Drew
Sent from my SGH-I777 using xda premium

drewdatrip said:
Yup. Im registering root now. However Superuser is crashing and im able to use the fixsu command
Im looking into it more now
Drew
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
I was able to update superuser, but titanium back up doesn't see either SD card.

drewdatrip said:
Yup. Im registering root now. However Superuser is crashing and im able to use the fixsu command
Im looking into it more now
Drew
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Superuser crashes when it is the lastest versions.
Do a google search for superuser.apk 3.0
I thought I included it in the package, but perhaps, once again in a rush
fudged that up too...

[DEV][TOOL] Generic SBK dumper [Source included]

Generic Nvidia Tegra Secure Boot Key Dumper, v0.4
**************************************
YOU MUST GET ROOT BEFORE PROCESSING!!!
This is a temp memory only fix, after you reboot your phone, everything will restore to it's original status. So it WILL NOT brick your phone at all!
**************************************
I am not sure it work for your devices or not, because I only get a SU660 device!
So , you must knew that P880 use a Secure Boot Key to encrypt its nflash communication, if you don't know the SBK, you can't use nvflash backup/restore your partitions.
I found that in the linux kernel, there is some protection that block the user try to read out SBK when the phone in "odm_production" status. So I designed a little software try to patch the phone RAM to bypass the protection.
This is a kernel patcher which will remove the protection when trying to read /sys/firmware/fuse/secure_boot_key
The dumper will patch the kernel in memory, and let you show the secure_boot_key.
Hope it work for all tegra devices.
Usage:
1. adb push dumpSBK /data/local/
2. adb shell
su
chmod 0777 /data/local/dumpSBK
/data/local/dumpSBK
After that, you can
4. cat /sys/firmware/fuse/secure_boot_key
dumpSBK will search the first 1MB physical address(which kernel will be there), and try to patch it.
Usage: dumpSBK [star_mem_addr in KB]
for example: dumpSBK 32
which will search the 32KB~1MB physical memory.
2012/12/31:
re-compile it with -static switch, so it can run on all android platform.
update instructions.
2013/01/01:
modify the program, and let you select which memory range to patch.
usage: dumpSBK [start_memory_addr] [end_memory_addr]
for example: dumpSBK 1 1024
which will search 1MB ~ 1024MB memory and try to patch the kernel.
2013/01/01:
v0.3 add more error detection in the file.
2013/01/06:
v0.4 wil search the first 1MB physical memory, you can specify the start_address , for example dumpSBK 32
and update the search pattern , it will fit for more compiler options.
2013/01/07:
Secure_Boot_Key Dumper for tegra2/tegra3 v0.1
1. adb push ss.ko /sdcard/
2. adb shell
su
cd /sdcard/
insmod ss.ko
dmesg
3. at the end of dmesg, you should see the secure_boot_key.....
2013/01/08:
v0.2 dump all known fuses.....

If you get a error:
Kernel patching failed! Abort....
that means your device kernel has a differnt tegra source code, or compiled with a different compiler........
Please let me know which kernel source code and compiler / compile switch it used.

marsgod said:
If you get a error:
Kernel patching failed! Abort....
that means your device kernel has a differnt tegra source code, or compiled with a different compiler........
Please let me know which kernel source code and compiler / compile switch it used.
Click to expand...
Click to collapse
will it hard brick the phone???

razerblade17 said:
will it hard brick the phone???
Click to expand...
Click to collapse
Do you want to try and find out? I certainly don't.
I like my phone and don't want to end up with an expensive paperweight instead :banghead:

SimonTS said:
Do you want to try and find out? I certainly don't.
I like my phone and don't want to end up with an expensive paperweight instead :banghead:
Click to expand...
Click to collapse
i'd have tried if i didnt sell mine
plus this wont brick the device
nothing can since bootloader's lock so u practically cant mess up anything that matters for booting up

The Troll said:
i'd have tried if i didnt sell mine
plus this wont brick the device
nothing can since bootloader's lock so u practically cant mess up anything that matters for booting up
Click to expand...
Click to collapse
Yep, i think Troll isn't trolling us i would try it out ,but i'm waitin' for my LG, factory reset via recovery bricked it.

This is a temp memory only fix, after you reboot your phone, everything will restore to it's original status. So it WILL NOT brick your phone at all!
The patcher will patch a single byte in your phone RAM, it will not modify any bit in your NAND Flash.

C:\adb>adb shell chmod 0777 /data/local/dumpSBK
Unable to chmod /data/local/dumpSBK: Operation not permitted
I got this

Here is a log of what happened, after I ran the program on my 4X with 10H F/W:
[email protected]:/data/local # /data/local/dumpSBK
/data/local/dumpSBK
[1] + Stopped (signal) /data/local/dumpSBK
[email protected]:/data/local # cat /sys/firmware/fuse/secure_boot_key
cat /sys/firmware/fuse/secure_boot_key
[1] + Segmentation fault /data/local/dumpSBK
Click to expand...
Click to collapse

^ You guys have rooted phone and debugging turned on? maybe that's why these errors.

phone rooted, recheked with root checker.
I have debuging mode one.
But i cant push files to /data/local/
C:\o4xr>adb push dumpSBK /data/local/
push: dumpSBK/Readme.txt -> /data/local/Readme.txt
failed to copy 'dumpSBK/Readme.txt' to '/data/local/Readme.txt': Permission deni
ed
Click to expand...
Click to collapse
So i put those files there with es file explorer and try to run second comand:
C:\o4xr>adb shell chmod 0777 /data/local/dumpSBK
Unable to chmod /data/local/dumpSBK: Operation not permitted
Click to expand...
Click to collapse
Who can explain why?

s7ar73r said:
phone rooted, recheked with root checker.
I have debuging mode one.
But i cant push files to /data/local/
So i put those files there with es file explorer and try to run second comand:
Who can explain why?
Click to expand...
Click to collapse
uhmm
as i seem to recall, the hello world rooting method *only known method* turns on access to that location..
thats where superuser and binaries are added
so if im correct u'd be able to push it if u follow the rooting method and adding the commands to the root.bat *or whatever its name it* that we run in pc by using notepad or anything..
so it should reroot and push ur desired file as well
*again, dun remember, been months but im sure hello world/backuptest thingy will be useful*

k1337Ultra said:
Here is a log of what happened, after I ran the program on my 4X with 10H F/W:
Click to expand...
Click to collapse
I get the this,too.
the v1 patch did not completely work.

The Troll said:
uhmm
as i seem to recall, the hello world rooting method *only known method* turns on access to that location..
thats where superuser and binaries are added
so if im correct u'd be able to push it if u follow the rooting method and adding the commands to the root.bat *or whatever its name it* that we run in pc by using notepad or anything..
so it should reroot and push ur desired file as well
*again, dun remember, been months but im sure hello world/backuptest thingy will be useful*
Click to expand...
Click to collapse
Its not the only known method... but now I don't have time, even to think... I just woke up and came to the computer.
You need to think widder
Gonna back to sleep :angel:

k1337Ultra said:
Here is a log of what happened, after I ran the program on my 4X with 10H F/W:
Click to expand...
Click to collapse
En.... I think it is due to I compiled the dumpSBK with 4.1.2 android, so it will not work on a ICS rom... I will check it later...

s7ar73r said:
C:\adb>adb shell chmod 0777 /data/local/dumpSBK
Unable to chmod /data/local/dumpSBK: Operation not permitted
I got this
Click to expand...
Click to collapse
You MUST root your device.
then type
adb root
to get the adb rooted work.
Of couse, you must have your device USB debug ON.

please do all the steps the right way , starting with the OP instruction you the right way.
OP is assuming we got a "unsecure" booted device, which we have not exactly due to the locked bootloader.
so its pointless to write "root" instruction froms adb when the device is in secure mode. OP is now told and should update the instructions, thank you.
ignore all the "adb shell" instruction and log into the device with "adb shell" once only.
in that shell which is opened execute the "su", so you get a root # prompt.
then run instructions given and skip all "adb shell" infront.
thats it, good luck.
edit:
adb remount,adb root and running root commands only work on unsecure devices , we got ro.secure=1 here and adb not allowed to run root commands

i think it's better toroot Your 4X with Dexter http://forum.xda-developers.com/showpost.php?p=30574547&postcount=85 because it doesn't have any issues, for me with 1st root method for example titanium backup wasn't working.
@marsgod, yep - we don't have 4.1.2 but 4.0.3, but u can leave this version because we'll get 4.1.2 in january

k1337Ultra said:
Here is a log of what happened, after I ran the program on my 4X with 10H F/W:
Click to expand...
Click to collapse
[email protected]:/data/local # /data/local/dumpSBK
/data/local/dumpSBK
[1] + Stopped (signal) /data/local/dumpSBK
[email protected]:/data/local # cat /sys/firmware/fuse/secure_boot_key
cat /sys/firmware/fuse/secure_boot_key
[1] + Segmentation fault /data/local/dumpSBK
i have same result . segmentation fault
whats wrong?

bullghost said:
[email protected]:/data/local # /data/local/dumpSBK
/data/local/dumpSBK
[1] + Stopped (signal) /data/local/dumpSBK
[email protected]:/data/local # cat /sys/firmware/fuse/secure_boot_key
cat /sys/firmware/fuse/secure_boot_key
[1] + Segmentation fault /data/local/dumpSBK
i have same result . segmentation fault
whats wrong?
Click to expand...
Click to collapse
after adb shell type su, u should have [email protected], not [email protected]
@edit so... anyone tested it in right way?

Removing System Apps

I'm rooted and am trying to mount the system to remove bloatware apps... However everytime Titanium Backup removes it and I reboot it's still there...
Anyone have any ideas?

System is protected: you can't modify it while the phone is booted. You'll have to make a zip or whatever to delete it in recovery.

You have to be kidding me...
I've spent all day long trying to root this bastard phone and that didn't work then I managed it and now I can't disable, remove any apps ?
So much for HTC being dev friendly

fkofilee said:
You have to be kidding me...
I've spent all day long trying to root this bastard phone and that didn't work then I managed it and now I can't disable, remove any apps ?
So much for HTC being dev friendly
Click to expand...
Click to collapse
It seriously took you all day to root? What went wrong?

Did you try just freezing the app instead?

Brand new trick from HTC?Didn't have it in hox+
Sent from my Nexus 4 using Tapatalk 2

afilopou said:
Brand new trick from HTC?Didn't have it in hox+
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
So you can no longer go into ES explorer, mount root/system go to system > apps and delete whatever you want ?
Sent from my HTC Incredible S using Tapatalk 2

The recovery flashed but wouldnt boot , managed to get round it when i discovered POB with his superboot Thank god for the desire C
Then i realised that i couldnt flash anything because I manged to install 6.0.2.8 as a boot img, and 6.0.3.0 as a proper recovery.
Then i didnt have any files on the device to flash boohoo so i managed to get ADB sideload working through the AIO One Toolkit... And managed to flash AHRD finally getting a working device,
As you see Im a seasoned vet at these things but the HTC One has been the first device that has stumped me....
----------------------
The apps issue is not unkwown for HTC however they havent done this for a while.... Back with the G2 they did exactly the same thing and yes ive frozen them but there should be away to remove system apps for us through root.... But i cant remember how, Throwing it into ADB Shell and requesting SU along with a Remount works fine but still would like to remove the apps.
Im also looking for someone with a locked phone... (Sim Locked) i have a theory and it worked on the Desire C Anyone wanna help?

fkofilee said:
I'm rooted and am trying to mount the system to remove bloatware apps... However everytime Titanium Backup removes it and I reboot it's still there...
Anyone have any ideas?
Click to expand...
Click to collapse
Delete the apps with titanium and power off the phone. Don't do a restart.

Already tried that ^_^

You need to flash a custom kernel with a modified ramdisk to disable system protection Without doing that you're like deleting an app on windows with deepfreeze on it

Is that the only solution?
There are so many bloated useless and intrusive (cr)apps on this phone it's unbelievable.

Other solution is boot in recovery and delete it there. Either thru adb while in recovery mode, flashable zip or through file manager(if you're using TWRP). Other than that nope

Hmmm I'm thinking adb through recovery here but how do I got about doing this?

fkofilee said:
Hmmm I'm thinking adb through recovery here but how do I got about doing this?
Click to expand...
Click to collapse
the joys of a s-on devices
read up on adb commands...
or use the zip I attached and edit line 18 in this format with the apps you want to get rid of, use a file explorer to get the proper names.
make a backup first in case you mess up something
Code:
delete("/system/app/xxxxx.apk", "/system/app/xxxx.odex", "/data/app/xxxxx.apk");

The best way to remove apps in recovery is through adb:
Code:
adb shell
sysrw
rm /system/app/abc.apk

the simple way is ROM CLEANER, but isn't available yet for the One.
cheers

fkofilee said:
Hmmm I'm thinking adb through recovery here but how do I got about doing this?
Click to expand...
Click to collapse
type the following commands.
Code:
adb shell
su
cd /system/app/
ls
rm <insert the name of the apk you want to delete here which can be found in the list shown by the ls command>

Riyal said:
type the following commands.
Code:
adb shell
su
cd /system/app/
ls
rm <insert the name of the apk you want to delete here which can be found in the list shown by the ls command>
Click to expand...
Click to collapse
I dont have a One, and dont plan on having one (ever, thanks to this thread! I think I'll stick to Sony, they have instructions to unlocking bootloader on their official website)
BUT, if the system is locked, it should be locked trough ADB too, so I guess what I'd try is install busybox, custom recovery, go into recovery, connected it to the PC (or a mac, but since we're on no-apple forum, I'll assume PC), mounting system there and doing your thing.
You can install busybox and custom recovery right?
Edit: never mind, I should really learn to read. Sometimes I think I'm dyslexic a little, just for words, not letters.
I did not see the 'recovery' part mentioned.
Anywho, mounting system is what you forgot, so at least I said something helpful

ogdobber said:
the joys of a s-on devices
read up on adb commands...
or use the zip I attached and edit line 18 in this format with the apps you want to get rid of, use a file explorer to get the proper names.
make a backup first in case you mess up something
Code:
delete("/system/app/xxxxx.apk", "/system/app/xxxx.odex", "/data/app/xxxxx.apk");
Click to expand...
Click to collapse
MacHackz said:
The best way to remove apps in recovery is through adb:
Code:
adb shell
sysrw
rm /system/app/abc.apk
Click to expand...
Click to collapse
limx said:
the simple way is ROM CLEANER, but isn't available yet for the One.
cheers
Click to expand...
Click to collapse
Riyal said:
type the following commands.
Code:
adb shell
su
cd /system/app/
ls
rm <insert the name of the apk you want to delete here which can be found in the list shown by the ls command>
Click to expand...
Click to collapse
issak42 said:
I dont have a One, and dont plan on having one (ever, thanks to this thread! I think I'll stick to Sony, they have instructions to unlocking bootloader on their official website)
BUT, if the system is locked, it should be locked trough ADB too, so I guess what I'd try is install busybox, custom recovery, go into recovery, connected it to the PC (or a mac, but since we're on no-apple forum, I'll assume PC), mounting system there and doing your thing.
You can install busybox and custom recovery right?
Edit: never mind, I should really learn to read. Sometimes I think I'm dyslexic a little, just for words, not letters.
I did not see the 'recovery' part mentioned.
Anywho, mounting system is what you forgot, so at least I said something helpful
Click to expand...
Click to collapse
All Wonderful Ideas folks, however i had a go at this last night, it was a fricking nightmare even mounting ADB through recovery