Hello All. Its me again. This time I bring you a long awaited solution. I'm sure you can remember changing your LCD density and then going to install an app which has always worked only to find that the market says its incompatible with your device. Well wait no more, This little hack will make you able to set any density and not be limited in the market.
EDIT: NOW A FLASHABLE ZIP
Process:
Download the zip and flash in recovery. (MOUNT SYSTEM FIRST)
Code:
/system/bin/density (YOUR DESIRED DENSITY)
reboot
Thats it. With every boot, the init.d script spawns the marketdensity script and it waits 45 seconds for boot to complete... Then it swaps the build.props so the market sees the correct one.
Have fun changing your density and not being limited.
Wanna help pay my bills???? Consider Donating
http://goo.gl/qQVRs
atc3030
Edited OP with new zip. Now flashable.
It didn't take when I flashed it. I'm using twrp recovery. does this support edify?
I could just put those files in there place with root explorer, right? What permissions do they need?
EDIT: I just realized I forgot to mount system. Will try again
Yes you can do root explorer. Idk the perms they need through that but if you use chmod in terminal, the perms are 775
Sent from my DROID2 GLOBAL using Tapatalk
It worked this time mounting system like I should have, lol.
But where do I enter the density? In place of the $1?
No. You run the script in terminal
Sent from my DROID2 GLOBAL using Tapatalk
I'm surprised more people aren't taking an interest in this. I understood this was a problem
Sent from my DROID2 GLOBAL using Tapatalk
atc3030 said:
I'm surprised more people aren't taking an interest in this. I understood this was a problem
Sent from my DROID2 GLOBAL using Tapatalk
Click to expand...
Click to collapse
I'm interested This has been a thorn in my side for a while now...
Gonna try this out
m.
No Joy.
Out of the box, the density script wasn't running, failing on the mount command.
I made a few changes to get it to run:
Code:
#!/system/bin/sh
echo "Setting Density to $1"
# mount only runs as root, so execute 'su' before 'mount'
su
# mount was failing without specifying the device
mount -o remount,rw /dev/block/mmcblk0p24 /system
sed "s/^ro\.sf\.lcd_density=.*/ro.sf.lcd_density=$1/" /system/build.prop > /system/.build.prop.hack
# not sure if this next mount is needed, but it makes sense to me to remount as ro once we've made the changes
mount -o remount,ro /dev/block/mmcblk0p24 /system
exit
After those changes, I was finally able to run density, and it does everything its supposed to, ie it creates /system/.build.prop.hack and the density is set to what I want there.
However, when I reboot, the changes are not applied. I'm guessing that the 98density init.d script is not being called.
I'm running a Telus SGH-T989 with Juggernaut 4.1 ROM.
Any thoughts on how to get this last piece to fall into place?
Clever idea btw, we really need something like this
m.
It works for me. I will work on it when I get home
Sent from my DROID2 GLOBAL using Tapatalk
I wanna try this out when I get home. awesome awesome awesome
Question: the 98density file in init.d is it suppose to be 755? cause all the other files in init.d are like so
I'm getting an sed:command not found. To fix it I had to write:
Busybox sed etc ....
this also needs needs SU
--EDIT-- just noticed a user above me had similar tweaks I wrote below (now striked out).
BTW for the mounting.. I think it will have to depend on your device..I got mine to mount by
mount -o rw,remount /dev/block/mmcblk0p24 /system
which I believe is different per device. I'll try the script again by changing that part of the code
After all the changes and no error. after reboot nothing changed.
very excited though
I am going to work on the scripts when I get home. They are on that computer.
Sent from my DROID2 GLOBAL using Tapatalk
emmdub said:
No Joy.
Out of the box, the density script wasn't running, failing on the mount command.
I made a few changes to get it to run:
Code:
#!/system/bin/sh
echo "Setting Density to $1"
# mount only runs as root, so execute 'su' before 'mount'
su
# mount was failing without specifying the device
mount -o remount,rw /dev/block/mmcblk0p24 /system
sed "s/^ro\.sf\.lcd_density=.*/ro.sf.lcd_density=$1/" /system/build.prop > /system/.build.prop.hack
# not sure if this next mount is needed, but it makes sense to me to remount as ro once we've made the changes
mount -o remount,ro /dev/block/mmcblk0p24 /system
exit
After those changes, I was finally able to run density, and it does everything its supposed to, ie it creates /system/.build.prop.hack and the density is set to what I want there.
However, when I reboot, the changes are not applied. I'm guessing that the 98density init.d script is not being called.
I'm running a Telus SGH-T989 with Juggernaut 4.1 ROM.
Any thoughts on how to get this last piece to fall into place?
Clever idea btw, we really need something like this
m.
Click to expand...
Click to collapse
Not all devices use the same memory block as your devices. therefore, the way you are mounting system will not work. I am working on fixing this now
Great idea but the hacked market works great.
Sent from my Incredible 2 using Tapatalk
Yeah, my setting wasn't applied after I ran it either but im not sure if it's the same problem as emmdub. I do see that it creates the .buildprop hack file. But i'm not sure why the setting isn't sticking.
I noticed that even with the hacked market sometimes I have to clear data/ cache because sometimes it kind of reverts itself.
Sent from my Incredible 2 using Tapatalk
I would like this to work, but I don't think this solution is permanent for a few reasons:
1. The market does not read the build.prop file directly. It uses the prop values that are stored in memory, and retrieved by the DisplayMetrics class. That is why after changing your density you have to reboot to get the market to recognize your new density.
2. The market does not use your device density to check compatibility. The check is server side. The market sends your density to their servers along with other info about your device when you accept their terms and services (and sometimes periodically, but not every time you use it). It registers your device info with your deviceID, and determines compatibility that way. Its how the website market knows which devices you have and if they are compatible.
Note that I am not an expert, but I have written an app to change lcd density, as well as decompiled the market and studied it a bit, so i am pretty knowledgeable in the subject.
disconnecktie said:
I noticed that even with the hacked market sometimes I have to clear data/ cache because sometimes it kind of reverts itself.
Sent from my Incredible 2 using Tapatalk
Click to expand...
Click to collapse
got a link for the hacked market?
edit: i got it, thanks
http://forum.xda-developers.com/showpost.php?p=20623581&postcount=10
http://forum.xda-developers.com/showthread.php?t=1434037
Here ya go. Just copy the original vending apk from data app to somewhere safe take the new market put in the data/app folder and rename it to vending and change the permissions to
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Did not think of that. I'm going too look into the memory thing right now.
Sent from my DROID2 GLOBAL using Tapatalk
Related
I got bored so I decided to compile the latest Donut source.
Please make a Nandroid backup before you flash any of this! Just in case.
To add Google apps, check out the Google Stuffer, or similar scripts.
Features:
- Latest Donut source compiled for the HTC-Dream
- Stock (No Google apps whatsoever)
- Otherwise fully working (report bugs if you find any though)
Bugs
- Home key and Phone key not working (I'll try to get them to work)
Instructions
Code:
Unzip "Android-1.6_r1.zip"
fastboot erase userdata
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
Only the system.img and boot.img is needed for the flashing procedure, but I included the other images just in case someone wants to take a look at them.
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download
http://www.mediafire.com/?ntdmo0ulxdr
Enjoy~
Is this a root rom?
Great job now we proved to Google that we don't need them
This does not affect the recovery.img. So if you have Cyanogen's 1.4 recovery.img you will still have root.
Although you won't have apps like SuperUser, since it's Stock.
Good Job!
I want to try this, but I dont ADB (yet) can this be flashed thru recovery??
I used Tmobile contacts backup, so I can see if it will restore my contacts.
Chevy
chevycowboyusa said:
I want to try this, but I dont ADB (yet) can this be flashed thru recovery??
I used Tmobile contacts backup, so I can see if it will restore my contacts.
Chevy
Click to expand...
Click to collapse
Yes you can use the recovery console.
Move the files to the root of your sdcard first though.
Code:
mount sdcard [enter]
mount system [enter]
flash_image system /sdcard/system.img [enter]
flash_image boot /sdcard/boot.img [enter]
reboot
any way you could make this a update.zip. so we can just use cyan recovery to flash the zip?
Only things that I noticed to be not working are the home key and phone key.
I'll investigate further.
is this experimental
i feel i shouldnt be looking at this. its so naked
Yes this is experimental since it's compiled from a non-finalized source.
I know this ROM is naked. But since Google is taking action against the distribution of their closed-source apps, everyone has to release Stock ROMs now.
Bavilo said:
Yes this is experimental since it's compiled from a non-finalized source.
I know this ROM is naked. But since Google is taking action against the distribution of their closed-source apps, everyone has to release Stock ROMs now.
Click to expand...
Click to collapse
i know i know its just so different from what were used to seeing.. but this is the new standard now(unless google changes! ..) so might as well get used to it =/
this looks very interesting. i will probably wait to use this until i see that it works with a few of the scripts that are being developed.
DavidChill said:
this looks very interesting. i will probably wait to use this until i see that it works with a few of the scripts that are being developed.
Click to expand...
Click to collapse
I'm sure someone will create a script that's compatible with Donut. Since we have all of the proprietary files necessary.
Script makers, do your magic please ;D
Weird
I keep getting an invalid argument when trying to mount the system in recovery terminal.
i typed
#mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
and
#mount -o remount,rw /dev/block/mtdblock3 /system
and
#mount -o remount,rw /dev/block/mmcblk0p2 /system
I seem to b having a brain fart.
Can i flash thru terminal emulator? edit: [I figured this one out.... NOPE!]
Chevy
It was VERY hard on my eyes to see an actual "bare bones" ROM already. Use to all the bells and whistles. I guess this is what we will have to work with right now till something is figured out. I really like this idea. Has ANYONE tested this yet with any google apps script. I really dont wanna try this until I know that we can get everything. I'll keep my eye on this though. Thanks for coming up with something so quickly
chevycowboyusa said:
I keep getting an invalid argument when trying to mount the system in recovery terminal.
i typed
#mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
and
#mount -o remount,rw /dev/block/mtdblock3 /system
and
#mount -o remount,rw /dev/block/mmcblk0p2 /system
I seem to b having a brain fart.
Can i flash thru terminal emulator? edit: [I figured this one out.... NOPE!]
Chevy
Click to expand...
Click to collapse
To mount anything in the recovery console you just need to type "mount system" for instance...or mount sdcard.
wow.. this is the start of more freedom... Rebenga!!!!
Weird things
Wow.... Something must have been messed up....
I wiped and reflashed cm 4.1.11.1... then I went to recovery terminal (after booting)
was able to [mount system] [mount sdcard] flashed system and boot imgs.
Rebooted and went thru g1 screen, then black, and then another g1 screen, then automatically went back to recovery.... {Weird!!!}
any advice?
chevycowboyusa said:
Wow.... Something must have been messed up....
I wiped and reflashed cm 4.1.11.1... then I went to recovery terminal (after booting)
was able to [mount system] [mount sdcard] flashed system and boot imgs.
Rebooted and went thru g1 screen, then black, and then another g1 screen, then automatically went back to recovery.... {Weird!!!}
any advice?
Click to expand...
Click to collapse
Yea that is weird. I only tried flashing the images with fastboot, and erasing the userdata.
I'm working on fixing the home and phone key atm.
I was trying to push a modified apk into /data/app but it broke the program and I had to re-install the original. All I did was modify the png files in the Pandora widget and some of the colors of Widgetlocker. I'm using terminal emulator as well. I've pushed framework, blur and swype files with no problem. Why is this happening?
Did you use 7zip? If not try it because it won't break it.
Sent from my DROIDX using Tapatalk
7zip isnt always the way to go, Sometimes it works in the data sometimes it doesnt. What string are you using to mount the data partition?
Have you tried pushing the same app to system/app? I have had that work when data wouldnt play well.
I'm using WinRAR to replace the res file and that worked with framework and blur. But I also tried putting a red background into Fancy Widgets and that broke the apk too. This is the string I'm using.
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/com.teslacoilsw.widgetlocker.apk /data/app
cp /sdcard/com.pandora.android.apk /data/app
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
Doesn't the modified apk have to overwrite the original installed one? If pandora and widgetlocker are both in /data/app how would pushing them to /system/app help? I'm not trying to sound like a jerk I have never messed with any type of Linux stuff literally just started Android hacking this week. I'm getting it for the most part. I've come back from the Dark Side of Windows Mobile.
Nah you dont sound like a jerk, always fun to learn. I only got heavy into changing pngs one I got my x. I hade the D1 for awhile but never did my own themes.
Winrar... not sure that might be your problem, I switched to 7zip since thats what everyone recommended.
Also that string is for mounting the system part, not the data.
for data use
su
mount -o rw,remount -t ext3 /dev/block/userdata /data
then push your file
mount -o ro,remount -t ext3 /dev/block/userdata /data
odds are it wont remount it will say busy
so type
reboot
sometime you have to push over the original, sometimes you have to uninstall the original, sometimes you have to uninstall the original and push the file to system/app instead, and the worst one I ran into.... left the original in data/app and had to push the modified one to system/app..... yeah that one sucked.... i was scratching my head for days!
i usually resign the app , uninstall the original and reinstall the modified one using astro or somethin.
xda has a autosign program in here somewhere that can resign the app
Link?
Sent from my DROIDX using Tapatalk
Hmm that killed the apps too. Any other ideas? This is the last bit of customizing I'm trying to do then my phone will have an awesome red theme which I'm sure you will appreciate bad.
Sent from my DROIDX using XDA App
Could you send me the modified and original apk? Ill see if I can finger it out. I'll pm you my email.
Sent via your mom and tapatalk
sorry took so long to reply
http://forum.xda-developers.com/showthread.php?t=473580
basically i have the .bat file in same folder as tools
so before i push an app back to sdcard or w/e i run the program real quick
then astro will install it successfully<sp>
sometimes even using 7z the app just breaks when you mess with it and the only way it will run is if you push it to /system or resign it
just my experience on this
good luck
Ehh I use Terminal Emulator, I haven't graduated to SDK yet...
not to be rude, but of course pushing modified files like that will cause them to not install. You HAVE to resign the app even if you are just messing with the res pics.
No worries, like I said, I started Androiding on Monday. I signed the apk using the method a couple posts ago, but I can't copy the file to the phone. It says the device has either stop responding or is disconnected. I can throw a regular apk like Fancy Widget on no problem. I tried pushing it to the phone but it says the phone isn't mounted, even when plugged in and I can explore it through windows. What am I doing wrong?
hmm make sure you have the proper drivers for the phone for pushing files.
also the phone has to be in pc mode for adb make sure you have debugging checked in applications > development in the phone settings.
or just plug in the phone and switch to mass storage and drop the file in the phone that way.
think if you dont have the proper drivers none of those will work, check motorola website for the drivers or somewhere in xda im sure theres a link.
edit: http://www.motorola.com/consumers/v/index.jsp?vgnextoid=bda09ec8009a0210VgnVCM1000008806b00aRCRD
explodee you get my reply email? All the images look the same. Double check those zips and get back to me.
yeah i sent it right back fixed
edit - I just sent another email
Oh **** I just got it! I've been schooling myself in SDK for the last day and got ADB goin on it with the resigner from the other post. First I sign the app I want to install and then in adb just to the adb install command. But... I couldn't get the modified Pandora to install. Check it out.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just got Pandora working too. I un-installed and renamed to pandora.apk and just pushed it to \system\app in terminal emulator.
Explodee said:
Just got Pandora working too. I un-installed and renamed to pandora.apk and just pushed it to \system\app in terminal emulator.
Click to expand...
Click to collapse
was the new one signed? I just pushed my themed handcent and themed laucher pro to system, still have yet to sign anything.
Come to think of it the pandora i had to push to system/app was only named pandora...
Pandora was not signed. I uninstalled the official pandora and renamed the com.pandora.android.apk to just pandora.apk, then pushed it to \system\app. So now all that is left is to theme the google search widget and I might be done for a while...
http://forum.xda-developers.com/showthread.php?t=817528
It works fine. Rename it from signed_YouTube.apk to YouTube.apk and replace with one in /system/app. Make sure that permissions are set when overwriting.
Works like a charm and looks quite good, thanks for this!
qwer23
Sent from my rooted X10i using XDA App
yep great mod
widget works great also.
Is it actually working for you ??
I am getting network error 400, both on GSM/3G and on WiFi...
There's some sort of Log-In bug, basically don't sign into your youtube account while using this mod and you should be fine. Hopefully there will be a fix for that soon.
Thanks, looks much better...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
...and had no trouble signing in. Did those that have uninstall the old app first?
Yeah looks great!
Thanks 4 share
Sent from my X10i using XDA App
XperiaX10iUser said:
Thanks, looks much better...
...and had no trouble signing in. Did those that have uninstall the old app first?
Click to expand...
Click to collapse
XperiaX10iUser: how'd you go about installing it? I'm still a noob when it comes to ADB and such (and yes, I did read your guide ), and want to make sure I'm not going to mess anything up installing this.
also, google geniewidget.apk (news and weather) also works. this one you can install it thru any file manager.
saltorio said:
XperiaX10iUser: how'd you go about installing it? I'm still a noob when it comes to ADB and such (and yes, I did read your guide ), and want to make sure I'm not going to mess anything up installing this.
Click to expand...
Click to collapse
Ok its easy:
Get to adb (shell):
$su
#mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
#rm /system/app/YouTube.apk
Then go to settings -> applications -> find com.android.youtube.apk and uninstall it
Reboot your phone
Then get to adb (shell):
$su
#mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
Install /sdcard/(where the modded .apk is)/signed_youtube.apk /system/app
Reboot phone
I did the permissions with root explorer (rw-r--r--)
How to do that with adb... idk sry
Sent from my X10i using XDA App
saltorio said:
XperiaX10iUser: how'd you go about installing it?
Click to expand...
Click to collapse
This is how I did it, in a command window on the laptop...
cd C:\android-sdk-windows\tools
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb shell rm system/app/YouTube.apk
adb uninstall com.google.android.youtube
adb push Youtube.apk /sdcard/Youtube.apk
adb shell dd if=/sdcard/Youtube.apk of=/system/app/Youtube.apk
...but if your Tools folder is elsewhere just change the first line.
PoTi_96 said:
Ok its easy:
I did the permissions with root explorer (rw-r--r--)
Click to expand...
Click to collapse
That should be:
# busybox chmod 644 <file>
XperiaX10iUser said:
This is how I did it, in a command window on the laptop...
cd C:\android-sdk-windows\tools
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb shell rm system/app/YouTube.apk
adb uninstall com.google.android.youtube
adb push Youtube.apk /sdcard/Youtube.apk
adb shell dd if=/sdcard/Youtube.apk of=/system/app/Youtube.apk
...but if your Tools folder is elsewhere just change the first line.
Click to expand...
Click to collapse
Wonderful. Worked beautifully, and I was able to login to my profile OK as well.
Thanks!
it didnt worked for me, failed to install.
fogozito said:
it didnt worked for me, failed to install.
Click to expand...
Click to collapse
Make sure to put the .apk in C:\android-sdk-windows\tools, and that it's named "YouTube.apk"
saltorio said:
Make sure to put the .apk in C:\android-sdk-windows\tools, and that it's named "YouTube.apk"
Click to expand...
Click to collapse
Thanks for that I didn't think I need them in both places.
Strange, after it worked perfectly for several hours it now force closes on start every time. Any suggestions?
Btw. I installed with root explorer. I just renamed the apk to YouTube.apk, then did overwrite the old one and set the same permissions that were set in the original youtube app. I was able to log in, too.
Sent from my rooted X10i using XDA App
Edit: reinstall did solve the problem for now. Let's see if it'll last
I also installed it successfully and it was running fine for a bit then suddenly now it is force closing a lot. I had to reboot the phone because it was stuck in a FC loop when I used the search function on the widget.
Wiping the data and resigning in seems to fix it. I guess there could be something wrong with account handling.
qwer23 said:
Strange, after it worked perfectly for several hours it now force closes on start every time. Any suggestions?
Btw. I installed with root explorer. I just renamed the apk to YouTube.apk, then did overwrite the old one and set the same permissions that were set in the original youtube app. I was able to log in, too.
Sent from my rooted X10i using XDA App
Edit: reinstall did solve the problem for now. Let's see if it'll last
Click to expand...
Click to collapse
sierratango88 said:
I also installed it successfully and it was running fine for a bit then suddenly now it is force closing a lot. I had to reboot the phone because it was stuck in a FC loop when I used the search function on the widget.
Wiping the data and resigning in seems to fix it. I guess there could be something wrong with account handling.
Click to expand...
Click to collapse
Did you guys sign in to your YouTube profile in the app? I know there is a problem being reported in the original thread related to signing in.
I did sign in, and it was worked fine initially, but now I'm seeing the same issue as you guys are reporting.
CWM ON EVERY BOOT WITH GPS WORKING
What Is This??
This is a mod to achieve ClockWorkMod Recovery on Every reboot/boot with a fully functioning GPS. So far this is the only method to have CWM On boot without breaking GPS.This methos uses IBMc PowerBoost 2.0.
Things you will need:
1. Jrummy16's BusyBox Installer (download on market)
2. Download PB-2dot0_final.zip and place on sdcard
3. Terminal Emulator (download on market)
INSTRUCTIONS:
Step 1. Reboot into CWM using Atrix Bootstrapper and
Step 2. flash PB-2dot0_final.zip and reboot
Step 3. Once rom loads up , uninstall AtrixBootstrapper or set permissions in SuperUser for it to "denied" (i would uninstall AtrixBootstrapper after quickly setting to deny,you wont need it)
Step 4. Download Jrummy16's Busybox Installer from market,open it,and click install. You want to install latest 1.19 Busybox over 1.17 that you probably have. looks like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 5. Open Terminal emulator and type the following one line at a time,hitting ENTER after each line is typed:
su
mount -o rw,remount /dev/block/mtdblock3 /system
chmod 755 /system/xbin/powerboost
powerboost
now you should see this:
Step 6. It will ask you if you want it to install Jrummy16's BusyBox Installer,just type N for "No" and hit enter as we already installed this.
Step 7. Now it will Prompt you to select a number. type in 5. "CWR On Every Boot"
Step 8. After "Installation Complete" only takes about 2 seconds, you will type 8 for a Reboot,and type Y for yes.
Step 8. Enjoy!
If you like my work,hit the thanks button,if not,hit the back button : P
If you plan on using this in your projects all i ask is for you to simply credit me in your OP.
CREDITS: BMc08GT (creator of the PowerBoost Script)
You are the man!
Thanks....cant hit the button on my mobile app but will when i get to my pc.
So terminal emulator, can that always be used to push adb commands?
Sent from my MB865 using XDA App
916x10 said:
You are the man!
Thanks....cant hit the button on my mobile app but will when i get to my pc.
So terminal emulator, can that always be used to push adb commands?
Sent from my MB865 using XDA App
Click to expand...
Click to collapse
yes and no, for apks i run adb from pc otherwise u run into problems.
Does this also fix the battery issue where it won't turn on or charge from 0%?
Sent from my MB865 on lfaber06's Supercharged ROM V 5, Update 2
You're my hero today. Ha! Thanks for this...
Out of curiosity... Does this work with PB 2.5 as well?
This is great, thanks a lot rdavisct!
Edit: Nevermind, figured it out.
Sent from my MB865 using xda premium
Question
Question. Does the bug still exist wherein the battery discharges completely and the phone is unable to regain a charge with CWM on Recovery script installed? I haven't personally experienced this because I've never let my battery drain. I've seen it posted in another thread.
http://forum.xda-developers.com/showthread.php?t=1543792&page=12
KEB64 said:
Question. Does the bug still exist wherein the battery discharges completely and the phone is unable to regain a charge with CWM on Recovery script installed? I haven't personally experienced this because I've never let my battery drain. I've seen it posted in another thread.
http://forum.xda-developers.com/showthread.php?t=1543792&page=12
Click to expand...
Click to collapse
Yea thats his phone.not a roms doing
Sent from my MB865 using XDA
rdavisct said:
Yea thats his phone.not a roms doing
Sent from my MB865 using XDA
Click to expand...
Click to collapse
So to answer ur question no,u have nothing to worry about
Sent from my MB865 using XDA
Oh I thought it was a cwm on recovery exclusive bug. BTW, congratulations on inheriting ifaber's work. I'm looking forward to V6. V5 is one of my favorites.
Sent from my MB865 using XDA
I can't get the script to stick. After I do the setup and reboot, I boot into CWM like it should, but once I power off and boot again it just boots normally. I followed the directions exactly, and tried the process again, but the same results.
I assume it's because I'm not creating this script where it wants to go. Any advice or help? Thanks
I should note that I'm on stock 3.6 and have only rooted and installed the bootstrapper previously.
41rw4lk said:
I can't get the script to stick. After I do the setup and reboot, I boot into CWM like it should, but once I power off and boot again it just boots normally. I followed the directions exactly, and tried the process again, but the same results.
I assume it's because I'm not creating this script where it wants to go. Any advice or help? Thanks
I should note that I'm on stock 3.6 and have only rooted and installed the bootstrapper previously.
Click to expand...
Click to collapse
Sounds like you are not mounting the /system first. Make sure u type it exactly in terminal emulator as i posted before running powerscript like so "mount -o /dev/block/mtdblock3 /system" without the quotes
Sent from my MB865 using XDA
Does the removal script work with this setup?
Sent from my MB865 using XDA
rdavisct said:
Sounds like you are not mounting the /system first. Make sure u type it exactly in terminal emulator as i posted before running powerscript like so "mount -o /dev/block/mtdblock3 /system" without the quotes
Sent from my MB865 using XDA
Click to expand...
Click to collapse
I typed it just as it is, and even done it in adb shell with copy and paste, but it would never create the init.d folder or the 99cwr script. So I opened root explorer to see what was going on. The system was mounted as rw, but it just wouldn't create it. So I made the init.d folder myself and ran powerboost again and it created the 99cwr script, but still, normal bootup. I guess it needs to be called during boot or whatever, but idk where to set that. Any suggestions or advice? Thanks
41rw4lk said:
I typed it just as it is, and even done it in adb shell with copy and paste, but it would never create the init.d folder or the 99cwr script. So I opened root explorer to see what was going on. The system was mounted as rw, but it just wouldn't create it. So I made the init.d folder myself and ran powerboost again and it created the 99cwr script, but still, normal bootup. I guess it needs to be called during boot or whatever, but idk where to set that. Any suggestions or advice? Thanks
Click to expand...
Click to collapse
It's because the stock ROM doesn't have init.d support. Flash this then try again.
Nice! That was it. Everything works as it should now. Thanks
cogeary said:
It's because the stock ROM doesn't have init.d support. Flash this then try again.
Click to expand...
Click to collapse
Sorry. Read too fast.assumed you were already had init.d support
Sent from my MB865 using XDA
i still can't get it to work..me also have the same problem as @41rw4lk,but after i flash the init.d file I still cannot get it to work:'(
stock rooted 2.3.6
---------- Post added at 07:00 PM ---------- Previous post was at 06:33 PM ----------
sorry a noob question, where do i need to install the busybox? system/bin or system/xbin
Welcome to the one and only, the original, universal
SystemRW / SuperRW feat. MakeRW / ro2rw by lebigmac
This script removes the read-only lock of all partitions embedded in the super partition of your stock firmware.
This allows you to mount your device as R/W and fully debloat your device and customize your MIUI experience to make it run as smooth as silk!
MIUI 12 is great but it has a little bit too much bloatware.
Be very careful and make lots of backups before messing with your System ! One small error could cause irreversible bootloop!
Enjoy debloating and customizing your fully read/write-able Android device!
NOTE: Before launching this script make sure you've got full read/write (rw) access to the /data partition by first decrypting and then mounting /data partition as r/w !
Visit official project thread
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PS C:\adb> adb shell "ls -Alg /dev/block/by-name | grep 'super'"
lrwxrwxrwx 1 root 16 1970-02-02 16:40 super -> /dev/block/sda23
POCO X3 pro
/
so does this work on x3 pro?
edit, it didnt. threw some devblock warnings about not mounting
@gsser Yes it works! Try latest version! Good luck!
lebigmac said:
@gsser it can work depending on how much effort you decide to put into it.
Click to expand...
Click to collapse
well if it is like that, then why is there even a non complete script when it can be done by the owner...
And since you have already asked how it is on x3 pro im saying it doesnt work.
"I'm looking forward to hearing from the Poco X3 Pro users how the script performs on your device."
It is mostly because of current recoveries for x3 pro doesnt support /data yet, but the script can use sdcard rather than internal storage.
@gsser Thanks for the screenshot and feedback. Please download latest v1.32
Feel free to send me your log files if you get any errors and I'll take a look. Thanks.
lebigmac said:
@gsser Thanks for the screenshot and feedback. Please download latest v1.31 that I uploaded today. And feel free to edit the script with your favorite text editor and change the super image dump path in line #333 to this. Then save file.
Code:
sDumpTarget="/sdcard/super_original.bin"
Feel free to send me your log files if you get any errors so I can take a look. Thanks.
Click to expand...
Click to collapse
Only lines i could find about data were these and i edited the path to my sdcard, flashed it.
Edit just seen you edited your reply. Ill try
I'm not 100% sure if your changes will work properly. Feel free to give it a try.
Keep in mind if you change variables the script might not work as expected.
The reason why the script is installed to /data/local/tmp is because in /scard path you don't have execution permission. That's why it's better to launch script from /data/local/tmp
Poco x3 pro recovery don't have full r/w access to /data/local/tmp ?! That's crazy!
You can try launch script directly from android and it should work as expected.
lebigmac said:
I'm not 100% sure if your changes will work properly. Feel free to give it a try.
You can also use /sdcard path it should be the same thing as what you wrote. Good luck.
Please report back any errors thanks.
Keep in mind if you change LOC variable you must also copy the whole script folder to that new location.
The reason why the script is installed to /data/local/tmp is because in /scard path you don't have execution permission. Is better to launch script from /data/local/path
You don't have full access to /data/local/path in poco x3 pro?
Click to expand...
Click to collapse
This is how the folder looks rightnow. Do i need to do anything about it? Also what is LOC :c
Edit nvm, lol im blind
Not sure what you're trying to do but that path is totally messed up
Just run script in android operating system as described in the instructions if you don't have full read write access to /data/local/tmp from custom recovery
Have you tried manually mounting /data partition in orange fox? Maybe it's not mounted and that's why /data/local/tmp is unavailable.
lebigmac said:
Not sure what you're trying to do but that path is totally messed up
Click to expand...
Click to collapse
Yeah ill just change than only line
lebigmac said:
Not sure what you're trying to do but that path is totally messed up
Just run script in android operating system as described in the instructions if you don't have full read write access to /data/local/tmp from custom recovery
Have you tried manually mounting /data partition in orange fox? Maybe it's not mounted and that's why /data/local/tmp is unavailable.
Click to expand...
Click to collapse
All available recoveries have issue mounting data, some cant even mount mtp.
Ill try android one and see what happens.
If your /data partition is not mounted then you can try manually mounting /data partition before running script.
mount /data
lebigmac said:
LOC is a safety path check feature I had to implement because some folks were launching the script from God knows where and overwriting God knows what with dd lol.
Did you try manually mounting /data partition before running script?
mount -o remount,rw /data
Click to expand...
Click to collapse
Yeah, ill try android version then flash it with fastboot but im a bit confused. Do i execute this command or do i need to do other things? Sorry im a noob at these things
./makesysrw.sh in=./files/super/super_original.bin out=./custom/path/super_fixed.bin size=50
Actually ill stop here since i dont get the whole thing, i dont understand at all :/ once i tried to use linux and it was not fun for me... Im bad with command lines and scripts
After copying script folder into /data/local/tmp/
open command prompt and type this
Bash:
adb shell
su
cd /data/local/tmp/systemrw_1.32
chmod +x ./systemrw.sh
./systemrw.sh size=50
lebigmac said:
After installing script folder into /data/local/tmp/
open command prompt and type this
Bash:
adb shell
su
cd /data/local/tmp/makesysrw_1.31
chmod +x ./makesysrw.sh
./makesysrw.sh size=25
Click to expand...
Click to collapse
now this is what i like
are you sure your bootloader is unlocked?
now do i need to flash the super_fixed.bin in script folder's files folder in fastboot? original super is approx. 8gb and fixed one is nearly half of it