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.
Related
I built a cm-kernel from Cyanogen's git repository for you to use. For now it is just a boot.img and wlan.ko, but I am going to make an update.zip for you as soon as I have time
Thanks to: cyanogen, rikupw, bcrook and Radix
This boot.img is only tested on CyanogenMod 4.1.11.1 and might work with older versions. But not on non-CyanogenMod roms!
I've also made some instructions for you to use if you want to build your own kernel: http://ostebaronen.dk/?p=210
{
"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"
}
Get the two files here:
BFS-300:
http://ostebaronen.dk/android/cm-kernel-2.6.29-bfs300/boot.img
http://ostebaronen.dk/android/cm-kernel-2.6.29-bfs300/wlan.ko
BFS-302:
http://ostebaronen.dk/android/cm-kernel-2.6.29-bfs302/boot.img
http://ostebaronen.dk/android/cm-kernel-2.6.29-bfs302/wlan.ko
To put it on your phone do as follows.
Code:
adb shell mount -o rw,remount /system
adb push wlan.ko /system/lib/modules
adb push boot.img /sdcard
adb shell
cat /dev/zero > /dev/mtd/mtd2
ignore no space left error.
flash_image boot /sdcard/boot.img
ignore read all-zero errors.
DISCLAIMER: I take no responsibility of bricking your phone, remember always to do nandroid backups! I will try to answer questions you ask here, off-topic questions will be ignored.
Lemme know if you need any help making a kernel update.zip. I would be happy to help out.
Oste
Thanks again! worked 100% well for me
i thing this kernel work for 32b
Very nice information. How about a guide for the pre build?
eViL D: said:
Very nice information. How about a guide for the pre build?
Click to expand...
Click to collapse
What do you mean, for making the boot.img?
I've found out compcache doesn't work, going to look at it.
Or wait, module works fine if I load it myself. So compcache can be enabled with.
Code:
modprobe ramzswap
/system/bin/rzscontrol /dev/block/ramzswap0 --init
swapon /dev/block/ramzswap0
Strange though, because the a2sd script should do this for us...
I know why compcache isn't working for you
Kernel versions and modules are intrinsicly linked by 'uname -r'
Cyanogen's kernel uses 2.6.29-cm41 and you've changed the name with yours to be different - so it's not going to load the modules automagically.
Those modules are slightly hidden from view too - they're in modules.sqf which is a squash4 volume that is mounted on boot.
Good job on documenting the git commands to track cyanogen's builds tho - this is what I need!
cat: write error: No space left on device
????
kchau said:
cat: write error: No space left on device
????
Click to expand...
Click to collapse
i get the same thing
i skipped cat zero
and it hangs at the mytouch screen:
K:\>adb logcat
I//system/bin/sh( 51): /system/bin/sh: Can't open /system/bin/a2sd
I/logwrapper( 51): /system/bin/sh terminated by exit(2)
on dwangs 1.6 rom, never had a2sd to begin with
OK, going to rebuild it for you with the correct uname. Lets see if that solves the modules problems, after that I will look at putting it inside a update.zip. bcrook gave me some guidance so it should be fairly easy
Updated kernel recompiled with the correct uname!
kchau said:
cat: write error: No space left on device
????
Click to expand...
Click to collapse
This is because cat continues filling the device with zeroes until the device is full. So you are ought to get the error No worries. Though this command is not necessary, but good to do since you are sure that nothing is left on it.
OK, for some reason no matter what I do on my phone it will not activate compcache automatically. I tried wiping and installing stock cm4.1.11.1 it didn't work there aswell. So I am sure it is not the kernels fault.
Could someone please confirm compcache is working for them?
will i still have the same a2sd hang on the mytouch screen now?
kchau said:
will i still have the same a2sd hang on the mytouch screen now?
Click to expand...
Click to collapse
What do you mean?
UPDATE:
Ok compcache is working. It seems the a2sd script does not like it when you dont have partitioned your SDcard. If you need help setting it up, ask away!
So what is the difference between the BFS in this kernel & the BFS is cm4.1.11.1? Is this one faster?
Edit: You just stated compcache is working if the sdcard is partitioned... so if we are already partitioned, we shouldn't have any problems, correct? Or do we have to reformat?
Cheesebaron said:
What do you mean?
UPDATE:
Ok compcache is working. It seems the a2sd script does not like it when you dont have partitioned your SDcard. If you need help setting it up, ask away!
Click to expand...
Click to collapse
when im on dwangs rom, it hangs at the mytouch screen, and adb logcat has this message
K:\>adb logcat
I//system/bin/sh( 51): /system/bin/sh: Can't open /system/bin/a2sd
I/logwrapper( 51): /system/bin/sh terminated by exit(2)
i dont think dwang's rom is a rom with a2sd, and i dont have it partitioned in my sd either.
however, when im on 4.0.4, and still dont have a partitioned sdcard, everything works fine
All right kiddies here is the ported version of my Red Dynamite. This is about 99% done and is fully functional. Updated with more red that was missing from original Dynamite.
12/24/10
340 Updated version HERE
-Of course you still need to be deodexed and rooted
-Boot into Koush's recovery and apply Dynamite 340.zip
EDIT:
Put stock sliders back in until I fix the .9png's
Fixed the notification text color to white in the framework xml files
Changed BlurHome Menu buttons to red with white highlights when pressed
I AM NOT RESPONSIBLE FOR ANYTHING BAD HAPPENING TO YOUR PHONE. USE AT YOUR OWN RISK!!!
Update.zip HERE
Download
Requirements
Root (duh!)
Deodexed 2.2
ADB/Terminal Emulator
So far the following things are skinned:
Music
Pandora
Battery Indicator
3G Status
BlurHome
Youtube
Power Widget
Fancy Widget
Facebook
Google Search
Widgetlocker
Lockscreen
Settings
Random Notification Icons (Wifi, BT, Airplane Mode, Silent Mode, Voicemail etc)
The Notification bar is based off of teenfaces thread here:
http://forum.xda-developers.com/showthread.php?t=733966
Thanks to bad4u6669 for the settings, power, and skinned Swype
Swype
Power and Settings
I'm gradually getting the hang of Androiding so take it easy. And if I'm forgetting anyone to give credit to let me know and I'll give credit where credit is due. Also I can't post the apk's for the commercial apps like Widgetlocker and Pandora so I can give you the res file to manually insert into the apk.
{
"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"
}
Directions
Unzip the contents of Froyo Dynamite.zip and put them on the root of your SD card
Open ADB or Terminal Emulator and input the following commands exactly
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/Music.apk /system/app
cp /sdcard/pandora.apk /system/app
cp /sdcard/Vvm.apk /system/app
cp /sdcard/com.facebook.katana.apk /system/app
cp /sdcard/GoogleQuickSearchBox.apk /system/app
cp /sdcard/BlurHome.apk /system/app
cp /sdcard/Swype.apk /system/app
cp /sdcard/Settings.apk /system/app
cp /sdcard/YouTube.apk /system/app
cp /sdcard/services.jar /system/framework
cp /sdcard/framework-res.apk /system/framework
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
The Fancywidget.apk is a little more tricky. Check My original Red Dynamite post for instructions.
Your phone might reboot a couple times and/or take a while to boot. Don't freak out just let it do its thing. After that you should be DY-NO-MITE!!
Your using my new swype with the red tracer right?
You know you want me to make an update.zip for this I can hook you up tomorrow or something. or take mine and mod it. I would recommend using 7zip open the zip in and archive then open the apks in an archive and replace the drawable folders with yours. Thats the only way i was able to get it work.
Looks good man. I'm working on my own personal theme (not releasing it) and this gives me a few ideas.
Keep up the good work.
Updated with some stuff that was messed up. If anyone wants to make an update.zip feel free and I will put it in the OP.
that live wallpaper look amazing. can you post the apk for that
Explodee said:
Updated with some stuff that was messed up. If anyone wants to make an update.zip feel free and I will put it in the OP.
Click to expand...
Click to collapse
Here is a link to a blank update.zip. Just download it and drop your updated files in the correct folders and you should be good to go. As mentioned I'd use 7-zip to open it and then just drag and drop your modified *.apks
http://alldroid.org/default.aspx?g=posts&t=855
Update.zip added!!
holy crap your phone is busy looking.
Umm...can we get better links than rapidshare? It keeps falsely telling me that i've used too many free downloads from my IP...and I even tried over 3g...
man I wish this would come to fission.
Explodee said:
Directions
Unzip the contents of Froyo Dynamite.zip and put them on the root of your SD card
Open ADB or Terminal Emulator and input the following commands exactly
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/Music.apk /system/app
cp /sdcard/pandora.apk /system/app
cp /sdcard/Vvm.apk /system/app
cp /sdcard/com.facebook.katana.apk /system/app
cp /sdcard/GoogleQuickSearchBox.apk /system/app
cp /sdcard/BlurHome.apk /system/app
cp /sdcard/Swype.apk /system/app
cp /sdcard/Settings.apk /system/app
cp /sdcard/YouTube.apk /system/app
cp /sdcard/services.jar /system/framework
cp /sdcard/framework-res.apk /system/framework
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
The Fancywidget.apk is a little more tricky. Check My original Red Dynamite post for instructions.
Your phone might reboot a couple times and/or take a while to boot. Don't freak out just let it do its thing. After that you should be DY-NO-MITE!!
Click to expand...
Click to collapse
+++++++++++++++++++++
How do you un-do the prompts that you put in? I cant seem to get the colors to return back to normal (not red). I'm assuming you have to type in more code to get it that way, what do I do?
Does anyone know if this will work with the new .340 OTA?
*Coming soon to Fission
All I did was replace .png files so if you are unsure about whether or not it will work, you can add my png's to your apk's or framework and do it manually.
Explodee said:
*Coming soon to Fission
All I did was replace .png files so if you are unsure about whether or not it will work, you can add my png's to your apk's or framework and do it manually.
Click to expand...
Click to collapse
Hey do you know if this theme will work with the .340 OTA?
Working on that now actually. I don't know if I like Fission
Explodee said:
Working on that now actually. I don't know if I like Fission
Click to expand...
Click to collapse
Thanks! Can't wait!!!!
Any new on when this will be available for the new OTA?
koentopp5 said:
+++++++++++++++++++++
How do you un-do the prompts that you put in? I cant seem to get the colors to return back to normal (not red). I'm assuming you have to type in more code to get it that way, what do I do?
Click to expand...
Click to collapse
Not really sure what you mean. If you want to get rid of this theme you need to replace these Dynamite files with your original files. The code is only copying over your stock stuff, not actually making the changes.
Updated for the 340 OTA! Check the OP. Happy Festivus everyone!!!
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
I am using Magisk 20.4 and trying to mount /system on a Google Pixel running Android 10.
I have tried using:
Code:
adb shell su -c mount -o rw,remount /system
that gives: me
mount: '/system' not in /proc/mounts
Click to expand...
Click to collapse
The following also do not work:
Code:
adb shell su -c mount -o rw,remount /
'/dev/root' is read-only
Click to expand...
Click to collapse
Code:
adb shell su -c mount -o rw,remount /sbin/.magisk/mirror/system_root
'/sbin/.magisk/block/system_root' is read-only
Click to expand...
Click to collapse
I was also curious whether stuff in /sbin/.magisk/rootdir/system/ can actually override stuff in /system/ but that doesn't seem to be the case..
Has anyone managed to mount /system on Android 10? Is this issue specific to Google Pixel?
Cheers,
Paschalis
Its due to EXT4 dedup filesystem (it's not writable).
This was pointed out by magisk developer john wu, more info: https://mobile.twitter.com/topjohnwu/status/1170404631865778177
So it's impossible? Even with TWRP?
Turns out I don't need to mount /system.
I wanted this so I could ship my modified version of libart.so, libart-compiler.so and dex2oat (which are in APEX), as well some other external compiler libraries and tools.
So I've written some magisk modules, and it works really well. Even for the runtime apex. I'm impressed!
The only reason someone might need to mount /system is if he/she uses an app/tool that needs it.
The only way to make changes to the /system partition is to make a Magisk module that mounts the files you modified instead of the original ones.
Paschalis said:
Turns out I don't need to mount /system.
I wanted this so I could ship my modified version of libart.so, libart-compiler.so and dex2oat (which are in APEX), as well some other external compiler libraries and tools.
So I've written some magisk modules, and it works really well. Even for the runtime apex. I'm impressed!
The only reason someone might need to mount /system is if he/she uses an app/tool that needs it.
Click to expand...
Click to collapse
Well I need to mount because of Link2sd. Is there any way to do it?
jcruzcruz35 said:
Well I need to mount because of Link2sd. Is there any way to do it?
Click to expand...
Click to collapse
No, on Android 10 the /system partition is locked at read only, the only way to make modifications to the /system partition is to make a Magisk module.
JJcoder said:
No, on Android 10 the /system partition is locked at read only, the only way to make modifications to the /system partition is to make a Magisk module.
Click to expand...
Click to collapse
Sht, it has to be especially make it for each smartphone? Or you think there gonna be eventually a Module for everyone?
jcruzcruz35 said:
Sht, it has to be especially make it for each smartphone? Or you think there gonna be eventually a Module for everyone?
Click to expand...
Click to collapse
I'm sure eventually there will either be a universal Module, Or a way to resize the partition and change the file system to make it writable.
JJcoder said:
...Or a way to resize the partition and change the file system to make it writable.
Click to expand...
Click to collapse
Resized works, but how to change the file system to make it writable?
vagyula said:
Resized works, but how to change the file system to make it writable?
Click to expand...
Click to collapse
How did you resize it?
Code:
$ su
# mount --remount / -w
ONLY makes effert to terminal, which means other apps like Solid Explorer, Root Explorer etc are still r/o. Some roms(Pixel Experience tested, including stock) are not working.
hardplastic said:
Code:
$ su
# mount --remount / -w
Only works in terminal
Click to expand...
Click to collapse
It doesn't work on Android 10, you will just get the error:
Code:
'/dev/root' is read only
JJcoder said:
It doesn't work on Android 10, you will just get the error:
Code:
mount: '/dev/root' not user user mountable in fstab
Click to expand...
Click to collapse
Reboot your device and try again, it works both two of my devices in Android 10
hardplastic said:
Reboot your device and try again, it works both two of my devices in Android 10
Click to expand...
Click to collapse
Nope, Same error bcuz it is locked at read only.
JJcoder said:
Nope, Same error bcuz it is locked at read only.
Click to expand...
Click to collapse
That's weird, have you checked your operation is in the terminal? It only makes /system rw to terminal, other apps still r/o .
hardplastic said:
That's weird, have you checked your operation is in the terminal? It only makes /system rw to terminal, other apps still r/o .
Click to expand...
Click to collapse
No, you can't just simply Type a command and have it mount as rw...
If you want to make modifications you have to make a Magisk Module which uses Magic Mount to mount the modified files over the original ones.
I have no idea how u got it to work, I would like to see proof..
JJcoder said:
No, you can't just simply Type a command and have it mount as rw...
If you want to make modifications you would have to make a Magisk Module which uses Magic Mount to mount the modified files over the original ones.
Click to expand...
Click to collapse
Then how do you explain that?
{
"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"
}
hardplastic said:
Then how do you explain that?
Click to expand...
Click to collapse
Let me see that u are on stock Android 10
JJcoder said:
Let me see that u are on stock Android 10
Click to expand...
Click to collapse
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