Last updated 2/28/2011
This is a pure stock rom with root+hsupa+sideload.
Warning: the following steps to flash the rom will wipe your data.
- Use HTC Inspire Hack Kit or some other way to get S-off so that you can flash custom roms.
- Download the rom, rename it to PD98IMG.zip, put it to the sdcard.
- Go to Settings -> Applications, turn off fast boot and then power down the phone.
- Boot into hboot by pressing volume down + power button and flash.
After flashing you should have a pure stock rom rooted, with hsupa on, and sideloading as an option. I don't have any problem with this rom while I got superuser permission, sideloading back on and noticed a higher upload speed.
Some people report to have problem with ClockWorkMod recovery on the stock rom. You can try the suggestion from this thread.
Link for the ROM: http://www.multiupload.com/93I04ACXYU
--------------------------------
Below are the steps that I took to made this rom, you can ignore it if you are not interested into know how to cook system.img or hack a rom.
I basically added the root files to the system.img and change ro.ril.hsxpa=1 inside of the build.prop file to ro.ril.hsxpa=3 to make hsupa work, edit the customize/CID/default.xml file and change <item name="unknown_sources_visibility">false</item> to <item name="unknown_sources_visibility">true</item> to enable the sideloading option in settings, no need to flash any custom radio or kernel.
Here's how to do it:
- Download the RUU for the stock rom.
- Open the RUU you downloaded, wait for the screen that says Welcome to the Rom Update Utility to come out, but don't flash yet!
- Navigate to the temporary folder and locate rom.zip, which is a file that the installer extracted. I found it by navigating the folder with the most recent Date modified.
- Copy rom.zip to some other folder. This is the zip file which you can use on the phone to flash back to stock.
- Extract android-info.txt and system.img from rom.zip and put system.img in a place where Linux can access.
Right now for the cooking part linux is required. I used Ubuntu to do it.
Code:
sudo mkdir /mnt/system
sudo mount -o loop,norelatime /path to/system.img /mnt/system
Code:
nano /mnt/system/build.prop
update ro.ril.hsxpa to 3 to enable hsupa
You also need the root files busybox, su, and Superuser.apk, which can be found at ace-hack-kit-v002/tools/root
Code:
sudo
cp /path to root files/busybox /mnt/system/xbin/busybox
chmod 4755 /mnt/system/xbin/busybox
cp /path to root files/Superuser.apk /mnt/system/app/Superuser.apk
chmod 644 /mnt/system/app/Superuser.apk
cp /path to root files/su /mnt/system/bin/su
chmod 4755 /mnt/system/bin/su
nano /mnt/system/customize/CID/default.xml
(update <item name="unknown_sources_visibility">false</item> to <item name="unknown_sources_visibility">true</item> to enable the sideloading option in the menu.)
umount /mnt/system
Right now you have a cooked system.img
- extract all files from rom.zip, replace system.img with the one we just cooked, then put all the files back to a new zip named PD98IMG.zip.
--------------------------------
Couldn't you post your cooked PD98IMG.zip for us? Shouldn't it work for all Inspire devices if it was taken from the official RUU?
it is very big, hold down. The phone needs to be S-off first in order to flash.
angelchen1111 said:
it is very big, hold down. The phone needs to be S-off first in order to flash.
Click to expand...
Click to collapse
Yeah... but you should still be able to post it. That would be a WHOLE lot easier than every one of us making the exact same file when we could just flash the one you made. Make sense?
If you want to share, try uploading it to multiupload.com
Pre-rooted stock system.img
File name: PD98IMG.zip File size: 242.81 MB
More links
have fun
Here's the link [removed]. Revert back to stock after being S-off to flash it. Also flashing system.img seem to factory reset the phone, so back up your data inside of your phone if any before flashing.
I just tried it and it did give me root access. Upload speeds are still crappy for me. It was worth the time just for root access. Thanks!
so let me ask a question. If someone were to use temp root with say visionary, can S-off be set from there without a gold card?
angelchen1111 said:
I found a way to enable hsupa and root the phone on the stock rom by "cooking" system.img from the stock rom and flash it over after the phone has been S-off and returned to stock.
I basically added the root files to the system.img and change ro.ril.hsxpa=1 inside of the build.prop file to ro.ril.hsxpa=3 to make hsupa work, no need to flash any custom radio or kernel.
Here's how to did it (this still looks kind like rough draft, I don't know if someone can help me to edit this to make it better or if I can put it up to wiki):
- use HTC Inspire Hack Kit or some other way to get S-off so that you can flash custom roms.
- Download the RUU for the stock rom.
- Open the RUU you downloaded, wait for the screen that says Welcome to the Rom Update Utility to come out, but don't flash yet!
- Navigate to the temporary folder and locate rom.zip, which is a file that the installer extracted. I found it by navigating the folder with the most recent Date modified.
- Copy rom.zip to some other folder. This is the zip file which you can use on the phone to flash back to stock.
- After done copying rom.zip proceed with RUU to flash back to stock.
- Extract android-info.txt and system.img from rom.zip and put system.img in a place where Linux can access.
Right now for the cooking part linux is required. I used Ubuntu to do it.
Code:
sudo mkdir /mnt/system
sudo mount -o loop,norelatime /path to/system.img /mnt/system
use an editor to edit /mnt/system/build.prop and update ro.ril.hsxpa to 3 to enable hsupa
You also need the root files busybox, su, and Superuser.apk, which can be found at ace-hack-kit-v002/tools/root
Code:
sudo
cp /path to root files/busybox /mnt/system/xbin/busybox
chmod 4755 /mnt/system/xbin/busybox
cp /path to root files/Superuser.apk /mnt/system/app/Superuser.apk
chmod 644 /mnt/system/app/Superuser.apk
cp /path to root files/su /mnt/system/bin/su
chmod 4755 /mnt/system/bin/su
umount /mnt/system
Right now you have a cooked system.img
put android-info.txt and the cooked system.img to a zip named PD98IMG.zip and put it to the sd card.
boot into hboot by pressing volume down and power button and flash.
After flashing you should have a pure stock rom rooted and with hsupa on. I don't have any problem with this rom while I got superuser permission and noticed a higher upload speed.
Click to expand...
Click to collapse
The install was fine and i have not had any fc yet. the only problem that i have is that i cant install non market apps. any suggestions on how to allow restore from titanium backup?
farmercyst said:
The install was fine and i have not had any fc yet. the only problem that i have is that i cant install non market apps. any suggestions on how to allow restore from titanium backup?
Click to expand...
Click to collapse
Once it is rooted, it is trivial to enable sideloading.
Code:
adb shell
su
busybox cp /data/data/com.android.providers.settings/databases/settings.db /sdcard/settings.db
exit
exit
adb pull /sdcard/settings.db settings.db
echo update secure set value = 1 where name = 'install_non_market_apps';|sqlite3 settings.db
adb push settings.db /sdcard/settings.db
adb shell
su
busybox cp /sdcard/settings.db /data/data/com.android.providers.settings/databases/settings.db
chown system.system /data/data/com.android.providers.settings/databases/settings.db
chmod 660 /data/data/com.android.providers.settings/databases/settings.db
exit
exit
After thar reboot and you should have sideloading
if it says command not found, try to append busybox in front of the commands.
thanks a lot. stock with root and sideloading is what i have been wanting.
Guess I will be going this route in the meantime as well. Can't handle the "tinny" audio in DHD ROMs.
Sent from my Desire HD using XDA App
So with the way you have this setup as of right now, it only works with a computer running the Linux OS?
Sent from my Inspire 4G.
slapdaddy said:
So with the way you have this setup as of right now, it only works with a computer running the Linux OS?
Sent from my Inspire 4G.
Click to expand...
Click to collapse
You need Linux to open the system.img in order to cook.
angelchen1111 said:
Once it is rooted, it is trivial to enable sideloading.
Code:
adb shell
su
cp /data/data/com.android.providers.settings/databases/settings.db /sdcard/settings.db
exit
exit
adb pull /sdcard/settings.db settings.db
echo update secure set value = 1 where name = 'install_non_market_apps';|sqlite3 settings.db
adb push settings.db /sdcard/settings.db
adb shell
su
cp /sdcard/settings.db /data/data/com.android.providers.settings/databases/settings.db
chmod 666 /data/data/com.android.providers.settings/databases/settings.db
chown system.system /data/data/com.android.providers.settings/databases/settings.db
After thar reboot and you should have sideloading
if it says command not found, try to append busybox in front of the commands.
Click to expand...
Click to collapse
After "cp /data/data/com.android.providers.settings/databases/settings.db /sdcard/settings.db", I get "cp: not found".
after using this method getting everything setup I ran across one issue so far
ROM manager "clockworkmod" issue ,,when rebooting into recovery, screen freaks out white then fading to black ,wait for a while & nothing ,hit power button phone reboots like nothing happend.
How is this done with the file that I'm downloading? The "cooked" file
how do you boot into hboot?
i wish you guys would enlighten me! I guess it's hard for a noob to get any help! Maybe I should just go back to modmyi and be a snob.
Related
This method we will use nandroid's recovery option in ClockworkMod
Requirements:
Rooted myTouch 3G 1.2 with USB Debugging
ClockworkMod Recovery Installed (can be install from ROM Manager)
Universal Androot apk saved to your AndroidSDK tools folder
(I will be doing this in adb)
Create the recovery folders
Code:
mkdir /sdcard/clockworkmod
mkdir /sdcard/clockworkmod/backup
mkdir /sdcard/clockworkmod/backup/Stock
Mount the SD card so you can access it on your computer.
Now extract SAPPIMG_Sapphire_T-Mobile_US_2.10.531.4_release_signed.zip (from shipped-roms) [FYI: I had to use 7zip for this] into clockworkmod/backup/Stock.
Now we are down with that unmount it and return to adb.
Once your phone has remounted the SD card do:
Code:
cd /sdcard/clockworkmod/backup/stock
md5sum * > nandroid.md5
cd ../../../
cat /system/bin/flash_image > flash_image
(If you do not have flash_image post here in this thread and I will pm you a link to it)
Reboot the phone and boot into recovery mode (hold home when powering on)
Once in there
**DO A FULL WIPE**
then restore the "Stock" backup from the restore menu,
It should get past boot and system then fail on /data THIS IS NORMAL
It is not safe to reboot your phone
Set up your phone and all that good stuff, then re-enable adb debugging.
in a command prompt cd to your androidsdk/tools folder and run
Code:
adb install UniversialAndroot.apk
and reroot your phone (bare with me)
once that is done do
Code:
adb shell
su
be sure to click allow on the Superuser Permission pop up that shows up on the phone
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/app
rm Superuser.apk
cd ..
cat /sdcard/flash_image > flash_image
chmod 0700 flash_image
./flash_image recovery /sdcard/clockworkmod/backup/Stock/recovery.img
rm flash_image
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
exit
unroot your phone via universal androot and uninstall it via the applications menu
reboot and done!
I have done this a couple times and every time it worked like a charm.
Hey there, I get to inputting the md5 command, but I get cannot create nandroid.md5: permission denied
What am I doing wrong?
Using a SAPPIMG.zip is not at all unsafe and is faster and easier.
Well, I have been trying to use the sappimg.zip from unlockr's guide and on the t-mobile dev forums, but yet all of them end up giving me a Main version is older! error.
I cant seem to find the solution.
I've had the same problem. I have made the gold card a million times (worked rooting the phone) and now it tells me the older error. Thought it would be easier reverting back, guess that's not true.
Anyways, can I get the flash_image file?
getting past the "older version" error
what i did to get past the "older version" error, was this:
step1: re-use gold card and the 1.5 version sappimg.zip from unlockr.com
step2: reboot using the original sappimg for t-mobile (i wont link from the post but i found it on XDA aka use search)
this will reload EVERYTHING as stock MT3g1.2 including original splash, and recovery images.
if you want to revert it to stock, try this: http://forum.xda-developers.com/showthread.php?t=641174, it may help
The safer way is to NOT BOTHER.
The update schedule is to run from today through the 25th inclusive. That's 11 days. The average length of time that any particular user will have to wait is therefore 5.5 days. Chances are that the update will be posted by tonight or tomorrow (latest), and 10 minutes later, it will be fixed so that it doesn't rob you of root (keep your options open!).
So... you save about 5 days of waiting (average) and end up with your options wide open. OR, you can commit to the average and end up locked out, possibly forever.
I like the way you think...
Sent from my T-Mobile myTouch 3G using XDA App
Need eng spl
bartcrusades said:
well, i have been trying to use the sappimg.zip from unlockr's guide and on the t-mobile dev forums, but yet all of them end up giving me a main version is older! Error.
I cant seem to find the solution.
Click to expand...
Click to collapse
just got through doing the same thing tried goldcard method and still got main version older....then i got it right...flash eng spl i beleive it was 0010 then do the sappimg.zip it works and when you finish the update your 0013 spl is back...then used universal androot installed superuser then installed rom manager and made backup of stock then put my phone back the way it was hopefully when the update comes out and i do think it will be a long time before it does i can restore backup of stock unroot with universal androot and uninstall superuser. At least thats the plan. If you want to do this look for kennys posts in the sappimg thread his directions are what i used.
That is the correct way to do it. Eng spl then tmo stock image. When done its back to completely stock.
Sent from my T-Mobile myTouch 3G using XDA App
hey i do not have flash_image can u post up a link? thanks.
Hello all.
I looked and can't find but is there a rooted 1.55.531.3 rom for the device anywhere.
Rooted the phone tried the ICS from sensation and kinda want to go back but not unroot.
I could send you my recovery if you have the ability to flash
rooted 1.55.531.3 with clockwork recovery and SU
M9x3mos said:
Hello all.
I looked and can't find but is there a rooted 1.55.531.3 rom for the device anywhere.
Rooted the phone tried the ICS from sensation and kinda want to go back but not unroot.
Click to expand...
Click to collapse
yeah, what you are looking for doesn't exist at the moment. i too thought about making a nandroid of the the new ROM for people to flash, but since the new setup comes with a new radio, new kernel, new HBOOT, etc., i'm not sure how it would fly if someone just flashed the nandroid?
Hboot n radio would be the only thing missing... Kernels sits in recovery....
rooted 1.55.531.3 with clockwork recovery and SU
I know I made a flashable package out of the Google Talk apk file, and either did or meant to make some out of the other apps in it - I'm not sure which thread it's in.
I can check later and link it. Not sure what else anyone did with it, if wifi calling wasn't pulled forward from it I'll have a package for that sometime soon anyway.
I also never did get a chance to check what the gps changes were I remember being in it.
Edit:
Link to Gtalk flashable zip package from that update.
Sent from my Bulletproof_Doubleshot using xda premium
nlarge said:
I could send you my recovery if you have the ability to flash
rooted 1.55.531.3 with clockwork recovery and SU
Click to expand...
Click to collapse
Do you have the stock rom for 1.55.531.3 that I can flash on my mt4gs? I would really appreciate it
http://forum.xda-developers.com/showthread.php?t=1484679
http://forum.xda-developers.com/showthread.php?t=1433805
It would be flashed as if restoring a nandroid. I would flash the above link. If you really want it I can send it
rooted 1.55.531.3 with clockwork recovery and SU
Thanks. Okay, this is where I am:
Unlocked bootloader with htcdev
s-on
hboot 1.45.0013
software 1.55.531.3
Would like to achieve root so that I can flash custom roms/use titanium backup. From what I can tell, nlarge was able to accomplish this. (http://forum.xda-developers.com/showthread.php?t=1474933&page=6). However, couldn't post on that thread because I have less than 10 posts....sorry.
Cannot use temproot (FR3VO) method because says needs s-off and/or adb mount issue:
An error occurred while running the exploit (-1) (errno: 22)
c:\Android>adb wait-for-device
c:\Android>adb remount
remount failed: Operation not permitted
c:\Android>adb shell mount -o rw,remount rootfs /
mount: Operation not permitted
c:\Android>adb shell mount -oremount,suid /dev/block/mmcblk0p23 /data
mount: Operation not permitted
c:\Android>adb shell mkdir /vendor/bin
mkdir failed for /vendor/bin, Read-only file system
c:\Android>adb shell chown root.shell /vendor/bin
Unable to chmod /vendor/bin: No such file or directory
c:\Android>adb shell chmod 755 /vendor/bin
Unable to chmod /vendor/bin: No such file or directory
c:\Android>adb push ./sqlite3 /vendor/bin
cannot stat './sqlite3': No such file or directory
c:\Android>adb push ./su /vendor/bin
cannot stat './su': No such file or directory
c:\Android>adb push ./busybox /vendor/bin
cannot stat './busybox': No such file or directory
c:\Android>adb shell chown root.shell /vendor/bin/su
Unable to chmod /vendor/bin/su: No such file or directory
c:\Android>adb shell chown root.shell /vendor/bin/busybox
Unable to chmod /vendor/bin/busybox: No such file or directory
c:\Android>adb shell chown root.shell /vendor/bin/sqlite3
Unable to chmod /vendor/bin/sqlite3: No such file or directory
c:\Android>adb shell chmod 6555 /vendor/bin/su
Unable to chmod /vendor/bin/su: No such file or directory
c:\Android>adb shell chmod 4555 /vendor/bin/busybox
Unable to chmod /vendor/bin/busybox: No such file or directory
c:\Android>adb shell chmod 755 /vendor/bin/sqlite3
Unable to chmod /vendor/bin/sqlite3: No such file or directory
c:\Android>adb shell busybox --install -s /vendor/bin
busybox: permission denied
c:\Android>adb shell sync
c:\Android>adb shell chmod 6555 /vendor/bin
Unable to chmod /vendor/bin: No such file or directory
c:\Android>adb install ./Superuser.apk
can't find './Superuser.apk' to install
c:\Android>pause
Press any key to continue . . .
So, I understand, permission denied/operation not permitted, I assume because I don't have root.
When I look at superuser, it says "su binary voutdated" and when I tap to check for updates, automatic update fails and error message "su was not updated. A zip file (su-2.3.1-bin-signed.zip) has been placed on your sdcard, please reboot into recovery mode and flash it to update your su binary.
Can't boot into recovery mode, phone just sits on mytouch 4g slide screen. Again, I assume because no root. Same thing happens if I try to factory reset, just stays on the mytouch 4g slide screen.
Anyone have any suggestions? I am going crazy trying to get this phone to work. I would really appreciate the help!
Flash clock work recovery... I think I linked it somewhere... Or Google will help
rooted 1.55.531.3 with clockwork recovery and SU
Now find yourself a nice recovery image (CWM), boot phone into fastboot mode, "fastboot flash recovery recovery.img".
When this is done you will have a free and open recovery image, and can use that to write/install the su binary and apk (either with flashable zip or through adb shell, either will work).
rooted 1.55.531.3 with clockwork recovery and SU
nlarge said:
Now find yourself a nice recovery image (CWM), boot phone into fastboot mode, "fastboot flash recovery recovery.img".
When this is done you will have a free and open recovery image, and can use that to write/install the su binary and apk (either with flashable zip or through adb shell, either will work).
rooted 1.55.531.3 with clockwork recovery and SU
Click to expand...
Click to collapse
Have tried flashing new and old versions of cwr and the earlier links from blue with no luck. Trying to do it manually through the computer with fastboot, results in 'waiting for device' message. All drivers installed, usb debug, have tried charge only/mount as disk drive options. Neither work. Have tried flashing manually by converting .img to .zip without compression and flashing through phone. No error message but nothing changes.
Cannot use cwm to flash because not error message says not rooted. Not sure what else to do. BTW, you guys are awesome for helping me out Thanks!
Put your phone in fastboot. Pull battery, hold down and power then try again
rooted 1.55.531.3 with clockwork recovery and SU
How to fastboot flash recovery
Return to Contents Page - doubleshot Developers Reference
Boltinghouse said:
Have tried flashing new and old versions of cwr and the earlier links from blue with no luck. Trying to do it manually through the computer with fastboot, results in 'waiting for device' message. All drivers installed, usb debug, have tried charge only/mount as disk drive options. Neither work. Have tried flashing manually by converting .img to .zip without compression and flashing through phone. No error message but nothing changes.
Cannot use cwm to flash because not error message says not rooted. Not sure what else to do. BTW, you guys are awesome for helping me out Thanks!
Click to expand...
Click to collapse
(hah, thanked but meant to hit quote)
What you need to do is go here: http://clockworkmod.com/rommanager
Scroll down the list and find the recovery for our device (5.0.2.7 for the myTouch 4G Slide) - download this.
Put it in the same folder as 'fastboot.exe' on your computer. Rename it to recovery.img
On your phone, turn off 'fastboot' in power options.
Power off the phone.
Now, give it a minute to power off - then hold the volume down button and press power.
Now it will boot up to the hboot menu. The list presented will have you highlighted on the word 'fastboot' - press power to choose this.
Now you are presented with the fastboot menu. It should say fastboot with a red highlight around it near the top.
At this time you should plug the USB cord from your computer into the phone. It will update to say fastboot USB in red highlight now.
-okay-
We have the phone booted up in fastboot, attached to the computer, and ready to work with.
Open up your command prompt, and navigate to the folder where you have the fastboot command. This is the same folder that you have the new clockworkmod recovery.img in from before.
In your terminal now type:
Code:
fastboot devices
This will come back with your device, serial number, and show you it is connected and ready to go. (if it is not something is wrong)
Now type:
Code:
fastboot flash recovery recovery.img
Let's break this down:
fastboot = activates the fastboot.exe command, and says that what's typed next uses the definitions in that fastboot.exe file.
flash = command that says write to
recovery = destination (name of partition) being written to
recovery.img = file written to previously defined location.
----
Since you have the new clockworkmod recovery file in the same folder as fastboot.exe, and you renamed it to recovery.img, then the previously shown command will overwrite your stock recovery with the new image you are providing it.
At this point you should have clockworkmod recovery in place of your stock recovery when you boot the device to hboot menu and select recovery.
Let us know if you have any other problems.
Good explanation blue.... It sounded like he knew what he was doing, hence my quick correction...
Hate typing a lot out from phone!
rooted 1.55.531.3 with clockwork recovery and SU
OMG! Thats awesome. FINALLY ROOTED!!!!! yay! So happy. Thank you guys so much. nlarge and blue, you two are the best!
Thanks again
~Brandi~
Oops... Sorry I called you a he...LOL... Most of us nerds are guys
We help where we can
Boltinghouse said:
OMG! Thats awesome. FINALLY ROOTED!!!!! yay! So happy. Thank you guys so much. nlarge and blue, you two are the best!
Thanks again
~Brandi~
Click to expand...
Click to collapse
rooted 1.55.531.3 with clockwork recovery and SU
nlarge said:
Oops... Sorry I called you a he...LOL... Most of us nerds are guys
We help where we can
rooted 1.55.531.3 with clockwork recovery and SU
Click to expand...
Click to collapse
It's all good, I know being a chick I'm in the minority here. Either way, thank you so much.
So it looks like both nlarge and boltinghouse rooted s-on phones. Is there any reason not to go ahead and root that way? Is there any reason you need/want s-off?
it depends on what you want to do with your phone...
If you just want to be able to make recovery and flash ROMS than you dont need s-off
If you want to play with other stuff(radios and mounts) then you need s-off.
I personally like doing things to my phone so I would like to get to s-off. I am ok with it for now, but S-off will give me the full control I want.
qwerty3656 said:
So it looks like both nlarge and boltinghouse rooted s-on phones. Is there any reason not to go ahead and root that way? Is there any reason you need/want s-off?
Click to expand...
Click to collapse
A working recovery for Samsung Conquer 4g!!!
Needs Root!
V. 5.0.2.7
1.Download the files below
2.Move flash_image (in the zip folder) and CWMR.img to your sd card
3.On your phone download root explorer
4.Move flash_image to /data/local using root explorer
5.Download a terminal Emulator on your phone
6.Open the terminal and put in:
Code:
$ su
# /data/local/flash_image recovery /sdcard/CWMR.img
7.Than to make sure it doesn't revert to stock recovery put in:
Code:
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock9 /system
to make sure its in rw mode put:
Code:
# mount | grep system
than:
Code:
# chmod 444 /system/etc/install-recovery.sh
(dont worry if you get an error not found some phones dont have this)
Credit goes to utankos over at rootwiki for creating the recovery.
Need some clarification
Perfect timing. I am just now starting to learn how to root my conquer 4g. I am having some issue locating this folder "/data/local/"
/data/local/flash_image recovery /sdcard/CWMR.img
I have installed the Root Browser - free version on my phone, but still not able to find the directory. Am I supposed to create the "local" folder within the /data folder?
Thanks.
yanxizao said:
Perfect timing. I am just now starting to learn how to root my conquer 4g. I am having some issue locating this folder "/data/local/"
/data/local/flash_image recovery /sdcard/CWMR.img
I have installed the Root Browser - free version on my phone, but still not able to find the directory. Am I supposed to create the "local" folder within the /data folder?
Thanks.
Click to expand...
Click to collapse
I have never ran into a problem like this but do so in the /data folder on your phone and sorry this has taken so long I haven't been on XDA for a while. Tell me if it works.
/data/local dir in root browser
Hi, in order to properly see the /data/local folder which is a hidden folder you need to access it as root. If you installed root browser before the phone wa rooted it already checked for root access and was denied. From then on it will run without root permissions. you need to gran it root access before you can access hidden folders the easiest way would be to erase the data of root browser in options|applications.
hope this helps.
Thanks for this, works great!
jhorton014 said:
Thanks for this, works great!
Click to expand...
Click to collapse
Actually I'm having difficulties getting the CWM recovery to be permanent. When I reboot it reverts back to stock recovery. I followed all of the instructions on the tutorial that you provided.
nvm
The official CWM has problems in mounting SD-EXT, thus, Jaggyrom and other custom roms (except stock) won't work properly and your phone will reboot everytime you install apps. You'll also get a lot of app crashes because Dalvik cache can't move properly. Now here's how to flash back to Yannou90's recovery using only Android Terminal Emulator.
__________
THINGS YOU NEED:
1. Your HTC Explorer must be rooted
2. Flash_image and Recovery (You can download it here on this thread)
3. Root File Explorers (Like Root Explorer and ES File Manager, at play store)
STEPS:
1. Download the zip file, read the readme inside the zip, and extract flash_image and recovery.img to the root of your SD Card
2. Download Root Explorer from play store, you can use ES file explorer if you want a root file explorer for free
3. Using your root explorer, copy flash_image to /system/bin/ but before you do that, make sure you mount /system/bin/ as R/W.
4. After copying flash_image, set flash_image permissions to rwxrwxrwx
5.Download Android Terminal Emulator on Play store
6. Run Terminal Emulator and open up preferences.
7. at the initial command, put this:
export PATH=/system/bin:$path
7. Go back to Terminal and Type su
8. Superuser should prompt. Accept it.
9. If you saw # it means you are running it as root, which is that we really needed. If you saw $ , it's not running as root and do type su again.
10. now type this:
flash_image recovery /sdcard/recovery.img
11. Wait for it and if it's done, boot your phone to recovery.
12. CONGRATULATIONS AND YOU ARE BACK TO YANNOU90's RECOVERY
DOWNLOAD LINK:
Flash_Image and Recovery.zip
mrchezco1995 said:
......
2. Flash_image and Recovery (You can download it here on this thread)
......
Click to expand...
Click to collapse
Sorry, on trying to download the following message shows up.
"The page you have requested does not exist. Please check your spelling and try again."
Can you please re-upload the Flash_image and Recovery.zip ?
Download link 404..
Sent from my HTC desire_HD using xda app-developers app
beegeevee said:
Sorry, on trying to download the following message shows up.
"The page you have requested does not exist. Please check your spelling and try again."
Can you please re-upload the Flash_image and Recovery.zip ?
Click to expand...
Click to collapse
Deivi_Z said:
Download link 404..
Sent from my HTC desire_HD using xda app-developers app
Click to expand...
Click to collapse
Download link fixed. Uploaded it to mediafire instead. Thanks for reminding guys.
permission denied
followed all the steps....still got the "Permission Denied" message
followed all the steps....still got the "Permission Denied" message
Click to expand...
Click to collapse
Check superuser and make sure Terminal is allowed. And type su in all lowercase, not uppercase like SU. That wont work
Sent from my HTC Explorer using XDA
mrchezco1995 said:
The official CWM has problems in mounting SD-EXT, thus, Jaggyrom and other custom roms (except stock) won't work properly and your phone will reboot everytime you install apps. You'll also get a lot of app crashes because Dalvik cache can't move properly. Now here's how to flash back to Yannou90's recovery using only Android Terminal Emulator.
__________
THINGS YOU NEED:
1. Your HTC Explorer must be rooted
2. Flash_image and Recovery (You can download it here on this thread)
3. Root File Explorers (Like Root Explorer and ES File Manager, at play store)
STEPS:
1. Download the zip file, read the readme inside the zip, and extract flash_image and recovery.img to the root of your SD Card
2. Download Root Explorer from play store, you can use ES file explorer if you want a root file explorer for free
3. Using your root explorer, copy flash_image to /system/bin/ but before you do that, make sure you mount /system/bin/ as R/W.
4. After copying flash_image, download Android Terminal Emulator on Play store
5. Run Terminal Emulator and open up preferences.
6. at the initial command, put this:
export PATH=/system/bin:$path
7. Go back to Terminal and Type su
8. Superuser should prompt. Accept it.
9. If you saw # it means you are running it as root, which is that we really needed. If you saw $ , it's not running as root and do type su again.
10. now type this:
flash_image recovery /sdcard/recovery.img
...
After this step what I get is as follows
usage: flash_image partition file.img
sh-3.2#
Click to expand...
Click to collapse
Superuser worked fine on terminal. But also got permission denied on last command in terminal.. should I push it via ADB?
You can simply flash the recovery using fastboot. Download this ZIP: http://forum.xda-developers.com/attachment.php?attachmentid=913094&d=1329843100 (courtesy of jaggyjags), start your phone in fastboot mode (ROM Manager might be able to reboot your phone into this mode, otherwise just turn it off, pull out the battery and replace it, then turn on while holding volume down and choose "FASTBOOT" from the menu that appears), then run "recovery.bat" from inside the ZIP. It's simpler than having to mess with adding files to /system/bin.
FYI, you need to set permissions on flash_image to allow it to be executed. I think typing this in the terminal emulator should work:
Code:
chmod 777 /system/bin/flash_image
(otherwise use your file manager to change the permissions to give read, write and execute permissions to all users i.e. tick all the boxes). This is the missing step from your guide to make it work from terminal emulator.
Also, you don't need multiple apps, you can just use terminal emulator for it all by using the "cp" command e.g. if flash_image is on the root of your SD card, use the following commands:
Code:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cp /sdcard/flash_image /system/bin/flash_image
then use the chmod command above and then the original command from the first post.
[BTW, if you're wondering, the first command identifies as root, the second remounts /system as RW, the last copies the file]
So the full process for terminal emulator ONLY, would be this:
Code:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cp /sdcard/flash_image /system/bin/flash_image
chmod 777 /system/bin/flash_image
flash_image recovery /sdcard/recovery.img
{rm /sdcard/flash_image
rm /sdcard/recovery.img}
The commands in the {} are optional and just delete the two files from your SD card. The 2nd and 3rd commands can be excluded if you copy flash_image with a root capable file manager, as can the 4th if you change permissions with the file manager.
(This post ended up being much longer than I originally intended. I was just going to post the first paragraph, but figured I may as well post how to make it work the way the OP described as well - or at least what I think should make it work, I haven't actually tested the full process [I have tested the exact same process with other binaries {viewmem, tcpdump} and it works perfectly. Provided the usage of flash_image as in the OP is correct and works, this method will work])
EDIT: You also shouldn't have to change the initial command, /system/bin is already specified in $PATH. If it wasn't, pretty much nothing on the phone will work.
SifJar said:
You can simply flash the recovery using fastboot. Download this ZIP: http://forum.xda-developers.com/attachment.php?attachmentid=913094&d=1329843100 (courtesy of jaggyjags), start your phone in fastboot mode (ROM Manager might be able to reboot your phone into this mode, otherwise just turn it off, pull out the battery and replace it, then turn on while holding volume down and choose "FASTBOOT" from the menu that appears), then run "recovery.bat" from inside the ZIP. It's simpler than having to mess with adding files to /system/bin.
FYI, you need to set permissions on flash_image to allow it to be executed. I think typing this in the terminal emulator should work:
Code:
chmod 777 /system/bin/flash_image
(otherwise use your file manager to change the permissions to give read, write and execute permissions to all users i.e. tick all the boxes). This is the missing step from your guide to make it work from terminal emulator.
Also, you don't need multiple apps, you can just use terminal emulator for it all by using the "cp" command e.g. if flash_image is on the root of your SD card, use the following commands:
Code:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cp /sdcard/flash_image /system/bin/flash_image
then use the chmod command above and then the original command from the first post.
So the full process for terminal emulator ONLY, would be this:
Code:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cp /sdcard/flash_image /system/bin/flash_image
chmod 777 /system/bin/flash_image
flash_image recovery /sdcard/recovery.img
{rm /sdcard/flash_image
rm /sdcard/recovery.img}
The commands in the {} are optional and just delete the two files from your SD card. The 2nd and 3rd commands can be excluded if you copy flash_image with a root capable file manager, as can the 4th if you change permissions with the file manager.
(This post ended up being much longer than I originally intended. I was just going to post the first paragraph, but figured I may as well post how to make it work the way the OP described as well - or at least what I think should make it work, I haven't actually tested the full process [I have tested the exact same process with other binaries {viewmem, tcpdump} and it works perfectly. Provided the usage of flash_image as in the OP is correct and works, this method will work])
EDIT: You also shouldn't have to change the initial command, /system/bin is already specified in $PATH. If it wasn't, pretty much nothing on the phone will work.
Click to expand...
Click to collapse
Thank You. U completed this thread. Decided to use fastboot (faster) instead of terminal emulator way.
SifJar said:
You can simply flash the recovery using fastboot. Download this ZIP: http://forum.xda-developers.com/attachment.php?attachmentid=913094&d=1329843100 (courtesy of jaggyjags), start your phone in fastboot mode (ROM Manager might be able to reboot your phone into this mode, otherwise just turn it off, pull out the battery and replace it, then turn on while holding volume down and choose "FASTBOOT" from the menu that appears), then run "recovery.bat" from inside the ZIP. It's simpler than having to mess with adding files to /system/bin.
FYI, you need to set permissions on flash_image to allow it to be executed. I think typing this in the terminal emulator should work:
Code:
chmod 777 /system/bin/flash_image
(otherwise use your file manager to change the permissions to give read, write and execute permissions to all users i.e. tick all the boxes). This is the missing step from your guide to make it work from terminal emulator.
Also, you don't need multiple apps, you can just use terminal emulator for it all by using the "cp" command e.g. if flash_image is on the root of your SD card, use the following commands:
Code:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cp /sdcard/flash_image /system/bin/flash_image
then use the chmod command above and then the original command from the first post.
So the full process for terminal emulator ONLY, would be this:
Code:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cp /sdcard/flash_image /system/bin/flash_image
chmod 777 /system/bin/flash_image
flash_image recovery /sdcard/recovery.img
{rm /sdcard/flash_image
rm /sdcard/recovery.img}
The commands in the {} are optional and just delete the two files from your SD card. The 2nd and 3rd commands can be excluded if you copy flash_image with a root capable file manager, as can the 4th if you change permissions with the file manager.
(This post ended up being much longer than I originally intended. I was just going to post the first paragraph, but figured I may as well post how to make it work the way the OP described as well - or at least what I think should make it work, I haven't actually tested the full process [I have tested the exact same process with other binaries {viewmem, tcpdump} and it works perfectly. Provided the usage of flash_image as in the OP is correct and works, this method will work])
EDIT: You also shouldn't have to change the initial command, /system/bin is already specified in $PATH. If it wasn't, pretty much nothing on the phone will work.
Click to expand...
Click to collapse
Mine worked for me on terminal without any problems, but thanks for filling up what I just missrf for others. Hehe
Sent from my HTC Explorer using XDA
mrchezco1995 said:
10. now type this:
flash_image recovery /sdcard/recovery.img
11. Wait for it and if it's done, boot your phone to recovery.
]
Click to expand...
Click to collapse
I did upto this point when I write and enter this string nothing happens it gives me another sh-3.2# to write in. How would I know that the Yannou90 recovery has completed??? I'm stuck
SherazHashmi said:
I did upto this point when I write and enter this string nothing happens it gives me another sh-3.2# to write in. How would I know that the Yannou90 recovery has completed??? I'm stuck
Click to expand...
Click to collapse
Why don't you try step 3 from jaggyjag's rooting tutorial....
Sent from my HTC Explorer A310e using xda app-developers app
My HTC Explorer's recovery was stuck green logo, but what thing that helped to get back my clockword recovery
is just downloading you recovery file and renamed it recovery.img
And...
I used Android SDK tool, and used the below command in command prompt and then I reboot the mobile, and I got back:
fastboot flash recovery recovery.img
Thanks for this valuable thread
SU not found !
after changing the INITIAL COMMAND
i restarted d terminal and now the initial command just gets printed and after that i typed 'su'...d output was 'su not found'..
wats d problem ???
I even tried d fastboot method...dats epic, whenever i try to install any .zip from it dis is wat i see
"Installing update...
Installation aborted."
Plz suggest nythng else other than REFLASHING it...its just that sumthng is restricting it to install :laugh:
hi! I have a question regarding recoveries... i have a recovery by yannou90 installed on my htc explorer, will this recovery work for other roms such as CM9 and CM10? It worked well with JaggyJags rom (3.2.1).. i am wondering if I need to switch to other recovery prior to installing CM roms.. thanks!
iamwin said:
hi! I have a question regarding recoveries... i have a recovery by yannou90 installed on my htc explorer, will this recovery work for other roms such as CM9 and CM10? It worked well with JaggyJags rom (3.2.1).. i am wondering if I need to switch to other recovery prior to installing CM roms.. thanks!
Click to expand...
Click to collapse
Yeah, ll work for all rom installation...
Hit :thumbup: if i helped...
R. SAINT said:
Yeah, ll work for all rom installation...
Hit :thumbup: if i helped...
Click to expand...
Click to collapse
got it man!
the steos for flashing the recovery worked for me but after 2 weeks now it responds to nothing when i try to wipe dalwik cache or perform any other funtion it displays nothing only the green title saying yonnou90 recovery.
Mayank T said:
the steos for flashing the recovery worked for me but after 2 weeks now it responds to nothing when i try to wipe dalwik cache or perform any other funtion it displays nothing only the green title saying yonnou90 recovery.
Click to expand...
Click to collapse
My initial response to such a situation would be start the phone in fastboot mode and then flash the recovery from there. Download the ZIP here: http://forum.xda-developers.com/attachment.php?attachmentid=913094&d=1329843100, extract it and double click "recovery.bat" once the phone is in fastboot mode (start phone holding volume down, select fastboot from menu instead of recovery).
This assumes you're on Windows. If you're on Mac/Linux, find the fastboot binary for your platform and run the following command in a terminal:
Code:
./fastboot flash recovery recovery.img
where recovery.img is taken from the ZIP I linked above.
Alternatively, you could install a more up-to-date recovery such as TWRP or a newer build of CWM (not sure of links for the latest versions of either, but have a look around the forum and you should find them. Also some older builds of CWM had bugs [hence this thread exists], but I think the newer builds work fine on the Explorer; not 100% sure as I still use yannou90's build)
I have gotten the built-in wireless tether to work. I know there's been some discussion about getting Wireless tether without FoxFi and similar.
Since we cannot use the recovery method directly, you can still use the tools and everything from it.
So to begin:
Obviously, you must have root for this to work.
1) Download the patch.zip from the original thread. [here: http://forum.xda-developers.com/showthread.php?t=2768837 ]
2) extract the zip to somewhere on sdcard. I extracted mine to the Download folder. You may need to edit the script below to reflect your locations.
3) okay, this part gets a little weird, but bear with me...
Save this code as run.sh in Download folder or wherever you extracted. You can over-write the old run.sh if you save it in toggle folder where original was located-- BE SURE TO EDIT AS REQUIRED
Code:
#!/sbin/sh
cp /mnt/sdcard/Download/toggle/sqlite3 /data/local/tmp/sqlite3
chmod 0777 /data/local/tmp/sqlite3
mount -o remount,rw /dev/block/mmcblk0p23 /system
cp /system/framework/framework-res.apk /system/framework/framework-res.apk.bak
cp /mnt/sdcard/Download/system/framework/framework-res.apk /system/framework/framework-res.apk
/data/local/tmp/sqlite3 /data/data/com.android.providers.settings/databases/settings.db < /mnt/sdcard/Download/toggle/toggles.sql
4) now open up adb on pc (preferred!!! So you can still see progress and if necesary you can undo/alter/fix things) or terminal emulator (untested but should work, may be weird since you have to reboot phone while it's interface is locked up)
Run:
adb shell
su
sh /mnt/sdcard/Download/toggle/run.sh [or where ever you saved it]
5) Your phone will probably lock up now because you've just replaced the framework-res.apk while the system was running.
adb reboot or reboot by other methods.
6) Profit ;]
I DO NOT WARRANTY OR GUARANTEE THIS METHOD. USE AT YOUR OWN RISK
I believe the sqlite edits serve the purpose of showing the icon in the quick settings pull down. Otherwise, just replacing the framework-res.apk with the correct changes is enough: See this thread for the changes needed:
http://forum.xda-developers.com/showthread.php?t=2759119
Incidentally, I was attempting to make the changes on my own and recompile the framework-res.apk, and I must've done something not quite right because the phone hung at the verizon logo. Thankfully adb was up so I was able to remount system as rw to replace the edited framework-res.apk from the original thread OP linked. Interestingly enough, as soon as I finished copying the edited file, the phone continued booting just fine, and I'm posting from the native tethered connection now.
Edit: I was able to do the changes on the framework-res.apk extracted/decompiled from my phone after all. I'm guessing that the phone didn't like deflate method as opposed to store method (no compression) on the resources.arsc file in the apk file. Had to use the 7zip command line tool to save the modified resources.arsc file without compression to the original apk:
7z u -mx0 framework-res.apk.zip resources.arsc
where -mx0 means no compression (copy)
Got it enabled by just replacing the framework-res.apk, and noticed speeds were really slow. I get 1.88mbps on LTE at home (so-so coverage), but only .15mbps on my iPad connected to my phone via Wi-Fi.
I did this: http://forum.xda-developers.com/showpost.php?p=53431713&postcount=9
SO MUCH EASIER than what you guys were doing. :good:
Droid_Evo_8 said:
I did this: http://forum.xda-developers.com/showpost.php?p=53431713&postcount=9
SO MUCH EASIER than what you guys were doing. :good:
Click to expand...
Click to collapse
It's a manner of preference. In terms of overhead, this native method should technically be quicker to enable, as it does not have to wait for the exposed module to intercept the call and return an empty array of apps to execute for the provision check. That being said, we're probably talking miliseconds at most. While I use xposed for other modules sometimes, others might prefer not to, and this native method does not require it.
vacaloca said:
It's a manner of preference. In terms of overhead, this native method should technically be quicker to enable, as it does not have to wait for the exposed module to intercept the call and return an empty array of apps to execute for the provision check. That being said, we're probably talking miliseconds at most. While I use xposed for other modules sometimes, others might prefer not to, and this native method does not require it.
Click to expand...
Click to collapse
I don't know much about adb or terminal emulator so I'm fine with it. :good:
Here's to hoping for an easy tethering mod!
fillyo said:
Here's to hoping for an easy tethering mod!
Click to expand...
Click to collapse
I'm not sure how easier it can get than installing xposed framework + X Tether mod and rebooting, or replacing the framework-res.apk file on your phone with the one listed in the OP... either will work. This of course assumes you have the Verizon model. Replacing the premade framework-res.apk on any other S5 model would probably cause issues and wouldn't solve anything .
I just made it 'harder' on myself by deciding to copy the original framework-res.apk from my phone, and using the latest apktool and aapt to extract the apk, make the modifications, rebuild it, and replace it on my phone (after renaming the original to .bak). I mostly did this to refresh my memory on how to do it as I had done the process with another phone a while back to do the same mod. As I mentioned earlier, the sqlite stuff is only necessary if you want a toggle in the quick settings bar... otherwise you can just go into settings menu and enable it that way.
vacaloca said:
I'm not sure how easier it can get than installing xposed framework + X Tether mod and rebooting, or replacing the framework-res.apk file on your phone with the one listed in the OP... either will work.
Click to expand...
Click to collapse
I don't see the framework-res.apk file in OP, am I missing something? I have no idea how to decompile mine to make changes.
fillyo said:
I don't see the framework-res.apk file in OP, am I missing something? I have no idea how to decompile mine to make changes.
Click to expand...
Click to collapse
It's linked to in step (1). It's inside the zip file that's meant to be flashed in a recovery... however, because our bootloader is still locked, we cannot flash a recovery, so the way to do it is by replacing the framework-res.apk file as the filesystem is live, which as the OP mentions, will trigger a soft reboot as this file is used extensively by Android apps.
vacaloca said:
It's linked to in step (1). It's inside the zip file that's meant to be flashed in a recovery... however, because our bootloader is still locked, we cannot flash a recovery, so the way to do it is by replacing the framework-res.apk file as the filesystem is live, which as the OP mentions, will trigger a soft reboot as this file is used extensively by Android apps.
Click to expand...
Click to collapse
I got the framework-res apk from the zip package, I guess I am a little nervous since this is from a dev edition, correct? Anyone else successfully just replace framework-res from the zip package on their retail Verizon GS5?
fillyo said:
I got the framework-res apk from the zip package, I guess I am a little nervous since this is from a dev edition, correct? Anyone else successfully just replace framework-res from the zip package on their retail Verizon GS5?
Click to expand...
Click to collapse
The OP (presumably), user in post #3, and myself before I did the changes manually.
SO I followed these instructions and this is what i get both from adb and Term Em.
mount: No such file or directory
: Read-Only file systemramework-res.apk.bak
: Read-Only file systemramework-res.apk
/mnt/sdcard/download/toggle/run.sh[8]: /mnt/sdcard/download/toggle/sqlite3: can't execute: permission denied
I use the same folder structure you did, created a download folder and extracted the zip...
Thoughts?
tangoboyz said:
SO I followed these instructions and this is what i get both from adb and Term Em.
mount: No such file or directory
: Read-Only file systemramework-res.apk.bak
: Read-Only file systemramework-res.apk
/mnt/sdcard/download/toggle/run.sh[8]: /mnt/sdcard/download/toggle/sqlite3: can't execute: permission denied
I use the same folder structure you did, created a download folder and extracted the zip...
Thoughts?
Click to expand...
Click to collapse
Seems at least like 2 errors... the mount command can't find the input or output directories, thus you attempt to copy the files and get read-only file system, and it looks like sqlite3 needs to be changed to executable... chmod +x sqlite3
Also make sure you're running as root, obviously.
I saw a similar post int the android development subforum, and they seem to believe you will bootloop if you try to overwrite your framework-res. I chickened out and just did the xposed and x tether mod.
vacaloca said:
Seems at least like 2 errors... the mount command can't find the input or output directories, thus you attempt to copy the files and get read-only file system, and it looks like sqlite3 needs to be changed to executable... chmod +x sqlite3
Also make sure you're running as root, obviously.
Click to expand...
Click to collapse
I am rooted. Here's what i had in my run.sh:
#!/sbin/sh
cp /mnt/sdcard/Download/toggle/sqlite3 /data/local/tmp/sqlite3
chmod 0777 /data/local/tmp/sqlite3
mount -o remount,rw /dev/block/mmcblk0p23 /system
cp /system/framework/framework-res.apk /system/framework/framework-res.apk.bak
cp /mnt/sdcard/Download/system/framework/framework-res.apk /system/framework/framework-res.apk
/mnt/sdcard/Download/toggle/sqlite3 /data/data/com.android.providers.settings/databases/settings.db < /mnt/sdcard/Download/toggle/toggles.sql
NOW does this look right??
#!/sbin/sh
cp /mnt/sdcard/Download/toggle/sqlite3 /data/local/tmp/sqlite3
chmod +x 0777 /data/local/tmp/sqlite3
mount -o remount,rw /dev/block/mmcblk0p23 /system
cp /system/framework/framework-res.apk /system/framework/framework-res.apk.bak
cp /mnt/sdcard/Download/system/framework/framework-res.apk /system/framework/framework-res.apk
/mnt/sdcard/Download/toggle/sqlite3 /data/data/com.android.providers.settings/databases/settings.db < /mnt/sdcard/Download/toggle/toggles.sql
I'm sorry as I'm very new to this.
tangoboyz said:
I am rooted. Here's what i had in my run.sh:
#!/sbin/sh
cp /mnt/sdcard/Download/toggle/sqlite3 /data/local/tmp/sqlite3
chmod 0777 /data/local/tmp/sqlite3
mount -o remount,rw /dev/block/mmcblk0p23 /system
cp /system/framework/framework-res.apk /system/framework/framework-res.apk.bak
cp /mnt/sdcard/Download/system/framework/framework-res.apk /system/framework/framework-res.apk
/mnt/sdcard/Download/toggle/sqlite3 /data/data/com.android.providers.settings/databases/settings.db < /mnt/sdcard/Download/toggle/toggles.sql
NOW does this look right??
#!/sbin/sh
cp /mnt/sdcard/Download/toggle/sqlite3 /data/local/tmp/sqlite3
chmod +x 0777 /data/local/tmp/sqlite3
mount -o remount,rw /dev/block/mmcblk0p23 /system
cp /system/framework/framework-res.apk /system/framework/framework-res.apk.bak
cp /mnt/sdcard/Download/system/framework/framework-res.apk /system/framework/framework-res.apk
/mnt/sdcard/Download/toggle/sqlite3 /data/data/com.android.providers.settings/databases/settings.db < /mnt/sdcard/Download/toggle/toggles.sql
I'm sorry as I'm very new to this.
Click to expand...
Click to collapse
The original script should work assuming the files are in the right path... when I mentioned make sure you are running as root meant, make sure you run the 'su' command and get the # prompt before you run the script, otherwise the script won't run with root permissions and will fail.
For the third line, you (and the OP) can replace the mount command with:
Code:
mount -o,remount rw /system
----
As an aside, the chmod 0777 part in the original script already does mark the file as executable... chmod works with generic +rwx (read,write,execute) distinctions or the regular numbering permissions (777 means rwx for everyone)
Edit: the last line of the script should start with: /data/local/tmp/sqlite3
because that's the one that you set the permissions to rwx, not the one in your sdcard
vacaloca said:
The original script should work assuming the files are in the right path... when I mentioned make sure you are running as root meant, make sure you run the 'su' command and get the # prompt before you run the script, otherwise the script won't run with root permissions and will fail.
For the third line, you (and the OP) can replace the mount command with:
Code:
mount -o,remount rw /system
----
As an aside, the chmod 0777 part in the original script already does mark the file as executable... chmod works with generic +rwx (read,write,execute) distinctions or the regular numbering permissions (777 means rwx for everyone)
Edit: the last line of the script should start with: /data/local/tmp/sqlite3
because that's the one that you set the permissions to rwx, not the one in your sdcard
Click to expand...
Click to collapse
Hmm still no dice... Something isn't working right. Really I wanted the Hotspot in the pull down menu. I am currently paying for hotspot anyway....
Just found that wanam xposed has an option to skip provisioning check. Anyone tried this yet? Seems to enable native tethering but doesn't give a quick settings button.
dlscott1111 said:
Just found that wanam xposed has an option to skip provisioning check. Anyone tried this yet? Seems to enable native tethering but doesn't give a quick settings button.
Click to expand...
Click to collapse
Yes, we have tried it and it works. The quick settings button, as I have mentioned earlier in this thread, is what the sqlite3 executable and the file commands it takes in (just a simple text file of DB commands) take care of. You could also just get sqlite editor ($3 from the play store, IIRC) and do them manually if you don't like command line tools. it's basically adding "WiFiHotspot" to system -> notification_panel_active_app_list_for_reset and notification_panel_default_active_app_list in the settings.db file in /data/data/com.android.providers.settings/databases/
Or you could just do it the free with the command line sqlite3 using the tools already at your disposal