My device: HTC Desire, CM7 RC1, unrevoked root, s-on
As a Chinese mainland user, I need to edit hosts to access certain websites like twitter and wordpress.(And because it seems that cm7 have some problems with vpn and ssh.)
but i tried various method (root explorer, adb, terminal), the only result is that origin hosts file come back after reboot. none of those methods mention s-off, so do I need s-off?
someone said it can be done in recovery mode,but I don't find that function in RA recovery 2.0. someone said it must be done through flashing a zip which contains new hosts file. Are they right?
Thanks
From fastboot (not recovery) without s-off OR with s-off in recovery OR with s-off with most file browsers with phone booted normal.
HTC desire has read only where hosts file reside without s-off
Sent from my HTC Desire using XDA App
From fastboot is new to me and I highly doubt that is true. From recovery means you boot in to recovery and then use a adb shell. This should work.
If it's just about the add blocking I believe this is the flashabel zip.
place the host file you want in system/etc in this zip then flash from recovery, its unsigned so you will have to turn off verification in the options first.
In Recovery you'll have read/write access to /system, regardless of your phone being S-OFF or S-ON. S-OFF is basically the ability to have the same level of access as you would have in Recovery, even when booted.
thanks for the reply. I'll try using adb shell in recovery later
Last night, I downloaded the cm7 nightly 11(cm_bravo_full-11.zip),unzip,edit hosts(\system\etc\hosts), rezip and sign, wipe all data, flash this rom. And hosts file didn't change，still just have one line（127.0.0.1 localhost). how could that possible?
I had the exact same problem but I re-did it all and the file is there with all the entries. However, none of the entries are being blocked. The file format is all right, it's one of the above. Also on CM7 RC1.
------------------------------
- Sent via HTC Desire -
luciffer said:
thanks for the reply. I'll try using adb shell in recovery later
Last night, I downloaded the cm7 nightly 11(cm_bravo_full-11.zip),unzip,edit hosts(\system\etc\hosts), rezip and sign, wipe all data, flash this rom. And hosts file didn't change，still just have one line（127.0.0.1 localhost). how could that possible?
Click to expand...
Click to collapse
Just push it to the correct position after ROM install through Recovery. It'll be there.
------------------------------
- Sent via HTC Desire -
luciffer said:
thanks for the reply. I'll try using adb shell in recovery later
Last night, I downloaded the cm7 nightly 11(cm_bravo_full-11.zip),unzip,edit hosts(\system\etc\hosts), rezip and sign, wipe all data, flash this rom. And hosts file didn't change，still just have one line（127.0.0.1 localhost). how could that possible?
Click to expand...
Click to collapse
Here's how I'd change my hosts file:
1. Boot in recovery, load up adb shell and mount both system and sdcard partitions.
2. Push the hosts file in your sdcard.
3. Remove the old hosts file (and check with ls).
4. Copy the new hosts file (and check with ls).
5. Reboot phone.
6. ???????
7. PROFIT
Related
This guide may be obsolesced shortly, but it's still good reading for the curious. See [UPDATE][HC3.1] Wifi and 3G! Completely Flashable! No Fastboot Needed! No Data Loss. (thanks, bigrushdog)
WARNING: Following this procedure may damage or permamently destroy your device. This procedure is provided with NO WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Perform this procedure at your own risk.
COMPATIBILITY NOTE: I have personally tested this procedure ONLY ON THE US XOOM WIFI MZ604. If other devices (i.e., Euro Xoom WiFi) implement the same Android 3.1 update file, then this procedure *should* work; some users have reported success with UK and Canadian models (see this post for more info). Know, however, that you proceed at your own risk.
AWESOMENESS NOTE: Instead of copying files which you're going to adb push to the platform-tools directory every time, why not just add the directory to your PATH environment variable ("How to update your PATH")? That way, you can run adb from any directory you want.
3G GUINEA PIGS: I've edited the 3G version of the updater_script in the same way as the WiFi, but I don't have a 3G Xoom with which to test. IF YOU ARE FLASHING AND TROUBLESHOOTING SUPASTAH, please try the attached updater-script_UNTESTED_Xoom3G_Android3.1_Root_v03.zip(Updated!) with the MZ600 HRI66 stock images and Xoom 3G 3.1 Update ZIP. If it works, I'll update the guide to cover both devices. Please PM me your feedback, since a post might be easily buried in this thread. Thanks!
[size=+1]SUMMARY[/size]
Here's a run-down on the current procedure:
Updates the Xoom WiFi to Android 3.1 using ClockworkMod Recovery (update.zip)
Resolves issue in updater-script: get_prop ro.product.device wingray
Sets correct permission on su to enable functioning root
Flashes the recovery (version 03 persists CWM Recovery), boot (kernel), and system partitions to stock (required at this time)
Stock kernel means no SD Card in Honeycomb (still available in recovery), no overclocking until devs release 3.1 compatible kernels
Updates bootloader to include Recovery in the boot menu
Leaves user data intact
Outstanding Issues:
(FIXED in updater_script version 03) Recovery partition gets overwritten to stock on reboot: Edit updater-script to leave recovery partition intact
Too many steps: Include the edited updater-script, su, Superuser.apk in the update.zip
Now, without further ado...
[size=+1]ASSUMPTIONS[/size]
You've downloaded the Xoom WiFi Android 3.1 update from Google (thanks, pof)
You've downloaded and unzipped the stock Xoom WiFi MZ604 HWI69 images from Motorola
You've downloaded su and Superuser.apk (see WiFi Xoom Root Zip link at Xoom WiFi (MZ604) Root!!)
You've flashed a boot.img that enables adb remount (Xoom WiFi (MZ604) Root!!, custom kernels, etc.)
You've flashed ClockworkMod Recovery (thanks, bigrushdog, koush, et al)
You've installed a physical SDCard in your Xoom (required for ClockworkMod Recovery updates) and have it functioning properly
You've configured the Android SDK on your PC, with adb functioning properly
You've downloaded fastboot and have it functioning properly (usually alongside adb in platform-tools)
You've installed an archive program that lets you edit the contents of an existing ZIP file (7-Zip, WinRAR, etc.)
You've downloaded and unzipped the edited updater_script file attached to this post
[size=+1]PROCEDURE[/size]
Prepare the Android 3.1 Update file
The update file as-provided is not ready for use in ClockworkMod Recovery. This fixes it. I could just include a link to a prepared update.zip file, but this is safer than trusting some dude with less than 20 posts on XDA. I'll upload one when I hit 25.
Rename the Android 3.1 Update file to update.zip
Open the zip file in an archive program for editing
Navigate to the following directory: META-INF/com/google/android
Delete the following file: updater-script
Copy the updater-script file from the ZIP file attached to this post to META-INF/com/google/android
Flash stock system.img
Prior to performing the actual update, the update script checks a number of files (including bcm4329.ko, which is usually built with the kernel) in /system. If any file doesn't match what's expected, the update halts. Flashing the stock system.img ensures a smooth update.
Code:
adb reboot bootloader
fastboot flash system system.img
fastboot reboot
Reconfigure superuser
After flashing stock, we no longer have superuser/root access on our Xoom. By pushing and configuring these files, we restore our root capability without interfering with the pre-update checks. (thanks, Berzerker for catching missing symlink)
Code:
adb remount
adb push su /system/bin/
adb shell chown root.shell /system/bin/su
adb shell chmod 4755 /system/bin/su
adb shell ln -s /system/bin/su /system/xbin/su
adb push Superuser.apk /system/app/
adb shell chmod 644 /system/app/Superuser.apk
Flash stock boot.img
The pre-update checks also include the boot partition. We wait until now to flash the boot partition to stock because we need to perform adb remount earlier in the procedure, which we can't do with the stock boot.img. The actual update flashes this partition with a new kernel that implements the new 3.1 features.
Code:
adb reboot bootloader
fastboot flash boot boot.img
fastboot reboot
Perform update
Code:
adb reboot recovery
Note that in recovery, you use the hardware volume buttons to navigate up and down, and the power button to select.
In ClockworkMod Recovery, select "mounts and storage"
Ensure your Xoom is connected to your PC via USB, then select "mount USB storage"
On your PC, copy update.zip to the root of the Xoom's SDCard ("Removable Disk" in Windows)
In ClockworkModRecovery (still on the "USB Mass Storage device" screen) select "Unmount"
In the "Mounts and Storage Menu" screen, if the option "unmount /sdcard" is present, continue to the next step; if "mount /sdcard" is present, select it then continue
Select "+++++Go Back+++++"
Select "apply update from sdcard"
Select "Yes - Install /sdcard/update.zip"
"Install from sdcard complete." will indicate that the update is completed.
.
Select "reboot system now"
New bootloader will install. The message, "Congratulation! Your bootloader was successfully upgraded" will be immediately followed by an automatic reboot.
Enjoy your rooted Xoom WiFi, running on Android 3.1!
[size=+1]POST-UPDATE NOTES[/size]
Custom kernels: As of 0730 11 May 2011, there are no kernels/boot.img that are compatible with the Android 3.1 update, though the devs are undoubtedly on it. Do not flash a custom kernel after performing this procedure unless you know that it's compatible with the 3.1 update.
Recovery: updater_script v03 no longer flashes stock recovery. If you ran a previous version of the update, please see this post by Berzerker on getting ClockworkMod Recovery to persist (thanks, Berzerker)
NICE! Will be trying this out shortly.
trying it now.... will give feedback
Can someone confirm the filesize and md5 of the update zip file? (the actual update.zip, not the updater-script)
Do I need to be using the stock kernal before I start?
good post.... cant wait to try this when I get home.
here's the official update link for wifi xoom:
http://android.clients.google.com/p...signed-tervigon-HMJ37-from-HWI69.e379f0b9.zip
just one quick question why is it US only ? don't you think it should work on wifi only euro too ?
pof said:
here's the official update link for wifi xoom:
http://android.clients.google.com/p...signed-tervigon-HMJ37-from-HWI69.e379f0b9.zip
Click to expand...
Click to collapse
Yes, but the official update won't flash in ClockwordMod Recovery unless it is modified, like the one in the OP of this thread. Posting the official version on this thread just adds to the confusion.
publicanimal said:
Yes, but the official update won't flash in ClockwordMod Recovery unless it is modified, like the one in the OP of this thread. Posting the official version on this thread just adds to the confusion.
Click to expand...
Click to collapse
All he posted in the OP was a modified script, you still need to get the update.zip from Google.
The Google server is much much faster than the 3rd party download sites too.
le_pere_noel said:
just one quick question why is it US only ? don't you think it should work on wifi only euro too ?
Click to expand...
Click to collapse
Only because I don't have a test device. I'll update the post.
Just got done with this procedure, and it works perfectly.
I'm rooted on 3.1 on my WiFi Xoom.
Thanks OP!
stachre said:
[*]Flash stock system.img
Code:
adb reboot bootloader
fastboot flash system.img
fastboot reboot
Click to expand...
Click to collapse
fastboot flash system system.img
tony710 said:
All he posted in the OP was a modified script, you still need to get the update.zip from Google.
The Google server is much much faster than the 3rd party download sites too.
Click to expand...
Click to collapse
Ah my bad, I only saw the .zip at the end of the filename
Anyone know if this works in Canada?
tony710 said:
Just got done with this procedure, and it works perfectly.
I'm rooted on 3.1 on my WiFi Xoom.
Thanks OP!
Click to expand...
Click to collapse
So, maybe a stupid question, but did you have Tiamat kernel installed? Just wondering if that makes a difference. Thanks!
-edit- plus, will this wipe all userdata??
were do we find a boot.img that enables adb remount?
Thanks man! Can't wait to give this a try when I get home!
One general question though, what program do you guys use to edit the update.zip?
Thanks in advance for the help fellas!
Peace
Dan
mbroeders said:
So, maybe a stupid question, but did you have Tiamat kernel installed? Just wondering if that makes a difference. Thanks!
-edit- plus, will this wipe all userdata??
Click to expand...
Click to collapse
Yeah, I had Tiamat installed and all my userdata stayed.
I'm currently trying to see if I can flash the latest Tiamet back to see what happens.
dowenprs said:
Thanks man! Can't wait to give this a try when I get home!
One general question though, what program do you guys use to edit the update.zip?
Thanks in advance for the help fellas!
Peace
Dan
Click to expand...
Click to collapse
I used 7z to edit the zip file
Hey Guys,
So I've been playing around with SDK using adb commands.
I been successful replacing stock ROM with a custom ROM.
Rooting and Unrooting.
Semi-bricking and getting it back.
Extracting a ROM file from an RUU and flashing it successfully.
Problem: the closest I can get to stock is a stock system with clockwork mod recovery flashed. Or Android system 3e recovery with the Superuser app installed on the system.
I've read posts that say to mount the system/ folder using
mount /system, mount -o remount, rw system/ , etc
all give me permission denied when I: rm /system/app/Superuser.apk
I've read that you must be recovery mode to mount system/ folder but when in recovery mode I cannot get connected with running: adb shell. error device not found.
So can anyone help me either remove Superuser.apk from my system/app folder or flash "Android recovery system 3e" without Superuser being installed?
I wish there was an RUU for Bell Mobility 1.34.666.5 floating around.
Thanks guys
HTC Vision
1.34.666.5
I'm driving and just skimmed through your post, but have you installed a pc10img through the booatloader? That is suppost to bring everything back to stock.
Sent from my HTC Vision using XDA Premium App
I did try using a PC10IMG.zip file using bootloader. But the only PC10IMG file that I could find was software version 1.34.666.1. I actually used this method to recover from a semi-brick state. (phone would not move past HTC boot screen)
I tried replacing the system.img file from the PC10IMG.zip that worked. But I believe that having S-ON prevented the new PC10IMG file to proceed. Which was probably a good thing as substituting the system.img file probably wasn't smart.
I've read that flash PC10IMG files with S-OFF is risky. If this is my best option. Can anyone give me a heads up as to what to double check for?
Thanks again for anyones input.
did you try this?http://forum.xda-developers.com/showthread.php?t=835971
Thanks for your reply.
Not sure this will help. If I had the files that corresponds to a
Bell Mobility 1.34.666.5 Stock Factory Bootloader / Recovery / ROM / Kernel I could get it no problem.
The hex editor I believe would be something new for me to try. But I believe this would only help if I am trying to apply software that is older then the software currently installed. This is not the case here.
Has anyone ever used clockwork mod recovery files to make a working PC10IMG.zip file that I could flash at startup using hboot?
I think you need to downgrade use the hex editor n flash the PC10Img
Sent from my SGH-T959 using XDA Premium App
Flashed my own PC10IMG.zip file with the new system.img file inserted. Only had to have S-OFF to do.
Unfortunately, this did not work. Phone boots to HTC screen and freezes.
Back to my original problem. Anyway to remove Clockwork recovery without installing Superuser.apk. or Anyway to uninstall Superuser.apk
I do not know why you say this...
MOD EDIT: Rooters beware. Proceed with extreme caution, as these are highly uncharted waters.
Hi,
I am here to provide you a new method in rooting your xoom, it does not require to flash the decrypted boot.img image.
I have tried it only on my Wifi XOOM, which is a UK version. (With a Japan version of ROM, downloaded from Motodev and upgrade to 3.1)
***EDIT***
I have also tried on a HK 3g xoom (which shows MZ601 in MTP but MZ602 in fastboot). It works without any problem, and internal storage preserved untouched.
===============================================================
I am NOT a xoom developer, nor a rom cook. I am just a user of xoom, which know
a little on developing and are willing to try new things.
So, I can not be sure that the method below works on your device. By following the
things below, your xoom may have a chance to brick.
I am not responsible for any brick or mulfunction device.
===============================================================
To root your xoom, you should start with flashing your device with the clockworkmod recovery (Please refer to the post by solarnz).
After flashing the clockworkmod recovery, do the following.
1. Download the attached ROOT.zip, place it on the root directory of the external sd card, and rename it to update.zip
2. Restart your device to the recovery by:
Type "adb reboot recovery" from your pc
OR press volumn down ~2 seconds after the motorola logo appears when the device starts,
then volumn up when "-->Android recovery" appears.
3. Apply the update in the recovery.
That's it. Your device should be already rooted.
=======================================================================
I am not the inventor of the method, I think about this since I have a Samsung i9000,
and the method of rooting the i9000 is by applying a update.zip file.
I have created the ROOT.zip file by changing the i9000 root zip file with the newer su and superuser.apk (From here: http://forum.xda-developers.com/showthread.php?t=1010568)
I have also changed the updater-script in order to let the updater mount the correct partition for the update.
I am not sure if this update applies to other devices (especially for the 3g ones). This should work if the system partition have name "/dev/block/platform/sdhci-tegra.3/by-name/system".
I would like to thank solarnz for providing the clockmodwork recovery for xoom,
the one who invented the method of rooting the i9000 with a update.zip (I cannot find who make that, sorry...),
and also Xaositek for providing the su and superuser.apk files (I am too lazy to find it by myself...).
========================================================================
That's all. Please try on your device (especially for those stock 3.2) if you would like to take some risk, and report if it is success or not.
Thanks.
eddielo said:
Hi,
I am here to provide you a new method in rooting your xoom, it does not require to flash the decrypted boot.img image.
I have tried it only on my Wifi XOOM, which is a UK version. (With a Japan version of ROM, downloaded from Motodev and upgrade to 3.1)
===============================================================
I am NOT a xoom developer, nor a rom cook. I am just a user of xoom, which know
a little on developing and are willing to try new things.
So, I can not be sure that the method below works on your device. By following the
things below, your xoom may have a chance to brick.
I am not responsible for any brick or mulfunction device.
===============================================================
To root your xoom, you should start with flashing your device with the clockworkmod recovery (Please refer to the post by solarnz).
After flashing the clockworkmod recovery, do the following.
1. Download the attached ROOT.zip, place it on the root directory of the external sd card, and rename it to update.zip
2. Restart your device to the recovery by:
Type "adb reboot recovery" from your pc
OR press volumn down ~2 seconds after the motorola logo appears when the device starts,
then volumn up when "-->Android recovery" appears.
3. Apply the update in the recovery.
That's it. Your device should be already rooted.
=======================================================================
I am not the inventor of the method, I think about this since I have a Samsung i9000,
and the method of rooting the i9000 is by applying a update.zip file.
I have created the ROOT.zip file by changing the i9000 root zip file with the newer su and superuser.apk (From here: http://forum.xda-developers.com/showthread.php?t=1010568)
I have also changed the updater-script in order to let the updater mount the correct partition for the update.
I am not sure if this update applies to other devices (especially for the 3g ones). This should work if the system partition have name "/dev/block/platform/sdhci-tegra.3/by-name/system".
I would like to thank solarnz for providing the clockmodwork recovery for xoom,
the one who invented the method of rooting the i9000 with a update.zip (I cannot find who make that, sorry...),
and also Xaositek for providing the su and superuser.apk files (I am too lazy to find it by myself...).
========================================================================
That's all. Please try on your device (especially for those stock 3.2) if you would like to take some risk, and report if it is success or not.
Thanks.
Click to expand...
Click to collapse
How do you flash cwm if your device if locked? Also the purpose of the rooted boot.img is to allow you to mount your device for adb commands.
Sent from my PG86100 using Tapatalk
yeah no offense but this sounds a little sketch... I see you make a quote at the bottom asking people to report success if they try... I personally would not try this.
Unlocking and rooting is really not that hard and not very time consuming using current methods
Of course, for installing CWM, you have to unlock your device by using "fastboot oem unlock", but that will not brick your device anyway.
For this method, you do not need to issue adb commands to root your device, so no need to have a modified boot.img.
Also, for the current rooting methods, it is not 100% work on some device (like the HK 3g version, which reported missing of internal storage after rooting with currently available method), I would like to see if this work on that.
Rooters beware. Proceed with extreme caution, as these are highly uncharted waters.
eddielo said:
For this method, you do not need to issue adb commands to root your device, so no need to have a modified boot.img.
Click to expand...
Click to collapse
I think you missed my point. Rooted boot.img isn't used for rooting. Its used for adb commands like adb remount. Say i want to adb push a file to my xoom, ls a directory on my xoom, or adb rename system files. Those are all reason you need the rooted boot.img.
Sorry, this is not a rooting method. All what this is doing is flashing su, busybox and Superuser.apk.
There is more to rooting a device than this. You also need an insecure boot image.
I am sorry if I do not catch the real meaning of rooting a device.
What I think of rooting is to let my device, starting from everything stock, untouched, to a state that applications that need root, like Titanium backup or root explorer, works without problem.
I have tried on my two devices with this method, titanium backup works perfectly, root explorer can remount the system partition to rw and can successfully copy files and delete files from that.
The insecure boot.img image, as far as I know, provides everyone to use "adb remount" and make changes to the system directory. But my method do not need adb in copying the binaries and chmod them. You may call it flashing, but after that, su works without problem.
Please, try it first. If you think it is not a method of rooting, I am sorry about that.
Actually guys, don't dismiss him just yet, over in the Galaxy S II forums we only flash insecured images long enough to root the OS then flash back to a secure one, so you have root access but no remount or system r/w.
It's a (fairly) legitimate method and is exactly how I rooted my xoom this time round, well not exactly, I did it like this:
unlock
flash solarnz CWM
adb mount system r/w
push su and busybox
reboot
install superuser from market
done
This is how most people run their GSII and means you can use root apps but no insecure boot image (because the GSII shows a warning on every boot with insecure images and keeps a binary flash counter, cheeky samsung).
This will at least get you to the point where you can su from within android and dump your boot image to modify it yourself, which is what I just did to update my Euro 3G root guide.
So does this mean just "rooted".....like can't flash a rom?
Sent from my Xoom using XDA Premium App
roughneckboren said:
So does this mean just "rooted".....like can't flash a rom?
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
Rooting has nothing to do with installing a rom. To install a rom, you just need to unlock and fastboot flash CWM. This guide in noway helps you flash a rom.
alias_neo said:
Actually guys, don't dismiss him just yet, over in the Galaxy S II forums we only flash insecured images long enough to root the OS then flash back to a secure one, so you have root access but no remount or system r/w.
It's a (fairly) legitimate method and is exactly how I rooted my xoom this time round, well not exactly, I did it like this:
unlock
flash solarnz CWM
adb mount system r/w
push su and busybox
reboot
install superuser from market
done
This is how most people run their GSII and means you can use root apps but no insecure boot image (because the GSII shows a warning on every boot with insecure images and keeps a binary flash counter, cheeky samsung).
This will at least get you to the point where you can su from within android and dump your boot image to modify it yourself, which is what I just did to update my Euro 3G root guide.
Click to expand...
Click to collapse
Without an rooted boot.img your recovery will get wiped out every time you boot the OS.
So will this let you make a titanium backup of your data? That way you could recover your data after using the regular unlock method that erases everything?
silvinoa said:
So will this let you make a titanium backup of your data? That way you could recover your data after using the regular unlock method that erases everything?
Click to expand...
Click to collapse
Yes and NO...
Yes this method will allow you to run titanium backup. But to use this method you have to unlock, which erases everything.
I edited a configuration file for Bluetooth(main.conf) in which i changed the device discoverable for value to be 0 (by default 120). then i left the folder as is (r/w) mode and saves and rebooted.
rescue mode is available(volume up - home -power)
boot loops continously
Kies not recognising when connecting when the device is turned off
there is a backup of the file at the same folder..
if you can provide me too ..how do i upload to my phone.
need help ASAP.
try installing firmware with odin
Other better ideas!
I am pretty sure that this matter was triggered because of that tweak..(editing of the file). I hope that restoring the original file would help.
Do you know about adb...?
Also i forgot where the actual bluetooth configurations file was in the root folder structure
adb will not work on device in recovery/download mode
to use adb mobile needs to be running
you can flash cwm in your mobile then upload the file and send me the link i will make a flashable zip and upload it then you can flash it
adb is running...just
Adb is running (while the phone keeps on showing boot animation-samsung logo-bootanimation-samsung logo-bootanima....) but it seems that it has permissions issues..i unrooted my phone before using adb .
i can access adb shell and list root directories but cannot enter further directories such as data\ permission denied
I donot have the file that i changed and quiet cannot remember it..
Check on your mobile and see for
data/misc/bluetoothd/
if it has files such as music.conf,main.conf etc etc..then this is the needed folder..
can you create a update.zip
like i used for rooting/ unrooting .that doesnt need CWM
that empties the directory ,because it has some backup files .bak created by root explorer
loads files from your mobile
i am currently unrooted ..do i need root?
actually adb works during splashscreen
get the original file and push it through the system, set permission and it should work
if all else fails,..... odin
download update.zip from http://dl.xda-developers.com/attach...5498d4d803e6a/4fcc0dd2/7/6/3/0/8/8/update.zip and place it in the root of your sdcard
go to recovery flash it you will get root then you can use adb
if it is not flashing first flash cwm through Odin then flash this update.zip through cwm
The file you sent is invalid. corrupt..?
what does this do..exactly.
i already have a update.zip and update-unroot.zip to root unroot my device
so
do i need root permission to use adb..because commands like
adb root gives"error not available in production devices"
&
adb shell
$ su
etc are showing permission denied.
if you have the original files on your galaxy y.. can you make update.zip with the above instruction
if adb works..i dont exactly remember the file path that i changed..so using the hints above please can you send me the file path
My aim here is to use odin or factory reset only at the last.
just root the device by flashing the root.zip in recovery and then use
adb shell
su
and it will work
No still get permission denied.... like always.
cd data
ls
open directory failed, Permission denied.
1. flash cwm recovery through odin
2. then upload the original file
3. I will create a update.zip and will upload it
4. you will need to flash it in cwm recovery
i will flash CWM using cwm.zip
i dont have the original file as i could not pull through adb..i hope your file may work
Finally i remembered the directory
/etc/bluetooth
the file i modified was main.conf however whole folder can be replaced from your mobile's or original one.
Thanks
y2k2r2d2 said:
i will flash CWM using cwm.zip
i dont have the original file as i could not pull through adb..i hope your file may work
Finally i remembered the directory
/etc/bluetooth
the file i modified was main.conf however whole folder can be replaced from your mobile's or original one.
Thanks
Click to expand...
Click to collapse
http://db.tt/2NStXBF8
flash it in recovery but it may not work as I don't have galaxy y I have a different mobile
it didnt allow installation both through cwm and recovery mode
& now
i messed up with CWM
backup-restore feature
create backup
edited the system.tar
put the original file
calculated md5 for new system,tar
edited the nandroid.md5 with appropriate editor and filled with the new calculated md5 of system.tar
advance restoore....select system files...
md5 check pass
restore fail
now boot stuck at initial screen
pretty sure even wipe data wont work
So i Had to resort to ODIN..Thanks for your time mate...
humm
I also think Odin is the last choice
Anyone know of a way to disable the boot sound? Having just recently rooted, installed TWRP, Xposed, and doing a few other things it's already driving me crazy. Searching has gotten me nowhere, with links being mostly about BoomSound, or boot animations.
I don't know if its the same for the M8, but here is how to do it for M7....
http://forum.xda-developers.com/showthread.php?t=2443825
mm79k said:
I don't know if its the same for the M8, but here is how to do it for M7....
http://forum.xda-developers.com/showthread.php?t=2443825
Click to expand...
Click to collapse
Thanks so much, fixed it for me. Now I can start rebooting it where needed at uni.
At last ... silence !!!
I got my M8 yesterday and have root with S-ON. (The link says on did this with S-ON) I've have renamed the mp3-file and also tried to edit the default.xml file.
In both cases the phone reboot istself and reverts any change I have made.
So I beleive I need S-OFF, even one said in the link he did this mod with S-ON?
@fasst
I believe with the M8 you have to be s-off or install this in order for any changes you make to /system stick after reboot.
fasst said:
I got my M8 yesterday and have root with S-ON. (The link says on did this with S-ON) I've have renamed the mp3-file and also tried to edit the default.xml file.
In both cases the phone reboot istself and reverts any change I have made.
So I beleive I need S-OFF, even one said in the link he did this mod with S-ON?
Click to expand...
Click to collapse
TWRP recovery :
boot to recovery - select Mount and mount system
select Advanced - select File Manager - browse to system/customize/resource and select the HTC_Sense5_Boot.mp3 then you have option to delete it or to rename it
done then reboot, it should work for S-On device
fasst said:
I got my M8 yesterday and have root with S-ON. (The link says on did this with S-ON) I've have renamed the mp3-file and also tried to edit the default.xml file.
In both cases the phone reboot istself and reverts any change I have made.
So I beleive I need S-OFF, even one said in the link he did this mod with S-ON?
Click to expand...
Click to collapse
I forgot if SOFF is required; but, you need to remount RW; so, either do
http://forum.xda-developers.com/showthread.php?t=2701816
or, make the change from recovery.
If phone reboots itself, it's an other issue. If just the module was missing, then, then change would be canceled after reboot, but after manual reboot.
Auto-reboot on write means you have an other issue. For me, it was that the file system was corrupted. I needed to run fsck on /system; it was not included in my ROM. A friend build it for me. Fsck found errors, fixed them, and them, i had no more reboot on write.
I will upload fsck on the thread about the module in a few days.
Works great! As I am rooted, I just used ES File Explorer to go to system/customize/resource and I renamed HTC_Sense5_Boot.mp3 to HTC_Sense5_Boot.mp3.Silent Works like a charm. Thanks!