I am running stock DNA, rooted, and with CWM touch recovery. For myself, being root is not merely a luxury, it is a need. Most importantly, I cannot stand having a crippled unix terminal without busybox, which of course, requires root.
I know not what the imminent OTA will bring, but root is too precious to risk losing. I would therefore like to engage in a DNA-specifc discussion about disabling the OTA update.
From what I can tell so far, the two methods include:
1) renaming the otacerts.zip file in /etc/security to a .bak file. This will not work in the present case, since /etc is mounted at /system/etc, and /system can only temporarily be mounted rw due to us being stuck with "S-ON" for now.
2) installing "FOTAkill.apk", or, flashing its corresponding zip (attached below) in custom recovery. Again, in the present case, this file was written for the EVO, and will most certainly not work. The updater-script in the zip can be modified to reflect the correct mount points, but there is a corresponding binary which I have no clue contains what, and would certainly need some expert opinion about.
Any ideas ye fine fellers?
You could always do load ota root keeper from the market back your root up temp un root via app update ota and then re root using the app, I have done this on other devices and I never lost root. Worked well. Might be worth a shot.
Sent from my HTC6435LVW using xda app-developers app
manzdagratiano said:
I am running stock DNA, rooted, and with CWM touch recovery. For myself, being root is not merely a luxury, it is a need. Most importantly, I cannot stand having a crippled unix terminal without busybox, which of course, requires root.
I know not what the imminent OTA will bring, but root is too precious to risk losing. I would therefore like to engage in a DNA-specifc discussion about disabling the OTA update.
From what I can tell so far, the two methods include:
1) renaming the otacerts.zip file in /etc/security to a .bak file. This will not work in the present case, since /etc is mounted at /system/etc, and /system can only temporarily be mounted rw due to us being stuck with "S-ON" for now.
2) installing "FOTAkill.apk", or, flashing its corresponding zip (attached below) in custom recovery. Again, in the present case, this file was written for the EVO, and will most certainly not work. The updater-script in the zip can be modified to reflect the correct mount points, but there is a corresponding binary which I have no clue contains what, and would certainly need some expert opinion about.
Any ideas ye fine fellers?
Click to expand...
Click to collapse
There are system writable kernels out there, and you can always rename your files in recovery. S-Off is not an issue in this scenario.
delete checkinprovider.apk, cotaclient.apk, and updater.apk from /system/app
Jaggar345 said:
You could always do load ota root keeper from the market back your root up temp un root via app update ota and then re root using the app, I have done this on other devices and I never lost root. Worked well. Might be worth a shot.
Click to expand...
Click to collapse
I have indeed heard this alternative thrown around but I am not willing to chance it; I have seen an equal amount of horror stories about people having their systems fried with this method (the Droid X for instance, which I had and where the last update broke root).
SolusCado said:
There are system writable kernels out there, and you can always rename your files in recovery. S-Off is not an issue in this scenario.
Click to expand...
Click to collapse
I will look at what's out there and if it is stable enough to be flashed. How does one rename files in recovery though? I rebooted into CWM (touch) and I see no such option - unless you can remount a partition and rename files in it somehow.
nitsuj17 said:
delete checkinprovider.apk, cotaclient.apk, and updater.apk from /system/app
Click to expand...
Click to collapse
This avenue seems promising. Has anyone tried this before? Also, how does one delete these in the S-ON situation? (I'm assuming recovery is the answer). I feel if I remounted rw, deleted and then rebooted, they will be right back where they are.
manzdagratiano said:
This avenue seems promising. Has anyone tried this before? Also, how does one delete these in the S-ON situation? (I'm assuming recovery is the answer). I feel if I remounted rw, deleted and then rebooted, they will be right back where they are.
Click to expand...
Click to collapse
If you install a kernel with /system writing enabled you can just delete them normally.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
If you install a kernel with /system writing enabled you can just delete them normally.
Click to expand...
Click to collapse
Great... thanks! I am looking into custom kernels. By the way, if custom kernels that do allow write to /system can be concocted, why is S-ON an issue at all? I was under the impression that this has to do with NAND memory being inaccessible, which seems to be a lower level issue than the kernel.
manzdagratiano said:
Great... thanks! I am looking into custom kernels. By the way, if custom kernels that do allow write to /system can be concocted, why is S-ON an issue at all? I was under the impression that this has to do with NAND memory being inaccessible, which seems to be a lower level issue than the kernel.
Click to expand...
Click to collapse
With s on we can not.
Flash radios
Flash kernels in recovery.
Change the splash screen
Go back to a locked bootloader
And a few other things I'm probably forgetting.
Sent from my HTC6435LVW using xda app-developers app
Related
I have searched for but found nothing for our leaked bretheren (me included) that would allow us to downgrade. Would the downgrade method of days gone by be applicable as well? If so can someone provide details please?
I am specifically looking to do so that I may have a non leak phone.
Namaste and Thanks!
PS- go see Scott Pilgrim, IT RUCKIN FAWKS XD
Sent from my FroyoEris using XDA App
nomorefear said:
I have searched for but found nothing for our leaked bretheren (me included) that would allow us to downgrade. Would the downgrade method of days gone by be applicable as well? If so can someone provide details please?
I am specifically looking to do so that I may have a non leak phone.
Namaste and Thanks!
PS- go see Scott Pilgrim, IT RUCKIN FAWKS XD
Sent from my FroyoEris using XDA App
Click to expand...
Click to collapse
Install the Leak-V3 PB00IMG.ZIP rom via HBOOT, or run the "Official" 2.1 RUU utility. They produce an essentially identical result.
The July 17 OTA will pop up sometime after the first boot when you do the above - possibly before you have even finished reconfiguring the phone.
bftb0
I don't want hboot 1.49 however.
nomorefear said:
I don't want hboot 1.49 however.
Click to expand...
Click to collapse
Fine. Then just unzip the Leak-V3 PB00IMG.ZIP file to a folder on your SD card and manually install each of the images contained therein using Amon_RA and the (adb shell) command line.
Just be aware that
1) "recovery.img" and "boot.img" are bootable Android images, so they are installed into their respective partitions (with the Amon_RA recovery booted) using the "flash_image" program.
2) "system.img" and "userdata.img" are yaffs2 (filesystem images); these are installed into the partitions /system and /data (respectively) in a four-step process:
- mount the partition
- do a (dangerous) rm -rf * command INSIDE THAT MOUNTED PARTITION to delete all the files
- perform an unyaffs command within that mount point using the respective image file
- unmount the partition.
Note that the the steps that I have just described are EXACTLY the same thing that a Nand Restore does. You could either read the shell script nandroid-mobile.sh (do an "adb pull /sbin/nandroid-mobile.sh nandroid-mobile.sh") to see the exact set of commands that are used...
OR, if you want, you could hand-create a fake Nandroid backup set from the
boot.img
system.img
userdata.img (renamed to data.img)
files, and do a Nandroid restore of them. Then, as a final step (still inside Amon_RA) do a
# flash_image recovery /sdcard/the-pb00img-that-i-unpacked/recovery.img
Note that my instructions are a little bit vague; that was done on purpose, because you need to understand what you are doing before you attempt it. If you do enough research to decipher and completely understand the jibberish above, it will be safe to perform.
bftb0
nomorefear said:
I don't want hboot 1.49 however.
Click to expand...
Click to collapse
Actually, I just re-read your first post that intimates that you were a leaker.
That means that you must have had the 1.49.0000 S-ON bootloader on your phone already - the same one that is in the PB00IMG.ZIP file of the Leak-V3.
Did you replace it somehow after you rooted? If not, the objection is removed.
bftb0
Before I finally rooted, I used the verizon ota RUU I think. Then I rooted. My understanding is my firmware is a bit shoddy due to being a leaker, even with the RUU.... Maybe I'm being a noob about it. I do understand the instructions and I'm very much capable of most things explained in this forum. Thanks again b
Sent from my FroyoEris using XDA App
The only thing I think might work is the jcase flash any ruu/ota/hboot thingy I found earlier today. Does it?
Sent from my FroyoEris using XDA App
I got the 1.9.0004 Hboot on the Amaze to the guys with Revolutionary and hopefully they can find some exploit wizardry to save us all from the dreaded HTC unlock.
In the meantime, I can confirm that their ZergRush exploit works on the Amaze 4G with software version 1.36.531.5 (untested on any others, but probably still fine). Link: http://forum.xda-developers.com/showthread.php?t=1296916
The exploit provides temporary root only and any root-level changes will not survive a reboot. This means you can use ZergRush, then push the su app and binary via adb and then use root apps and delete bloat, etc but on reboot it will all go back to the way it was before (the nand partition is not unlocked with this).
Cayniarb said:
I got the 1.9.0004 Hboot on the Amaze to the guys with Revolutionary and hopefully they can find some exploit wizardry to save us all from the dreaded HTC unlock.
In the meantime, I can confirm that their ZergRush exploit works on the Amaze 4G with software version 1.36.531.5 (untested on any others, but probably still fine). Link: http://forum.xda-developers.com/showthread.php?t=1296916
The exploit provides temporary root only and any root-level changes will not survive a reboot. This means you can use ZergRush, then push the su app and binary via adb and then use root apps and delete bloat, etc but on reboot it will all go back to the way it was before (the nand partition is not unlocked with this).
Click to expand...
Click to collapse
can we do anytime type of a recovery?
Nice Job bro
Sent from my HTC_Amaze_4G using xda premium
anybody know where i can find a tutorial on how to do this? the link provided has instructions but very vague... i really would like to get this thing rooted... even if just temporary
Enzopreme said:
anybody know where i can find a tutorial on how to do this? the link provided has instructions but very vague... i really would like to get this thing rooted... even if just temporary
Click to expand...
Click to collapse
It's all there, trust me. follow the instructions with adb in the first post then refer to http://forum.xda-developers.com/showthread.php?p=18373159 in the same thread to push su and superuser to the phone.
Sent from my HTC_Amaze_4G using Tapatalk
Confucius say - Longest journey begins with first step
Credit's for my man Revolution being in IRC# asking question's about ZR haha & nice , remember this only allow's you to run root only applications .
Does this zergrush allow you to remove the bloatware and it stays gone after a reboot? Or do they come back..
Adamp24 said:
Does this zergrush allow you to remove the bloatware and it stays gone after a reboot? Or do they come back..
Click to expand...
Click to collapse
It comes back on reboot.
That's so weird. If you remove the system .apks via uninstall.. how would they magically restore themselves?
There has to be a way to clear off this bloatware! =\
Adamp24 said:
That's so weird. If you remove the system .apks via uninstall.. how would they magically restore themselves?
There has to be a way to clear off this bloatware! =\
Click to expand...
Click to collapse
There is..... its called "permaroot"! Relax and be patient... good things always come to those who wait...
Adamp24 said:
That's so weird. If you remove the system .apks via uninstall.. how would they magically restore themselves?
There has to be a way to clear off this bloatware! =\
Click to expand...
Click to collapse
NAND is still locked, anything root level reverts to the way it way after a reboot and this is only a temp root.
when i try to adb shell chmod 755 /data/ local/ zergRush i get a error message "unable to chmod read-only file system"....any thoughts
bizal05 said:
when i try to adb shell chmod 755 /data/ local/ zergRush i get a error message "unable to chmod read-only file system"....any thoughts
Click to expand...
Click to collapse
Either change permissions of the file, or see if a file manager will let you change the folder to R/W. Since i do not have my Amaze yet (in the mail), I cannot go to the folder to see if you can do the latter without root.
Does not work on Wind's Amaze ROM.
Would this be a possible solution to our kernel flashing problems, I know it works for the evo
Sent from my HTC Amaze 4G using XDA App
DEFINITIONOFREAL said:
Would this be a possible solution to our kernel flashing problems, I know it works for the evo
Sent from my HTC Amaze 4G using XDA App
Click to expand...
Click to collapse
It's possible. In fact I mentioned this about a month ago to a developer.
I would like to see one that has a couple of options such as flashing recovery and flashing boot.img files.
You can easy push the flash_image binary to /system/bin and set the permission to 755. In fact my CWMFaux kernel does just that. Faux stopped using it because it doesn't always work.
In fact I made it so easy that all you need to do is push the boot.img to /system and reboot. Yet... no one uses it. In fact I suggested to a couple of rom developers to simply add the binary file to /system/bin so that you can at least run the command from terminal but they don't even want to do that. I like being able to update my recovery at anytime by entering "flash_image recovery /sdcard/recovery.img" and then just rebooting to recovery. You can easily do that for kernels too. But I suppose it's so much easier to carry a computer around.
Binary100100 said:
It's possible. In fact I mentioned this about a month ago to a developer.
I would like to see one that has a couple of options such as flashing recovery and flashing boot.img files.
You can easy push the flash_image binary to /system/bin and set the permission to 755. In fact my CWMFaux kernel does just that. Faux stopped using it because it doesn't always work.
In fact I made it so easy that all you need to do is push the boot.img to /system and reboot. Yet... no one uses it. In fact I suggested to a couple of rom developers to simply add the binary file to /system/bin so that you can at least run the command from terminal but they don't even want to do that. I like being able to update my recovery at anytime by entering "flash_image recovery /sdcard/recovery.img" and then just rebooting to recovery. You can easily do that for kernels too. But I suppose it's so much easier to carry a computer around.
Click to expand...
Click to collapse
Im going to contact joeykrim and see if I can get him to add support in his app, and Ive been using your method since I got the phone (2 days ago) and started reading, but still a little hassle, and a big htc fail
Sent from my HTC Amaze 4G using XDA App
DEFINITIONOFREAL said:
Im going to contact joeykrim and see if I can get him to add support in his app, and Ive been using your method since I got the phone (2 days ago) and started reading, but still a little hassle, and a big htc fail
Sent from my HTC Amaze 4G using XDA App
Click to expand...
Click to collapse
Keep me posted will ya?
I believe that Faux and other developers would have to use the zImage kernel flashing technique to get it to work with his existing app but I'm sure he can simplify it to accept .img files and the .ko files in the /system/lib directory of a zip file. It actually should be very easy. It took me about ten mintues with testing included to create the script for my method. I just can't code for apps else it would be done by now.
DEFINITIONOFREAL said:
Im going to contact joeykrim and see if I can get him to add support in his app, and Ive been using your method since I got the phone (2 days ago) and started reading, but still a little hassle, and a big htc fail
Sent from my HTC Amaze 4G using XDA App
Click to expand...
Click to collapse
I contacted pershoot, no answer lol!!!
Joeykrim is willing to support the Amaze, he just needs testers, this would be a great backup incase the new script failed to push the kernel. I'll keep everyone posted with updates
Sent from my HTC Amaze 4G using XDA App
I've been working with joeykrim getting his app setup for our device, it looks like it should work, hopefully, within the next couple of days we can get this working and released
Sent from my HTC Amaze 4G using XDA App
DEFINITIONOFREAL said:
I've been working with joeykrim getting his app setup for our device, it looks like it should work, hopefully, within the next couple of days we can get this working and released
Sent from my HTC Amaze 4G using XDA App
Click to expand...
Click to collapse
That would be wonderful!
I'm tired of having to repeat myself.
flash_image boot /sdcard/boot.img
flash_image recovery /sdcard/recovery.img
Binary100100 said:
That would be wonderful!
I'm tired of having to repeat myself.
flash_image boot /sdcard/boot.img
flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
I just wish the devs would use your script, it would make things so much easier
Sent from my HTC Amaze 4G using XDA App
DEFINITIONOFREAL said:
I just wish the devs would use your script, it would make things so much easier
Sent from my HTC Amaze 4G using XDA App
Click to expand...
Click to collapse
Once I see that they do I can work out something else like:
kernelupdate
recoveryupdate
kernelupdate would be
flash_image boot /sdcard/kernel/*boot*.img
recoveryupdate would be
flash_image recovery /sdcard/recovery/*recovery*.img
So that if you place ANY of the appropriate img file in the perspective folders on the sdcard partition it would flash the .img by just entering either of the two commands from adb shell or terminal.
But I'm not going to waste my time if the devs don't want to use it.
Binary100100 said:
Once I see that they do I can work out something else like:
kernelupdate
recoveryupdate
kernelupdate would be
flash_image boot /sdcard/kernel/*boot*.img
recoveryupdate would be
flash_image recovery /sdcard/recovery/*recovery*.img
So that if you place ANY of the appropriate img file in the perspective folders on the sdcard partition it would flash the .img by just entering either of the two commands from adb shell or terminal.
But I'm not going to waste my time if the devs don't want to use it.
Click to expand...
Click to collapse
could a script be written to automatically flash these while installing/flashing the custom rom? This would cut down atleast the step for flashing kernels for a lot of noobs!!
seansk said:
could a script be written to automatically flash these while installing/flashing the custom rom? This would cut down atleast the step for flashing kernels for a lot of noobs!!
Click to expand...
Click to collapse
Actually, yes! I did add it to the init.d script but since xboarder had removed the init.d scripts from his rom it doesn't work anymore. But you sure could. It was basically how I was setting up my CWMFaux kernels. However it didn't seem to work 100% of the time. Couldn't figure out why.
It basically worked like this...
Flashing the CWM custom kernel .zip via recovery.
copies boot.img to /system
copies init.d 06tweaks script to init.d folder.
copies and set permissions for flash_image binary and kernelupdate script to /system/bin directory.
You then boot your phone up which triggers the init.d script which commands the kernelupdate script to initiate. The kernel update script is simply using the flash_image binary command "flash_image boot /system/boot.img" and it automatically updates the kernel. Then the init.d script removes the boot.img file from the /system directory to keep it from flashing upon every boot.
I would like to change it to /sdcard directory but there's the problem that the sdcard doesn't get mounted until the very end. WAY after the system. Which is why I stored it there. The system gets mounted even before the data partition so I couldn't even store the file in data because the script would run even before the data partition could mount. Basically the script is initiated while your still looking at the boot animation. Pretty much when your softkey backlights and led light comes on it flashes the new kernel. It's a pretty neat workaround if I must say but unfortunately nowhere near perfect and not even close to having an s-off workaround.
Now if you don't mind the fact that it won't be initiated upon boot I could make it so that it will flash any file in a perspective folder on the sdcard.
example:
kernelupdate would update the kernel with any *boot*.img file located in a certain directory... say /sdcard/kernel
recoveryupdate would update the recovery with any *recovery*.img file located in a certain directory... say /sdcard/recovery
The problem:
Some people would want to collect their kernels and recoveries and store them in those directories. That would NOT be possible since using the command "flash_image recovery /sdcard/*recovery*.img would flash any img file with the word "recovery" in it. So if there's more than one it would error out and not flash anything because of the conflict. Same principal with the kernel only MOST kernels are simply named "boot.img" where-as almost all recovery files have a unique name since they are all already custom.
Binary100100 said:
Actually, yes! I did add it to the init.d script but since xboarder had removed the init.d scripts from his rom it doesn't work anymore. But you sure could. It was basically how I was setting up my CWMFaux kernels. However it didn't seem to work 100% of the time. Couldn't figure out why.
It basically worked like this...
Flashing the CWM custom kernel .zip via recovery.
copies boot.img to /system
copies init.d 06tweaks script to init.d folder.
copies and set permissions for flash_image binary and kernelupdate script to /system/bin directory.
You then boot your phone up which triggers the init.d script which commands the kernelupdate script to initiate. The kernel update script is simply using the flash_image binary command "flash_image boot /system/boot.img" and it automatically updates the kernel. Then the init.d script removes the boot.img file from the /system directory to keep it from flashing upon every boot.
I would like to change it to /sdcard directory but there's the problem that the sdcard doesn't get mounted until the very end. WAY after the system. Which is why I stored it there. The system gets mounted even before the data partition so I couldn't even store the file in data because the script would run even before the data partition could mount. Basically the script is initiated while your still looking at the boot animation. Pretty much when your softkey backlights and led light comes on it flashes the new kernel. It's a pretty neat workaround if I must say but unfortunately nowhere near perfect and not even close to having an s-off workaround.
Now if you don't mind the fact that it won't be initiated upon boot I could make it so that it will flash any file in a perspective folder on the sdcard.
example:
kernelupdate would update the kernel with any *boot*.img file located in a certain directory... say /sdcard/kernel
recoveryupdate would update the recovery with any *recovery*.img file located in a certain directory... say /sdcard/recovery
The problem:
Some people would want to collect their kernels and recoveries and store them in those directories. That would NOT be possible since using the command "flash_image recovery /sdcard/*recovery*.img would flash any img file with the word "recovery" in it. So if there's more than one it would error out and not flash anything because of the conflict. Same principal with the kernel only MOST kernels are simply named "boot.img" where-as almost all recovery files have a unique name since they are all already custom.
Click to expand...
Click to collapse
quite a dilemma, I wonder if we could add pause to the script until everything is loaded on the first boot then after the pause the script flahes the recovery and more importantly the kernel!!! if this was possible we could keep the files in a separate place on the SD card.
Still nothing like S-off!!! Thanks HTC for being so dev friendly
seansk said:
quite a dilemma, I wonder if we could add pause to the script until everything is loaded on the first boot then after the pause the script flahes the recovery and more importantly the kernel!!! if this was possible we could keep the files in a separate place on the SD card.
Still nothing like S-off!!! Thanks HTC for being so dev friendly
Click to expand...
Click to collapse
I'm sure there's a way to add a delay timer of some sort. I'm just not that savvy. Easiest way would be through an app like Tasker.
DEFINITIONOFREAL said:
Would this be a possible solution to our kernel flashing problems, I know it works for the evo
Sent from my HTC Amaze 4G using XDA App
Click to expand...
Click to collapse
The short answer is yes!
I've setup the application to support the HTC Amaze 4G, but before I release it publically and officially, I want to have a few testers confirm everything is working properly for them.
Posted all the information in a new thread as this one seems to be covering a few different topics so I didn't want to "hijack".
http://forum.xda-developers.com/showthread.php?p=21574722
Thanks for the request and for reaching out to me DEFINITIONOFREAL.
Binary100100 said:
Once I see that they do I can work out something else like:
kernelupdate
recoveryupdate
kernelupdate would be
flash_image boot /sdcard/kernel/*boot*.img
recoveryupdate would be
flash_image recovery /sdcard/recovery/*recovery*.img
So that if you place ANY of the appropriate img file in the perspective folders on the sdcard partition it would flash the .img by just entering either of the two commands from adb shell or terminal.
But I'm not going to waste my time if the devs don't want to use it.
Click to expand...
Click to collapse
I think my application, Flash Image GUI, will be the best alternative, but of course I have a biased opinion!
Regarding alternatives, I think a simple sh script which takes an argument would make a nice wrapper. The argument would be location to the image file to flash. The script could either bundle the flash_image binary or take the location of it as another argument.
All depends on how the developers want to create some type of standard. Which is another great reason Flash Image GUI will work well as it contains everything required and doesn't rely on developers providing support in their ROM, only relys on developers following the standards for ROMs and kernel .zip files.
Also, in looking through some of the custom ROMs and kernel .zip files for this device, I notice one of the custom kernels does something similar to the suggestions above, it executes a file located in /system/etc/init.d on every boot which automatically flashes /system/boot.img file.
At first glance I was horrified to see this as this is a *major* security issue. If anybody were to place any type of file in /system/boot.img, either a rogue kernel or just a blank file, the script automatically flashed it on boot w/o any type of file verification or user notification!
Wanted to get that off my chest and discourage the use of *automatic* loading of any type of major file, such as kernel or recovery image, especially without at least file verification or user approval/notification.
I'll try and keep up with the thread and help contribute ideas to alternatives for anybody who wants to develop/implement! Great ideas in the thread and always enjoy reading community collaboration efforts, especially in resolution to manufacturer "adjustments" of standards.
ugh, sorry about the double post (too excited for being too early in the morning). if a moderator wants to combine my last two posts, please do. i dont have access to delete a post.
joeykrim said:
I think my application, Flash Image GUI, will be the best alternative, but of course I have a biased opinion!
Regarding alternatives, I think a simple sh script which takes an argument would make a nice wrapper. The argument would be location to the image file to flash. The script could either bundle the flash_image binary or take the location of it as another argument.
All depends on how the developers want to create some type of standard. Which is another great reason Flash Image GUI will work well as it contains everything required and doesn't rely on developers providing support in their ROM, only relys on developers following the standards for ROMs and kernel .zip files.
Also, in looking through some of the custom ROMs and kernel .zip files for this device, I notice one of the custom kernels does something similar to the suggestions above, it executes a file located in /system/etc/init.d on every boot which automatically flashes /system/boot.img file.
At first glance I was horrified to see this as this is a *major* security issue. If anybody were to place any type of file in /system/boot.img, either a rogue kernel or just a blank file, the script automatically flashed it on boot w/o any type of file verification or user notification!
Wanted to get that off my chest and discourage the use of *automatic* loading of any type of major file, such as kernel or recovery image, especially without at least file verification or user approval/notification.
I'll try and keep up with the thread and help contribute ideas to alternatives for anybody who wants to develop/implement! Great ideas in the thread and always enjoy reading community collaboration efforts, especially in resolution to manufacturer "adjustments" of standards.
ugh, sorry about the double post (too excited for being too early in the morning). if a moderator wants to combine my last two posts, please do. i dont have access to delete a post.
Click to expand...
Click to collapse
I look forward to tryin out your app.
It was basically what this thread was all about in the first place.
The clockwork method that you mentioned is the only workaround that I was able to come up with for custom kernels (like Faux123) because a kernel cannot be flashed through recovery without s-off. Really stupid. So I started thinking "How can we flash a boot.img file from recovery without the typical means?" Then came up with the solution to flash_image the boot.img file automatically IF the file is detected. But how to start a script automatically upon boot? init.d is the only way I could think of. Okay... so where to put the boot? I tried the sdcard but it failed to mount until it was way too late. So... data. Nope... still didn't mount in time. Cache? Well... how many developers will include a cache file into their roms? So the only other option was /system and it seemed convenient since /system mounts BEFORE the script can run (obviously) so that's why it is as it is. I also figured "If someone wants to flash a new kernel all they need to do is push the boot.img to /system and reboot." Must easier than using the EKF method (requiring PC access) and I don't know about you but I'm not around a computer 24/7.
hi everyone. i got my htc rezound on friday and have been fighting with it most of the weekend. i have the bootloader unlocked and (i assume) root achieved via amon ra. i cant get rid of the bloatware via multiple bloat removal tools, and its starting to make me hate life. can someone just tell me how i get to /system/apps so i can do it myself?
thanks.
Get a root explorer and it will allow you to remove the apks.
EmerikL said:
Get a root explorer and it will allow you to remove the apks.
Click to expand...
Click to collapse
thanks, that was excruciatingly simple. i grabbed an app and apparently perm root didnt take. going to need to try again after work.
im new to all this stuff with phones, i should have learned with my incredible 1 but it was satisfactory out of the box. seems like everything HTC with the newest version is full of bloat and runs like garbage. the last OTA to incredible nearly bricked the phone, i had to manually reprogram it to get back on the network; verizon tech support didnt do jack.
ill keep reading over these forums and learning as much as i can. any suggestions for this phone are greatly appreciated. currently im using the stock sense UI and stock kernel. i like the UI as it is, dont plan on modding it, just need to get rid of bloat.
Madnapali said:
hi everyone. i got my htc rezound on friday and have been fighting with it most of the weekend. i have the bootloader unlocked and (i assume) root achieved via amon ra. i cant get rid of the bloatware via multiple bloat removal tools, and its starting to make me hate life. can someone just tell me how i get to /system/apps so i can do it myself?
thanks.
Click to expand...
Click to collapse
Are you sure you're rooted and unlocked? You did the HTC unlock dance, right?
The reason I ask is that you say you achieved root via Amon Ra.....and Amon Ra doesn't get you root; it's a recovery vehicle/manager. Anyway, have you seen this thread?
HTH
rfarrah said:
Are you sure you're rooted and unlocked? You did the HTC unlock dance, right?
The reason I ask is that you say you achieved root via Amon Ra.....and Amon Ra doesn't get you root; it's a recovery vehicle/manager. Anyway, have you seen this thread?
HTH
Click to expand...
Click to collapse
i cant be sure im rooted, but i am unlocked. i watched the bootloader unlock myself, and it says 'unlocked' at the top of the hboot screen.
i have no idea how to see if i have root, though, and i know i dont right now.
as for that thread, yes, i have all that on my PC at home and tried it earlier today. unfortunately, i had previously used a different method, so i skipped straight up to the part after the unlock. the other method i used had me get into amon ra and use the su installer, which is why i mentioned that.
any other suggestions? im all ears heh.
rfarrah said:
Are you sure you're rooted and unlocked? You did the HTC unlock dance, right?
The reason I ask is that you say you achieved root via Amon Ra.....and Amon Ra doesn't get you root; it's a recovery vehicle/manager. Anyway, have you seen this thread?
HTH
Click to expand...
Click to collapse
No Amon Ra has the functionality to install su. It's been one of the only ways to obtain root after the OTA.
Sent from my ADR6425LVW using xda premium
Madnapali said:
i cant be sure im rooted, but i am unlocked. i watched the bootloader unlock myself, and it says 'unlocked' at the top of the hboot screen.
i have no idea how to see if i have root, though, and i know i dont right now.
as for that thread, yes, i have all that on my PC at home and tried it earlier today. unfortunately, i had previously used a different method, so i skipped straight up to the part after the unlock. the other method i used had me get into amon ra and use the su installer, which is why i mentioned that.
any other suggestions? im all ears heh.
Click to expand...
Click to collapse
Okay, then this: procedure.
if you haven't done this from beginning to end (incl step 7), you may not be perm-rooted. Good luck!
rfarrah said:
Okay, then this: procedure.
if you haven't done this from beginning to end (incl step 7), you may not be perm-rooted. Good luck!
Click to expand...
Click to collapse
actually... i think that is the first method i used LOL. either way, im going to factory reset my phone and go with hasoon2000's tool.
let me preface this by again stating i have the bootloader unlocked and can prove it with a picture if i have to.
ok, i factory reset my phone and used amon ra to install superuser. this did not work.
superuser says 'no apps in list.' ES file explorer tells me i cant delete Blockbuster.apk. terminal emulator says it is read only. after rebooting my phone, terminal emulator's keyboard is stuck in all caps mode (weird) and i cant even cd.
this is what i get when i use hasoon's method (cant post about this there cuz i dont have 10 posts ):
Code:
C:\Rezound_All-In-One_Kit_V1.0\data>adb shell mount /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
C:\Rezound_All-In-One_Kit_V1.0\data>adb push SU/Superuser.apk /system/app
failed to copy 'SU/Superuser.apk' to '/system/app/Superuser.apk': Read-only file
system
C:\Rezound_All-In-One_Kit_V1.0\data>adb push SU/androidterm.apk /system/app
failed to copy 'SU/androidterm.apk' to '/system/app/androidterm.apk': Read-only
file system
C:\Rezound_All-In-One_Kit_V1.0\data>adb push SU/Busybox /system/app
failed to copy 'SU/Busybox' to '/system/app/Busybox': Read-only file system
C:\Rezound_All-In-One_Kit_V1.0\data>adb push SU/Busybox /system/bin
failed to copy 'SU/Busybox' to '/system/bin/Busybox': Read-only file system
C:\Rezound_All-In-One_Kit_V1.0\data>adb push SU/su /system/app
failed to copy 'SU/su' to '/system/app/su': Read-only file system
C:\Rezound_All-In-One_Kit_V1.0\data>adb push SU/su /system/bin
failed to copy 'SU/su' to '/system/bin/su': Read-only file system
C:\Rezound_All-In-One_Kit_V1.0\data>pause
Press any key to continue . . .
Madnapali said:
let me preface this by again stating i have the bootloader unlocked and can prove it with a picture if i have to.
ok, i factory reset my phone and used amon ra to install superuser. this did not work.
superuser says 'no apps in list.' ES file explorer tells me i cant delete Blockbuster.apk. terminal emulator says it is read only. after rebooting my phone, terminal emulator's keyboard is stuck in all caps mode (weird) and i cant even cd.
this is what i get when i use hasoon's method (cant post about this there cuz i dont have 10 posts ):
Code:
C:\Rezound_All-In-One_Kit_V1.0\data>adb shell mount /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
C:\Rezound_All-In-One_Kit_V1.0\data>adb push SU/Superuser.apk /system/app
failed to copy 'SU/Superuser.apk' to '/system/app/Superuser.apk': Read-only file
system
C:\Rezound_All-In-One_Kit_V1.0\data>adb push SU/androidterm.apk /system/app
failed to copy 'SU/androidterm.apk' to '/system/app/androidterm.apk': Read-only
file system
C:\Rezound_All-In-One_Kit_V1.0\data>adb push SU/Busybox /system/app
failed to copy 'SU/Busybox' to '/system/app/Busybox': Read-only file system
C:\Rezound_All-In-One_Kit_V1.0\data>adb push SU/Busybox /system/bin
failed to copy 'SU/Busybox' to '/system/bin/Busybox': Read-only file system
C:\Rezound_All-In-One_Kit_V1.0\data>adb push SU/su /system/app
failed to copy 'SU/su' to '/system/app/su': Read-only file system
C:\Rezound_All-In-One_Kit_V1.0\data>adb push SU/su /system/bin
failed to copy 'SU/su' to '/system/bin/su': Read-only file system
C:\Rezound_All-In-One_Kit_V1.0\data>pause
Press any key to continue . . .
Click to expand...
Click to collapse
You don't have root. Install this by flashing it in Amon Ra, that should give you root. Then rerun the tool.
EmerikL said:
You don't have root. Install this by flashing it in Amon Ra, that should give you root. Then rerun the tool.
Click to expand...
Click to collapse
flashed the zip from amon ra and restarted so hasoon's permroot could run. still says read only file system.
im beginning to think no one has actually rooted the rezound, and this is an elaborate, worldwide prank on me lol.
if your in root explorer you need to press on the read only to change it to read write. Probably the same with any file manager. Default is read only.
Sent from my ADR6425LVW using xda premium
mjh68 said:
if your in root explorer you need to press on the read only to change it to read write. Probably the same with any file manager. Default is read only.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
!!!!!!!!!!!!!!!!!!!!!!!!!!!
you, sir, are the winner of the day. you have earned yourself a lifetime supply of HUGS! lol, thanks much.
ok, its not over yet. i removed a bunch of the .apk files for crapps i dont use, but the shortcuts still exist in the app menu and the processes still run. i verified that the .apk files are still gone.
also, the HTC people widgets are mysteriously gone .
what next?
Madnapali said:
ok, its not over yet. i removed a bunch of the .apk files for crapps i dont use, but the shortcuts still exist in the app menu and the processes still run. i verified that the .apk files are still gone.
also, the HTC people widgets are mysteriously gone .
what next?
Click to expand...
Click to collapse
Have you rebooted after your changes?
I would have used titanium backup first to freeze the apps that I am thinking about removing. And then moving them to a safe place rather than deleting them so that if I have to, I can put them back if there is a bad result.
krelvinaz said:
Have you rebooted after your changes?
I would have used titanium backup first to freeze the apps that I am thinking about removing. And then moving them to a safe place rather than deleting them so that if I have to, I can put them back if there is a bad result.
Click to expand...
Click to collapse
yeah, i rebooted. i dont understand... why would i have to freeze apps and move them? i own the stupid phone, cant i just delete this crap and forget about it?
i swear to god, this is more frustrating than buying a laptop from best buy...
Madnapali said:
yeah, i rebooted. i dont understand... why would i have to freeze apps and move them? i own the stupid phone, cant i just delete this crap and forget about it?
i swear to god, this is more frustrating than buying a laptop from best buy...
Click to expand...
Click to collapse
Simple. If you remove the wrong thing, you may have problems trying to put it back. Without having to reload the ROM again and start over.
Remove the wrong things... and you have a non-working phone.
By freezing them, you can see the affects before you perm remove them. If you move them instead of deleting them, you can put them back. If you delete them, sometimes even TB can't restore them.
It comes down to how much time you want to put into this...
krelvinaz said:
Simple. If you remove the wrong thing, you may have problems trying to put it back. Without having to reload the ROM again and start over.
Remove the wrong things... and you have a non-working phone.
By freezing them, you can see the affects before you perm remove them. If you move them instead of deleting them, you can put them back. If you delete them, sometimes even TB can't restore them.
It comes down to how much time you want to put into this...
Click to expand...
Click to collapse
edit: got it! thanks everyone for responding!
EmerikL said:
You don't have root. Install this by flashing it in Amon Ra, that should give you root. Then rerun the tool.
Click to expand...
Click to collapse
Seems that the AIO Tool's permaroot had problems and this did the trick. Thanks to you and the OP!
I'm trying to get ICS on my dad's phone, but for his company he needs it to be unrooted. The IT dept uses MobileIron which won't install unless the phone is unrooted. I flashed Shostock ROM and am trying to remove root. Now SU is gone, but I'm still able to access root directory using a file explorer. So it seems like the only way to fully unroot is to flash a stock ICS kernel. Where can I get one?
Or maybe someone has experience with MobileIron and can tell me if removing SuperUser is enough? Or does it also check for s-off?
You can extract the zImage from the UCLE5 plus Root tar package that is available in the development section.
You should however, leave the custom kernel on the phone and not install the stock UCLE5 kernel since that would introduce the risk of the eMMC superbrick bug.
Root does not reside within the kernel anyway. It is in the system partition, and since the phone is currently rooted, you can remove the files that make the phone rooted, and when you subsequently reboot the phone, it will no longer be rooted.
You will need to install a root file explorer. There are several available and I think at least one that is free on Google Play is a part of Super Manager 3.0 by Gpc. You can remove the applications after you remove root.
Be sure to remove all of the following before you reboot. You can't do it in steps. There is actually only one su binary and one busybox binary, but the other one of each of those is a symlink.
To remove root from the phone:
/system/app/superuser.apk
/system/bin/su
/system/bin/busybox
/system/xbin/su
/system/xbin/busybox
Thanks a lot. Those files are all gone, so I guess the phone is officially unrooted then. I was just worried since the root directory could still be accessed. I guess I won't be needing that official kernel then.
Thanks again!
mzaur said:
Thanks a lot. Those files are all gone, so I guess the phone is officially unrooted then. I was just worried since the root directory could still be accessed. I guess I won't be needing that official kernel then.
Thanks again!
Click to expand...
Click to collapse
You may be able to look at root in read-only but you won't be able to modify anything without root permissions.
Well, apparently the IT dept couldn't install MobileIron security software on the phone. I did remove all the root files, but I'm guessing it does check for unofficial kernels or something. I guess i'll have to give official ICS a try
mzaur said:
Well, apparently the IT dept couldn't install MobileIron security software on the phone. I did remove all the root files, but I'm guessing it does check for unofficial kernels or something. I guess i'll have to give official ICS a try
Click to expand...
Click to collapse
Not too surprised. You can find the UCLE5 stock firmware in the Download Repository.
Just don't do a wipe with that kernel installed !
Sent from my MB860 using Tapatalk 2