Hello everyone,
I'd like to pay back the community that have been helping me with my cellphone, and also helped me learn a lot on how to help myself.. so i decided to give back.. i have been customizing GB and for my own personal use, now i am trying to customize ICS port by xbsall. the only problem i have is packing the rom in a flashable zip. I searched everywhere with no success all i need is how to pack the system and data to .img file.
I'd appreciate the help and i will be posting my custom rom the forums soon.
Special thanks to xbsall, defcomg, and everyone working on making the ICS possible on the O3D.
You can try this out:
ROM Factory v1.7.1[May/12/2012]
Although P920 isn't on the "Supported Devices" list...
or this:
[KITCHEN] Android Kitchen, v0.214 [Linux / Mac / Windows]
Just be careful.
Mount .IMG As Dir Named system
Code:
mkdir system
sudo mount -t ext4 -o loop system.img system/
New System
Code:
sudo cp -ar system new_system
Create New .img
Code:
sudo ./make_ext4fs -l 700m -a system system.img new_system/system
Source
defcomg said:
Mount .IMG As Dir Named system
Code:
mkdir system
sudo mount -t ext4 -o loop system.img system/
New System
Code:
sudo cp -ar system new_system
Create New .img
Code:
sudo ./make_ext4fs -l 700m -a system system.img new_system/system
Source
Click to expand...
Click to collapse
Thanks guys, I am gonna try and report back..
BadSoul said:
Thanks guys, I am gonna try and report back..
Click to expand...
Click to collapse
I tried those methods and none of it created me a .img packed rom.
Any other suggestions? please
Thank you
BadSoul said:
I tried those methods and none of it created me a .img packed rom.
Any other suggestions? please
Thank you
Click to expand...
Click to collapse
Lets suppose you have made the changes to your system the way you like it. (add/remove apps , etc)
Now in order to make your system.img
boot into cwm/twrp
connect to pc
use the following command to make the img file
adb shell
dd if=/dev/block/mmcblk0p7 of=/emmc/system.img
wait until it ends
your system.img is ready and packed into your emmc
make sure your emmc has plenty of space to fit it
now you can make a zip file with it and use the command
package_extract_file("system.img", "/dev/block/mmcblk0p7");
in your updater script to unpack
happy cooking
_____________________________________________________
the cmd output should look like this
Code:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
~ # cd dev
cd dev
/dev # cd block
cd block
/dev/block # dd if=/dev/block/mmcblk0p7 of=/emmc/system.img
dd if=/dev/block/mmcblk0p7 of=/emmc/system.img
1445274+0 records in
1445274+0 records out
739980288 bytes (705.7MB) copied, 126.201996 seconds, 5.6MB/s
/dev/block #reboot
Thank you very much xbsall. That worked perfectly.
Do you know can i create data.img also? most of my customization is in the data. I'd really appreciate it.
What block is it in?
Thanks for the great work.
mmcblk0p8 is data
Sent from my LG-P920 using xda app-developers app
iodak said:
mmcblk0p8 is data
Sent from my LG-P920 using xda app-developers app
Click to expand...
Click to collapse
Awesome! thanks iodak, xbsall, defcomg and TMProduct1onZ.. I really appreciate the help.
xbsall with dsixda's kitchen would there have to be a new edify_defs created for SU760 if using your XBSA404 port? The reason I am asking is I am getting an error Status 0 when creating a ROM in the kitchen. I think this may be due to the device being ro.product.device=SU760 in build.prop but not having an edify_defs for the SU760? any help appreciated.
Status 0 might be two things: 1) You used an update-script (Amend format, which is very old) when you should be using an updater-script (Edify format), or the other way around; OR 2) Your updater-script is using the "MTD" partition type when mounting a partition rather than another type such as EMMC (and thus, you need the device defined under the kitchen's /tools/edify_defs folder).
Havent used dsixda kitchen for a long long long... long time.
So i cant help you with it.
Tell me what you wanna do to your ROM.
xbsall said:
Havent used dsixda kitchen for a long long long... long time.
So i cant help you with it.
Tell me what you wanna do to your ROM.
Click to expand...
Click to collapse
Just trying to start with a basic platform by de-odexing and zip alligning and build on it from there
dsixda's kitchen seemed like the easiest method and i've managed with some degree of success but required the update binary from other peoples ROM's which I would rather not do.
Lol just adb pull/push them..
xbsall said:
Lol just adb pull/push them..
Click to expand...
Click to collapse
lol thats fine but i'd rather have a flashable zip without having to use others update binary and modified updater script :victory:
---------- Post added at 10:16 PM ---------- Previous post was at 10:13 PM ----------
I'll keep messing around with the kitchen in the meantime :laugh:
BTW that looks tremendous is it ROM: XBSA V3b ICS ROM for Optimus3D P920 with ACiD Audio?
{
"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"
}
Yes its v3b
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 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
*** WARNING: This is a risky procedure that could damage your phone - PROCEED AT YOUR OWN RISK ***
ONLY FOR P690 - NOT P698 OR OTHER DIFFERENT MODELS
for p698 look at this thread : http://forum.xda-developers.com/showpost.php?p=25103749&postcount=1
*** ONLY INSTALL THE LATEST VERSION AVAILABLE ***
Hello everyone,
I've succesfully ported the CyanogenMod Clockworkmod recovery for our *beloved* Net Optimus Some details:
-> REQUIREMENTS:
-- ROOT
-- ADB
-- KNOW HOW TO CHECK THE MD5SUM OF A FILE -> HowToMD5SUM - Guide for Windows and Linux
The Recovery can be installed as follow:
Download recovery.img from the link attachment
IMPORTANT: Check MD5SUM - This is to ensure that during the download / copy the file is not corrupted
Copy recovery.img to the SD
download Flash_image, unzip and copy it to SD
Now you must install the recovery through ADB (the commands must be entered one by one in the shell, waiting a couple of seconds between one and another.
Code:
$ adb shell
# su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
# cat /sdcard/flash_image> /system/bin/flash_image
# chmod 755 /system/bin/flash_image
# mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock1 /system
# flash_image recovery /sdcard/recovery.img
# reboot recovery
Note: the command
Code:
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
could give you an error "File not found", ignore it.
If all goes well, the menu with a cheerful hat ClockworkMod background confirms that the boot recovery occurred in CW.
Also ignore the error below: "E: bad boot message" is not a real error.
The recovery functionality is simple:
- The volume keys to scroll
- The back button to go back
- The power button to select a menu item.
If you have problems, you can select Advanced / Error Reporting. This will generate a log into SD (recovery.log). You can use it to understand the problem.
---------------------------------------- Changelog - --------------------------------------------------------
v1 beta.1 (MD5SUM 5707de3d7463072e3bf9d3c1d6108ef1)
updated to 5.0.2.8
Original Thread : [TEST] Custom Recovery per LG Optimus Net - Clockwork 5.0.2.7 - Androidworld.it
Thanks to:
save80
Disclaimer:
Neither I nor XDA consider ourselves responsible for any damage caused to the telephone,
install this recovery at your own risk.
RELEASES :
5.0.2.8 -> https://rapidshare.com/files/2585790621/recovery.img (258e95cd2a697d902c2c139893d83063)
Please give me feedback about recovery functionalities.
Help me
I'm newbie. I'm using LG Optimus Z, everyone show me install clockworkmod for Optimus Z, please....
Thanks very much.....
---------- Post added at 03:57 PM ---------- Previous post was at 03:40 PM ----------
jst_tsj said:
Post Reserved for future updates.
Please give me feedback about recovery functionalities.
Click to expand...
Click to collapse
Please help me install clockworkmod for LG Optimus Z . Thanks very much...
Every body, help me ,please....
Hmm... no feedback... is it good or bad? Does this works for anybody?
Am gonna try it now hope i dont get bricked!
---------- Post added at 05:17 PM ---------- Previous post was at 05:12 PM ----------
What do you mean by :-
you must install the recovery through ADB (the commands must be entered one by one in the shell, waiting a couple of seconds between one and another.
Click to expand...
Click to collapse
IT WORKED!!!
IT Worked man!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
---------- Post added at 07:41 PM ---------- Previous post was at 06:52 PM ----------
{
"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"
}
Really would like some Nice ROM's and OC kernels plz!!!
can you show some screen shot please
sorry i stuck at $adb remount nothing happen. but it show permission denied
help me please
Seems like you are using windows 7. Ryt click on cmd and run as administrator.
Sent from my LG-P690 using xda premium
Urmas1 said:
Hmm... no feedback... is it good or bad? Does this works for anybody?
Click to expand...
Click to collapse
all worked fine guy
i successfully installed the cwm recovery on my optimus net.....thanks
but i didnt used remount command , when i use this command it says permission denied.. is there any problem?? but cwm is installed
i m unable to flash new ROM by this recovery..... i have tried 4-5 times but it stuck in LG logo then i have to go back to recovery mode and recover to my old firmware...
anybody installed CM7 or other ROMs reply by..
is there any more feedbacks? i would like to use it
work for optimus net dual?
New version available... Sorry I've disappeared, but I'm here again now
could you provide me official kdz of 2.3 please....
Please can we have the new one! thanks
UPDATE
New version available
** Fixed a problem with sd-ext mounting, please update in order to avoid problems with sd-ext partition
recovery link : https://rapidshare.com/files/2585790621/recovery.img
md5sum : 258e95cd2a697d902c2c139893d83063
http://forum.xda-developers.com/showpost.php?p=19626804&postcount=2
jst ive been following your thread for lg optimus net in italian forum and waiting for your best update that less bugs...looking forward to that day
Galaxy Tab 4 7.0 (3G) system dump
~~~~~~~
Apps:
HERE
~~~~~~~
priv-app - folder:
HERE
~~~~~~~
media - folder:
HERE
~~~~~~~
Framework:
HERE
~~~~~~~
lib - folder:
HERE
~~~~~~~
bin - folder:
HERE
~~~~~~~
vendor - folder:
HERE
~~~~~~~
etc - folder:
HERE
~~~~~~~
recovery.img:
(I´m not sure if this image is working please give feedback)
HERE
~~~~~~~
boot.img:
(I´m not sure if this image is working please give feedback)
HERE
~~~~~~~
build.prop:
HERE
~~~~~~~
Note: I´m not responsible for any damage to your device
~~~~~~~
Wrong device ?
Galaxy Tab 4 10.1 dump here
Galaxy Tab 4 8.0 dump Coming soon
Make your own dumps Coming soon
Thank you so much bro
Waiting for this \m/
Sent from an expensive Toaster (SM-T211)
Boot
Hey I'm trying to make a boot.img dump myself. Did you find out if you dumped the right mount point? I downloaded Partition Table from the play store and it shows all the mount points but I'm not sure which one is the boot. It doesn't actually specify a boot partition and if i go into the /dev/block/platform/soc,2/by-name folder it doesn't have a boot file in there or an aboot file. So I'm confused.
ubuntu is the solution
TheOriginalist said:
Hey I'm trying to make a boot.img dump myself. Did you find out if you dumped the right mount point? I downloaded Partition Table from the play store and it shows all the mount points but I'm not sure which one is the boot. It doesn't actually specify a boot partition and if i go into the /dev/block/platform/soc,2/by-name folder it doesn't have a boot file in there or an aboot file. So I'm confused.
Click to expand...
Click to collapse
Hey,
I can't help you with that using a phone.
I have done this multiple times using Ubuntu.
PHP:
sudo apt-get install abootimg
sudo abootimg -x boot.img
mkdir workspace
cd workspace
gzip -cd initrd.img | cpio -i
I could upload the dump, too !?
UAdeveloper said:
Hey,
I can't help you with that using a phone.
I have done this multiple times using Ubuntu.
PHP:
sudo apt-get install abootimg
sudo abootimg -x boot.img
mkdir workspace
cd workspace
gzip -cd initrd.img | cpio -i
I could upload the dump, too !?
Click to expand...
Click to collapse
Wait I don't quite understand did you successfully dump the boot img from the tablet? Cause it looks like your just making a boot img there (not too linux friendly I mainly use windows)
TheOriginalist said:
did you successfully dump the boot img from the tablet?
Click to expand...
Click to collapse
Yes (using the linux method) ...
Do you need it? I could upload it tomorrow
Hi, all I really need is the keyboard files but, I cannot see the files. I can ony see so many and the list cuts off. Also, I cannot download the .zips. Is there any way you could just link me to the keyboard files, please?
{
"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"
}
UAdeveloper said:
Wrong device ?
Galaxy Tab 4 10.1 dump here
Galaxy Tab 4 8.0 dump Coming soon
Make your own dumps Coming soon
Click to expand...
Click to collapse
still waiting for 'make your own dumbs'
bubenking said:
still waiting for 'make your own dumbs'
Click to expand...
Click to collapse
I don`t work with Samsung Tab´s anymore, sorry.
If someone wants me to link him to his work, pm me.
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