I posted this question in several threads and I got no answer, so once again, can someone post here a boot.img from stock rom, base 1.18, or a boot.img from nand backup of the same rom. I''m interested only for boot.img from STOCK rom, not from custom rom that can be obtained here on forum?
If someone has factory rom on his/her phone and he installed custom recovery and rooted it, please make a nand backup and post me boot.img from backup.
Thanks in advance.
So, nobody willing to help?
I'm sorry man, don't know how I could get it, I already flashed sense revo R3 :l
Sent from my awesome fridge
Thank's anyway.
However you can help me in another way. First a question, can you remove apps from system partition without reappearing after reboot? Then, did you flash boot.img separately from fastboot or you just flashed the rom.zip? And when you give me the answers, can you post me a file located on the system root of phone (the same location where system, data, sdcard and the rest of the stuff is mounted) called default.prop?
nlooooo said:
I posted this question in several threads and I got no answer, so once again, can someone post here a boot.img from stock rom, base 1.18, or a boot.img from nand backup of the same rom. I''m interested only for boot.img from STOCK rom, not from custom rom that can be obtained here on forum?
If someone has factory rom on his/her phone and he installed custom recovery and rooted it, please make a nand backup and post me boot.img from backup.
Thanks in advance.
Click to expand...
Click to collapse
here u go bro. as requested, its stock rom base 1.18, customer recovery and rooted.
Yup, will do, but it'll take some time, just coming back from iceskating.
Sent from my awesome fridge
MaartenXDA said:
Yup, will do, but it'll take some time, just coming back from iceskating.
Sent from my awesome fridge
Click to expand...
Click to collapse
I think I'm getting somewhere, now I need your stuff to post me.
And I'm sure you've made a nand backup of your current rom so if you're willing post me your boot.img from the backup, not from the rom I already have it.
Don't have a backup
But the system app removal worked.
I'm on Sense Revolution R3, used aroma file manager 1.80 to remove the files, worked like a charm.
Sent from my awesome fridge
MaartenXDA said:
Don't have a backup
But the system app removal worked.
I'm on Sense Revolution R3, used aroma file manager 1.80 to remove the files, worked like a charm.
Sent from my awesome fridge
Click to expand...
Click to collapse
Aroma yes, but how about using Titanium Backup, wipe data first, then uninstall and reboot? The point is to do it when phone booted.
And I need that default.prop, please.
nlooooo said:
Aroma yes, but how about using Titanium Backup, wipe data first, then uninstall and reboot? The point is to do it when phone booted.
And I need that default.prop, please.
Click to expand...
Click to collapse
Here it is, sorry had to use .zip, .prop is invalid
No doesn't work with titanium and delete data.
Then it's not a problem with secure kernel, cause you boot with unsecure, this is from your default.prop
ro.secure=0
Click to expand...
Click to collapse
so this means that you successfully flashed boot.img when you flasher rom. Have you ever flashed it separetely, I mean when you installed previous versions of rom?
And one more question which SU app do you have Superuser on SuperSU?
nlooooo said:
Then it's not a problem with secure kernel, cause you boot with unsecure, this is from your default.prop
so this means that you successfully flashed boot.img when you flasher rom. Have you ever flashed it separetely, I mean when you installed previous versions of rom?
And one more question which SU app do you have Superuser on SuperSU?
Click to expand...
Click to collapse
Yeah, I flashed the one with R1 or R2, to fix the WiFi bug.
MaartenXDA said:
Yeah, I flashed the one with R1 or R2, to fix the WiFi bug.
Click to expand...
Click to collapse
So definitely, boot.img flashing via recovery is mandatory to get it all working.
Apps uninstalling still looks kinda weird to me. You didn't tell me about SU app.
@nlooooo
Do you still want the boot.img that not yet go thru android kitchen ?
I have one that in CWM backup.
ckpv5 said:
@nlooooo
Do you still want the boot.img that not yet go thru android kitchen ?
I have one that in CWM backup.
Click to expand...
Click to collapse
Thanks but I've already got it, I unpacked it to see default.prop settings, but it all seems that uninstalling of system apps doesn't depend on the way how kernel boots, even if it boots as unsecure apps still can't be uninstalled.
However I confirmed my claims that boot.img can't be flashed installing rom, only via fastboot.
Yep.. correct.
What I notice is the system/app folder's permission is rwxr-xr-x instead of the normal rwxrwxrwx and I can't find where the permission is set.
ckpv5 said:
Yep.. correct.
What I notice is the system/app folder's permission is rwxr-xr-x instead of the normal rwxrwxrwx and I can't find where the permission is set.
Click to expand...
Click to collapse
Maybe it's set here in ramdisk in int.protou.rc
on emmc
mkdir /system
mkdir /data 0771 system system
mkdir /cache 0770 system cache
mkdir /devlog 0700 root root
devwait [email protected]
mount ext4 [email protected] /system ro barrier=1
devwait [email protected]
# exec /system/bin/e2fsck -p [email protected]
mount ext4 [email protected] /data nosuid nodev barrier=1 noauto_da_alloc
mount ext4 [email protected] /cache nosuid nodev barrier=1
mount ext4 [email protected] /devlog nosuid nodev barrier=1
I'm not a programmer so I dont know, or maybe in init.rc.
Related
Sorry if it is a silly question. I am new to installing new ROM and flashing stuff. I have come across the thread on TWRP recovery where it says that to install it, we have to flash it from other recoveries(i.e. CWM or AmonRA). What if I have none of these? Should I install one of them at first place and then proceed to flash TWRP or, there is some other way out? Thanks.
flash_image, Flash Image GUI, fastboot, another recovery, LGMDP.exe for unrooted phones. Read the sticky threads.
Sent from my LG-P500 using XDA App
dr.notor said:
flash_image, Flash Image GUI, fastboot, another recovery, LGMDP.exe for unrooted phones. Read the sticky threads.
Sent from my LG-P500 using XDA App
Click to expand...
Click to collapse
Thanks Sir for your quick response. Will go through it.....
developer++ said:
Sorry if it is a silly question. I am new to installing new ROM and flashing stuff. I have come across the thread on TWRP recovery where it says that to install it, we have to flash it from other recoveries(i.e. CWM or AmonRA). What if I have none of these? Should I install one of them at first place and then proceed to flash TWRP or, there is some other way out? Thanks.
Click to expand...
Click to collapse
root using gingerbreak,download latest rom manger and install clockwork recovery from there - if want to change reovery to twrp just flash from clockowrk recovery after it gets installed
this may help u http://forum.xda-developers.com/showthread.php?t=1038338
make sure usb debugging is enabled while installing custom recovery from rom manger ,make sure u download the latest rom manger from market
welcome to world of custom rom
shhbz said:
root using gingerbreak,download latest rom manger and install clockwork recovery from there - if want to change reovery to twrp just flash from clockowrk recovery after it gets installed
this may help u http://forum.xda-developers.com/showthread.php?t=1038338
make sure usb debugging is enabled while installing custom recovery from rom manger ,make sure u download the latest rom manger from market
welcome to world of custom rom
Click to expand...
Click to collapse
Thanks for the info. Was really a nice descriptive guide for newbies.
One more question. I am on stock froyo 2.2.2 and have flashed TWRP recovery which creates partition in ext4 only. Now I have also flashed Darktremor A2SD which fails to move dalvik to sd card which I assume is because of the ext4 partition that is not recognised by the stock rom. Am I correct with my assumption?
Is flashing another rom is the only way out? If yes, how should I move the existing apps from my stock rom to the new row. Thanks.
Code:
cat /proc/filesystems
will tell you what your kernel supports.
shhbz said:
root using gingerbreak,download latest rom manger and install clockwork recovery from there - if want to change reovery to twrp just flash from clockowrk recovery after it gets installed
this may help u http://forum.xda-developers.com/showthread.php?t=1038338
make sure usb debugging is enabled while installing custom recovery from rom manger ,make sure u download the latest rom manger from market
welcome to world of custom rom
Click to expand...
Click to collapse
This method is not quite OK for me. Did anyone try to actually install that recovery using "Phone Terminal Emulator method"?
I mean this.
adb shell
su (it will ask for root permission in your phone screen just allow)
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 (you will get an error just proceed)
mount -o remount,ro -t yaffs2 /dev/block/mtdblock1 /system
flash_image recovery /sdcard/LGp500-recovery-v12.img (note just name the blue marked as the same as your custom recovery name and should end with .img)
Click to expand...
Click to collapse
Martin "skunk" Rotter said:
This method is not quite OK for me. Did anyone try to actually install that recovery using "Phone Terminal Emulator method"?
I mean this.
Click to expand...
Click to collapse
Click the link in my signature. There are 3 perfectly working methods to flash recovery. Dunno what the problem really is.
Well, if course i know these methods and i used it many times. Maybe author of this (extremely interesting and incredibly looking) recovery could mention these methods in his thread. I think that only "flash this ZIP via your CWM"-like tutorial is not enough for some users and then they are confused -> and then new threads like this are created.
Martin "skunk" Rotter said:
Well, if course i know these methods and i used it many times. Maybe author of this (extremely interesting and incredibly looking) recovery could mention these methods in his thread. I think that only "flash this ZIP via your CWM"-like tutorial is not enough for some users and then they are confused -> and then new threads like this are created.
Click to expand...
Click to collapse
That thread is a development thread for that particular recovery. There is absolutely no difference when flashing this or another recovery (like AmonRa or CWM.) So, there are enough howtos here (mentioned in the sticky thread that noone reads) to cover flashing recovery.
Development section is for development, not for repeating redundant stuff over and over again.
I get it, but obvíously developer++ doesn't.
Martin "skunk" Rotter said:
This method is not quite OK for me. Did anyone try to actually install that recovery using "Phone Terminal Emulator method"?
I mean this.
Click to expand...
Click to collapse
well that an outdated mwthod and a lengthy procedure so why not use rom manger and get the latest clockwork recovery and easily shift to whichever recovery u are wiling to use
shhbz said:
well that an outdated mwthod and a lengthy procedure so why not use rom manger and get the latest clockwork recovery and easily shift to whichever recovery u are wiling to use
Click to expand...
Click to collapse
There is nothing outdated about the method. And why not use ROM Manager? Because ROM Manager absolutely lacks any sanity checks when flashing recovery. It will happily download incomplete *.img (happens a LOT esp. on 2G/3G) and flash it, making your phone stuck with fastboot.
I have mentioned numerous times that they should distribute a signed ZIP with recovery contained and check the ZIP before flashing. (Even the ZIP format itself has a CRC checks built in if you are too lazy to bother with manifests.)
There are tons of complaints from people all over the board about ROM Manager half-bricking their phones, I am really stunned by the bad design of the feature and lack of action to fix it.
shhbz said:
well that an outdated mwthod and a lengthy procedure so why not use rom manger and get the latest clockwork recovery and easily shift to whichever recovery u are wiling to use
Click to expand...
Click to collapse
Well, but don't you see that problem?
get the latest clockwork recovery and easily shift to whichever recovery u are wiling to use
Click to expand...
Click to collapse
Why this? Some say usual recovery installation methods will work and you say to use this (weird) method. Then you can't wonder, why creator of this thread is confused.
dr.notor said:
There is nothing outdated about the method. And why not use ROM Manager? Because ROM Manager absolutely lacks any sanity checks when flashing recovery. It will happily download incomplete *.img (happens a LOT esp. on 2G/3G) and flash it, making your phone stuck with fastboot.
I have mentioned numerous times that they should distribute a signed ZIP with recovery contained and check the ZIP before flashing. (Even the ZIP format itself has a CRC checks built in if you are too lazy to bother with manifests.)
There are tons of complaints from people all over the board about ROM Manager half-bricking their phones, I am really stunned by the bad design of the feature and lack of action to fix it.
Click to expand...
Click to collapse
yes the problem was there of phone getting into fastboot mode ,but i beieve the problem was later solved and then it worked fine as many users dont follow instruction carefully which land them into probs.yes i do agree on ur internet connection part if that lacks than they need to use adb to get it done.
since,many users are not able to use adb and stuff just bcoz they cannot configure it properly.
so they have these option to do it the easiest way if they are not able to configure adb to work properly.
shhbz said:
yes the problem was there of phone getting into fastboot mode ,but i beieve the problem was later solved and then it worked fine as many users dont follow instruction carefully which land them into probs.yes i do agree on ur internet connection part if that lacks than they need to use adb to get it done.
Click to expand...
Click to collapse
I do not believe they ever changed the ROM Manager design in the way suggested. The problem is with lack of sanity checks, do not blame users for their sucky internet connection.
Martin "skunk" Rotter said:
Well, but don't you see that problem?
Why this? Some say usual recovery installation methods will work and you say to use this (weird) method. Then you can't wonder, why creator of this thread is confused.
Click to expand...
Click to collapse
It depends on the users choice what they choose as we started with thunderg recovery than came the clockwork method and now the twrp method.
there are various threads and discussion on the first two method .
go and read threads as i said is a matter of choice which way u want it to get it done.
so make ur choice in which u are comfortable and confident.
dr.notor said:
Code:
cat /proc/filesystems
will tell you what your kernel supports.
Click to expand...
Click to collapse
the above command gives me the following output:
Code:
cat /proc/filesystems
nodev sysfs
nodev rootfs
nodev bdev
nodev proc
nodev tmpfs
nodev debugfs
nodev sockfs
nodev pipefs
nodev anon_inodefs
nodev rpc_pipefs
nodev inotifyfs
nodev devpts
ext3
ext2
nodev ramfs
vfat
nodev nfs
yaffs
yaffs2
as seen my kernel does not support ext4.
dr.notor said:
Click the link in my signature. There are 3 perfectly working methods to flash recovery. Dunno what the problem really is.
Click to expand...
Click to collapse
Yes, I have been following links from your signature. They are perfectly ok. But the situation I got into was that I flashed TWRP recovery and created a ext4 partition which was the only format supported by TWRP. Then I flashed Darktremor A2SD but it was unable to mount the ext4 partition as such was unable to move dalvik to sd.
Martin "skunk" Rotter said:
Well, if course i know these methods and i used it many times. Maybe author of this (extremely interesting and incredibly looking) recovery could mention these methods in his thread. I think that only "flash this ZIP via your CWM"-like tutorial is not enough for some users and then they are confused -> and then new threads like this are created.
Click to expand...
Click to collapse
Yes, I too think an additional info about the other ways to install recovery as stated by dr.notor would be very much helpful.
And as for creating new threads I sincerely apologize if I have a made a mistake here.
Flash the correct franco kernel, it supports ext4 just fine. (v1 versions are for CM7 6.6.x and stock(-based) GB ROMs only!)
What is this?
These are pre-rooted Stock ROM Base's for Developer to use to create modified stock ROMs or for the average Joe to restore their device's to working order if they are stuck in a bootloop. You must have an unlocked bootloader and a working Custom Recovery to use this.
Downloads:
T-Mobile / Retail US - 139.11.6 - Odex ***Tested, will not go past the boot logo.
Instructions:
Put the .zip on your internal storage.
Boot up to your Custom Recovery of choice (example: Clockworkmod Recovery).
Make a complete backup of your device using the Custom Recovery, and store that backup on a computer or alternative storage.
Wipe data using the Custom Recovery.
Mount system using the Custom Recovery.
Format system using the Custom Recovery.
Install the .zip from your internal storage using the Custom Recovery.
Reboot and enjoy! (If it asks to disable recovery install, tell it not to.)
Thanks:
My testers.
The Firmware Team.
mhous33 for the base script/binary for the RAZR M DST ROM.
I'll try to get some more bases up since we now have the means to install them and have them working correctly.
Amazing!
Thanks alot man. Never hurts to have an extra backup on my Google Drive or something should the worst happen.
Flashing in 15 minutes or so, when it's done downloading.
THANK YOU for this!
I'll need the /tmp/recovery.log after the flash if anyone could provide it
Something isn't going right so I'll need it to see what isn't.
Sent from my SGH-M919 using Tapatalk 2
mattlgroff said:
I'll need the /tmp/recovery.log after the flash if anyone could provide it
Something isn't going right so I'll need it to see what isn't.
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
It's not booting, so I can't retrieve the file you need. Adb won't detect the device
Gonna have to restore my backup.
[edit] actually ADB is seeing it once I go to recovery... how do I retrieve the file you need?
figured it out, here is the file you requested: https://www.dropbox.com/sh/l2s290vdcokf38i/Ej6iIe2dqK
Extracted using adb while phone was in recovery, after flashing your file. Have to restore now =P
Thanks! Working on it.
Sent from my SGH-M919 using Tapatalk 2
mattlgroff said:
Thanks! Working on it.
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
Cheers. I can test the revised ROM whenever it's ready =)
Thanks again for your troubles, this will be the stepping stone all the ROM Cooks have been waiting for!
scorpion667 said:
Cheers. I can test the revised ROM whenever it's ready =)
Thanks again for your troubles, this will be the stepping stone all the ROM Cooks have been waiting for!
Click to expand...
Click to collapse
Updated the file, same link as OP.
I'll probably need the /tmp/recovery.log again if it fails.
Code:
adb pull /tmp/recovery.log
Thanks
mattlgroff said:
Updated the file, same link as OP.
I'll probably need the /tmp/recovery.log again if it fails.
Code:
adb pull /tmp/recovery.log
Thanks
Click to expand...
Click to collapse
On it. download eta 20 mins
No luck. Uploaded the new recovery.log https://www.dropbox.com/sh/l2s290vdcokf38i/Ej6iIe2dqK
Let me know if you need any other files/logs off the phone.
would a copy of my nandroid backup help you at all?
[Breakthrough?] After flashing your ROM I did Advanced Restore and selected to ONLY restore System (from my backup) and I managed to boot! No FC or anything - seems to work perfect. I suppose that's where the problem lies? [sidenote: I always follow the instructions in OP for flashing your ROM i.e wipe data, mount system, format system, just thought I'd mention I'm not taking any shortcuts]
I dunno when I flash the ROM it does it a little too fast (under 5s?)... faster than it took my N4 to flash a 96MB Rom lol. I wonder if it's writing to system at all.
It did that for me on the first rom, I don't know if Matt put something in the build prop to differentiate it from the stock rom
Sent on my Moto X
scorpion667 said:
On it. download eta 20 mins
No luck. Uploaded the new recovery.log https://www.dropbox.com/sh/l2s290vdcokf38i/Ej6iIe2dqK
Let me know if you need any other files/logs off the phone.
would a copy of my nandroid backup help you at all?
[Breakthrough?] After flashing your ROM I did Advanced Restore and selected to ONLY restore System (from my backup) and I managed to boot! No FC or anything - seems to work perfect. I suppose that's where the problem lies? [sidenote: I always follow the instructions in OP for flashing your ROM i.e wipe data, mount system, format system, just thought I'd mention I'm not taking any shortcuts]
I dunno when I flash the ROM it does it a little too fast (under 5s?)... faster than it took my N4 to flash a 96MB Rom lol. I wonder if it's writing to system at all.
Click to expand...
Click to collapse
Sounds like its not flashing to system at all
Shame the log isn't saying what is wrong with the ROM zip. Heck its not even showing it attempting to install the zip at all!
No sense.
Sent from my SGH-M919 using Tapatalk 2
Could it be a recovery issue? The updater script looks way different than what I usually see, normally the system is formated and flashed , sym links, permissions and finally the kernel is flashed
Sent from my A2109A using Tapatalk 4
flashallthetime said:
Could it be a recovery issue? The updater script looks way different than what I usually see, normally the system is formated and flashed , sym links, permissions and finally the kernel is flashed
Sent from my A2109A using Tapatalk 4
Click to expand...
Click to collapse
If Superuser.zip flashes its the ROM.zip as the issue.
Sent from my SGH-M919 using Tapatalk 2
New updater script?
There's missing files also meta-inf folder?
Sent from my A2109A using Tapatalk 4
flashallthetime said:
New updater script?
There's missing files also meta-inf folder?
Sent from my A2109A using Tapatalk 4
Click to expand...
Click to collapse
Once an OTA update comes out for any Moto X variant we'll have a much better idea of the META-INF folder as a whole. In the meantime everyone feel free to keep playing with it to try to get it to work right. Making small updater-script changes to re-upload the entire ROM.zip is a huge pain. Soon enough we'll have the Dev Edition and more Developers will be joining us to get everything squared away.
Thanks testers!
What is the filesystem it (Moto X)?
Jovistyle said:
What is the filesystem it (Moto X)?
Click to expand...
Click to collapse
Code:
# mount point fstype device [device2] [length=]
/boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot
/cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache
/recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery
/sdcard datamedia /dev/null
/data f2fs /dev/block/platform/msm_sdcc.1/by-name/userdata
/system ext4 /dev/block/platform/msm_sdcc.1/by-name/system
/modem ext4 /dev/block/platform/msm_sdcc.1/by-name/modem
/customize ext4 /dev/block/platform/msm_sdcc.1/by-name/customize
These,
seems pretty solid my co-worker tried it an seems great now
BLKWIDOW said:
seems pretty solid my co-worker tried it an seems great now
Click to expand...
Click to collapse
Wait, so it works now?
Sent from my XT1058 using Tapatalk 2
Is it deodex? No biggy if its not. Download link? Fantastic, getting flashing widthdrawls, shaking and i can't sleep at night
Sent on my Moto X
I have tried a lot of custom Roms. I'm on Neat ROM Lite now. Not sure which ROM changed my file access permission settings to cause this problem but I'm not able to delete any files from my external memory card. I was able to delete when I was on stock rom. The other problem is for a few apps I get an error message which says can't install on usb/sd card. I have posted this in another thread
some time back but got no response. Some one please point me in the right direction.
This is what my file permission looks like.
PS: I am able to delete when my fone is connected to PC via USB. So I don't think it has anything to do with a faulty sd card.
pavitar said:
I have tried a lot of custom Roms. I'm on Neat ROM Lite now. Not sure which ROM changed my file access permission settings to cause this problem but I'm not able to delete any files from my external memory card. I was able to delete when I was on stock rom. The other problem is for a few apps I get an error message which says can't install on usb/sd card. I have posted this in another thread
some time back but got no response. Some one please point me in the right direction.
This is what my file permission looks like.
PS: I am able to delete when my fone is connected to PC via USB. So I don't think it has anything to do with a faulty sd card.
Click to expand...
Click to collapse
file permissions are 775, try changing them to 777(all boxes ticked)
for future refference he is my support thread Ricky310711 AllInOne Support Thread
ricky310711 said:
file permissions are 775, try changing them to 777(all boxes ticked)
for future refference he is my support thread Ricky310711 AllInOne Support Thread
Click to expand...
Click to collapse
Can you please tell me, how to apply a file permission? I tried checking the box which is not checked in the snapshot shared, but that too gives an error.Says "Operation failed"
pavitar said:
Can you please tell me, how to apply a file permission?
Click to expand...
Click to collapse
download mobile terminal from playstore
Hey I know its been quite sometime now.but as ur advice I downloaded mobile terminal and now have to run the following command everytime I boot my fone:
mount -o rw,remount -t/yaffs2 /storage/extSdCard
Otherwise i do not get rw access to my external sd.Istn't there a permanent solution to this? Also I fail to understand what changed my permissions and why does this persist across all the new roms I flash?
Sent from my GT-I9100 using xda app-developers app
Wanamlite ->Slim Bean 4.2.2 ->NeatRom Lite -> wanamlite
pavitar said:
Hey I know its been quite sometime now.but as ur advice I downloaded mobile terminal and now have to run the following command everytime I boot my fone:
mount -o rw,remount -t/yaffs2 /storage/extSdCard
Otherwise i do not get rw access to my external sd.Istn't there a permanent solution to this? Also I fail to understand what changed my permissions and why does this persist across all the new roms I flash?
Sent from my GT-I9100 using xda app-developers app
Wanamlite ->Slim Bean 4.2.2 ->NeatRom Lite -> wanamlite
Click to expand...
Click to collapse
Create a blank file and type that command in it. Now save it and rename it to 95mountsd with no extension
Now, if you have init.d support, place it in /system/etc/init.d and reboot
Command will run on every boot itself
Thank you, it worked. Now could please have a look at my other issue, in this post I'd be really thankful.
Can you please tell me what could be the reason for my default rw settings to change, coz I remember when I had stock os I never had to do all this.
iamareebjamal said:
Create a blank file and type that command in it. Now save it and rename it to 95mountsd with no extension
Now, if you have init.d support, place it in /system/etc/init.d and reboot
Command will run on every boot itself
Click to expand...
Click to collapse
pavitar said:
Thank you, it worked. Now could please have a look at my other issue, in this post I'd be really thankful.
Can you please tell me what could be the reason for my default rw settings to change, coz I remember when I had stock os I never had to do all this.
Click to expand...
Click to collapse
Sorry, i'm not good at hardware stuff
Maybe the ROMs aren't mounting that special kind of partition your sdcard is having
FAT32 format works universally
yaffs2 may not
I'm not sure
iamareebjamal said:
Sorry, i'm not good at hardware stuff
Maybe the ROMs aren't mounting that special kind of partition your sdcard is having
FAT32 format works universally
yaffs2 may not
I'm not sure
Click to expand...
Click to collapse
Hey I have switched back to stock rom and I've rooted it by flashing philz kernel. Now I don't see init.d in my /system/etc , where do I place this 95mountsd in this case?
pavitar said:
Hey I have switched back to stock rom and I've rooted it by flashing philz kernel. Now I don't see init.d in my /system/etc , where do I place this 95mountsd in this case?
Click to expand...
Click to collapse
Try this
https://play.google.com/store/apps/...&utm_medium=organic&utm_term=universal+init.d
Hi there!
Today I finally found how to make our codinas' kernels universal, i.e. allow to install kernel on whatever ROM and finally separate recovery from kernel. It's well known, bootloader decides what will be loaded - kernel or recovery. That probably may explain why AnyKernel installer(or other similar) doesn't work on codina, because we can't move recovery partition anywhere.
But there is also a little trick that allow us load recovery and boot.cpio from different partition - https://github.com/ChronoMonochrome/Chrono_Kernel/commit/df9094f1f12618ad9599da266792d6b2f8106170 - just an another approach
Don't worry, we won't touch bootloader at all.
As can be seen, /dev/block/mmcblk0p17 (kernel2 partition) will be used for storing recovery.cpio and boot.cpio. On stock that may not work (I don't know for what exactly uses Kernel2 partition, besides of manually restoring of kernel1 partition. I only know that is almost useless on custom ROMs, and we can use it as we want )
First do some preparations:
Download this kernel and needed recovery/boot scripts(4.4.x.cpio.zip, 4.4.x_f2fs.cpio.zip, etc... 4.4.x.cpio means that it support only ext4) from my google drive (folder ramdisks), unzip recovery (twrp or cwm) and rename to recovery.cpio, then move it to external SD card. Then do it with boot scripts that you've downloaded (e.g. 4.4.x_f2fs.cpio.zip - unzip and rename to boot.cpio)
Well, that all that needs for installation. Read following instruction very carefully, otherwise that may cause brick Keep in mind, all that you do at your own risk! I'm not responsible if you brick your phone!
Installation method:
1) reboot into recovery, plug your phone to your PC, enable adb:
Code:
adb shell
2) Format kernel2 partition to ext4 file system:
Code:
mke2fs -T ext4 /dev/block/mmcblk0p17
Think twice before you hit 'enter' button - wrong command may cause hardbrick!
3) create /ramdisk folder and mount kernel2 partition
Code:
mkdir /ramdisk
mount -t ext4 /dev/block/mmcblk0p17 /ramdisk
move your recovery.cpio and boot.cpio to this folder, give 777 permissions:
Code:
chmod 777 /ramdisk/recovery.cpio
chmod 777 /ramdisk/boot.cpio
4) install downloaded kernel
Now you can change recovery via changing /ramdisk/recovery.cpio - just make a backup of this file, and then replace with one of another recoveries. If you want to install another ROM or change filesystem of partition then replace /ramdisk/boot.cpio with one of needed boot scripts. Don't forget to give 777 permission (probably 644 is enough, but I didn't test it) to both of these files.
This method tested and working on 4.4.x TC ROM + twrp recovery + kernel with full F2FS support.
Well, now it's time to create uncompressed kernel, that may slightly decrease the boot time
@ChronoMonochrome
Thanks. do you mean that kernel2 partition is useless in stock and cyanogenmod firmware?
Is it right that boot loader will read kernel1 partition then it will read system partition? and kernel2 is not necessary for booting?
I have installed new universal kernel (2.5) , so I flashed new ramdisk for 4.4.x , can I roll back to older versions or stock firmware with this ramdisk or I should restore Partition17 backup?
sorset said:
@ChronoMonochrome
Thanks. do you mean that kernel2 partition is useless in stock and cyanogenmod firmware?
Click to expand...
Click to collapse
As it turned out, it's unneeded even on stock. So if you won't restore kernel2 partition, nothing will happen.
Is it right that boot loader will read kernel1 partition then it will read system partition? and kernel2 is not necessary for booting?
I have installed new universal kernel (2.5) , so I flashed new ramdisk for 4.4.x , can I roll back to older versions or stock firmware with this ramdisk or I should restore Partition17 backup?
Click to expand...
Click to collapse
Yes, you can roll back to usual kernels. it doesn't matter what written on kernel2 partition - real kernel or anything else...
ChronoMonochrome said:
As it turned out, it's unneeded even on stock. So if you won't restore kernel2 partition, nothing will happen.
Click to expand...
Click to collapse
Ok, thanks , But why do you mount kernel2 partition inside of OS? As I understand boot.cpio is necessary before booting OS . And inside of OS is just an extra storage! (is that true?)
sorset said:
And inside of OS is just an extra storage! (is that true?)
Click to expand...
Click to collapse
Yes and no, is 16 Mb big enough to be called "storage"? I did it, just to be able replace ramdisks even without booting to recovery. But newest boot scripts doesn't have it.
Ace 2 has 15 - 20 Partitions my Friend
ace2nutzer said:
Ace 2 has 15 - 20 Partitions my Friend
Click to expand...
Click to collapse
And what ? We actually talking about kernel2 partition.
ChronoMonochrome said:
And what ? We actually talking about kernel2 partition.
Click to expand...
Click to collapse
sorry, i meant @sorset
ChronoMonochrome said:
Yes and no, is 16 Mb big enough to be called "storage"? I did it, just to be able replace ramdisks even without booting to recovery. But newest boot scripts doesn't have it.
Click to expand...
Click to collapse
You are right , but I remember days that 1.44MB floppy disk was a large STORAGE and 16MB was HUGE
sry , I have another question , So can I remove its line from fstab to prevent mounting?
I'm confused
boot.img in kernel archive is recovery image that will extract on partition15 (kernel) , but what recovery.cpio exactly is that yu copy on partition17 (kernel2) ?
ace2nutzer said:
Ace 2 has 15 - 20 Partitions my Friend
Click to expand...
Click to collapse
Yes,With counting internal storage , 17 exactly , but thats not the point , I'm afraid.
sorset said:
sry , I have another question , So can I remove its line from fstab to prevent mounting?
Click to expand...
Click to collapse
just redownload bootscripts(kernel/ramdisks), as I said, newest scripts doesn't mount kernel2 partition.
boot.img in kernel archive is recovery image that will extract on partition15 (kernel) , but what recovery.cpio exactly is that yu copy on partition17 (kernel2) ?
Click to expand...
Click to collapse
I don't get it rephrase please
ChronoMonochrome said:
just redownload bootscripts(kernel/ramdisks), as I said, newest scripts doesn't mount kernel2 partition.
I don't get it rephrase please
Click to expand...
Click to collapse
I didn't too
There is an Image named boot.img in kernel flashable zip archive that extracts into partition 15 (named kernel) as I understood is recovery (TWRP or CWM) image and you wont touch linux orginal image , and your modified custom kernel is new modules for linux image that loads while booting (sry, I cant explain fine), So what is recovery.cpio that is in recovery flashable zip image that extracts into partition 17 (named kernel2) ?
sorset said:
as I understood is recovery (TWRP or CWM) image and you wont touch linux orginal image
Click to expand...
Click to collapse
originally kernel + recovery
, and your modified custom kernel is new modules for linux image that loads while booting (sry, I cant explain fine), So what is recovery.cpio that is in recovery flashable zip image that extracts into partition 17 (named kernel2) ?
Click to expand...
Click to collapse
In my mod kernel(mmcblk0p15) and recovery (mmcblk0p17) are splitted.
Thank you. I see.
This is probably the best (and only?) way to rebuild the ramdisk without having to compile anything, which is an excellent base for my NoUMS patches
:good:
<remove>
Build.prop file accidentally got empty and haven't rebooted yet. Any ways to restore it?
Am i screwed?
You have a customer recovery? Then you can dirty flash your rom
I definitely would have done that if i did.
But TWRP was never released for my phone (poco x3 gt)
Depends the device and android version I guess...
I would do getprop and edit the output to build.prop form.
Notice to chmod the file correctly, 644 or whatever..
I think you can reboot safely because build.prop is inside super partition and therefore read-only.
of course you can download stock ROM from xiaomifirmwareupdater and extract build.prop from super.img, but it's more easy to flash super.img from fastboot.
aIecxs said:
I think you can reboot safely because build.prop is inside super partition and therefore read-only.
of course you can download stock ROM from xiaomifirmwareupdater and extract build.prop from super.img, but it's more easy to flash super.img from fastboot.
Click to expand...
Click to collapse
Nvm my phone just got an OTA update.
I just have to restore the root now
aIecxs said:
I think you can reboot safely because build.prop is inside super partition and therefore read-only.
Click to expand...
Click to collapse
And it's empty like how? Weird crap anyway... ok now, so who cares...
Idk but /system /vendor /product /system_ext /odm are ro dynamic partitions inside super partition, either OP did re-duplicate blocks with e2fsck -E unshare_blocks and disabled avb/dm-verity to allow remount rw / system_root (would break OTA), or it simply wasn't written to build.prop at all (magisk systemless overlay)? "empty" could also mean does not exist/no permissions...
https://github.com/Yuyuko1024/device_xiaomi_chopin/blob/lineage-18.1/rootdir/etc/fstab.mt6891
TWRP is available btw
https://forum.xda-developers.com/t/twrp-unofficial-3-6-0-poco-x3-gt-redmi-note-10-pro-5g.4369207