Hello, at the moment my phone is in a bit weird state and I would really appreciate any help
this is what I have, it's a SHS bought in Europe
Model number: GT-I9000
Formware version: 2.2
Baseband version: I9000XXJPP
Kernel version: 2.6.32.9 [email protected] #Voodoo_stable_5.5
Build number: FROYO.XWJPF
I installed latest voodoo recently and it worked fine, quadrant was giving me about 1500 points so I'm sure it working and the phone was really fast
everything was fine until decided to root it to apply wifi timeout fix... since I have 3 button recovery mode I didn't think I was risking anything (MY MISTAKE!)
unfortunately, after 4 hours of reviving my phone I don't remember what program from market I used to root... anyway, I ended up having SuperUser app with ninja icon... and I lost all my other apps... now I know I should have converted the filesystem back before doing anything, but it was too late
at this point female voice was already saying "data partition /*something*/ system not available"
I decided to reset the phone from the recovery menu and it was giving me errors, it couldn't mount partition or do something with them, and it also wouldn't boot anymore
I started searching for solutions and found THIS, everything looked exactly as I had so I decided to follow those instructions, I think they can be summed up to this:
Now, we need to fix the partitions. This is assuming that the partitions are there, just the wrong format (which is what happened to me .. I accidentally made them FAT32 instead of ext). So, run the following: parted /dev/block/mmcblk0 mkfs ext2. It will ask if you want to continue, hit yes. When it asks for the partition number, enter 1. Next, when it asks for the format, enter ext2. Let it do its thing. Now, once it's done, run parted again. This time, enter partition 2 (everything else is the same).
Click to expand...
Click to collapse
I did what this said and my phone could boot and wipe data from recovery menu could also work
but it kept saying about "system not available"
I thought the problem could still be in the superuser ninja app, so I started looking how to remove it, and found THIS, which also worked and I got rid of it
but I still have female void saying "system not available" on boot
and for some reason, the phone can't connect by wifi to my router anymore, it gets stuck on obraining IP address, it could after all this, but after some restarts and resets it can't connect anymore
he's the voodoo logs that I have now:
2011-03-20 20:33:52 model detected: 8GB
2011-03-20 20:33:53 option: lagfix disabled
2011-03-20 20:33:53 option: lagfix is allowed to convert /system to Ext4
2011-03-20 20:33:53 option: debug mode enabled
2011-03-20 20:33:53 filesystem detection on system:
2011-03-20 20:33:53 Ext4 on /dev/block/stl9
2011-03-20 20:33:53 filesystem detection on dbdata:
2011-03-20 20:33:53 Ext4 on /dev/block/stl10
2011-03-20 20:33:53 filesystem detection on cache:
2011-03-20 20:33:53 Ext4 on /dev/block/stl11
2011-03-20 20:33:53 filesystem detection on data:
2011-03-20 20:33:53 RFS on /dev/block/mmcblk0p2
2011-03-20 20:33:53 battery level: 77%
2011-03-20 20:33:53 convert cache (/dev/block/stl11) from ext4 to rfs
2011-03-20 20:33:53 ERROR: unable to call the df command from system, cancel conversion
2011-03-20 20:33:53 Your Android system partition is empty or it is corrupt (Universal Lagfix /system corruption)
2011-03-20 20:33:53 You may flash a new factoryfs.rfs with Odin or try to it with the RFS fixer
2011-03-20 20:33:53 battery level: 77%
2011-03-20 20:33:53 convert dbdata (/dev/block/stl10) from ext4 to rfs
2011-03-20 20:33:53 ERROR: unable to call the df command from system, cancel conversion
2011-03-20 20:33:53 Your Android system partition is empty or it is corrupt (Universal Lagfix /system corruption)
2011-03-20 20:33:53 You may flash a new factoryfs.rfs with Odin or try to it with the RFS fixer
2011-03-20 20:33:53 no need to convert data
2011-03-20 20:33:53 battery level: 77%
2011-03-20 20:33:53 convert system (/dev/block/stl9) from ext4 to rfs
2011-03-20 20:33:56 ERROR: unable to call the df command from system, cancel conversion
2011-03-20 20:33:56 Your Android system partition is empty or it is corrupt (Universal Lagfix /system corruption)
2011-03-20 20:33:56 You may flash a new factoryfs.rfs with Odin or try to it with the RFS fixer
2011-03-20 20:33:58 manage fat.format in /system/bin
2011-03-20 20:33:58 fat.format wrapper already installed in /system/bin
2011-03-20 20:33:58 running extension: apk_cleaner.sh
2011-03-20 20:33:58 TouchWiz 3.0 Launcher already optimized
2011-03-20 20:33:58 running extension: install_bln.sh
2011-03-20 20:33:58 BackLightNotification improved liblights already installed
2011-03-20 20:33:58 running extension: install_su.sh
2011-03-20 20:33:58 secure su binary for Superuser apk already installed
2011-03-20 20:33:58 running extension: sdcard_cleaner.sh
2011-03-20 20:33:58 sdcard cleaned up
2011-03-20 20:33:58 running extension: update_vold.fstab.sh
2011-03-20 20:33:58 running init !
Click to expand...
Click to collapse
Quadrant gives me 1000 points now, so there's probably some different filesystem configuration at the moment... maybe it's because I followed the instructions and created ext2 partitions?
anyway, even though my phone has 3-button recovery and still boots it is still screwed at the moment, so I'm looking for a way to get back to stock firmware and then voodoo again
but should I somehow convert back to RFS first?
I don't care about my data, there's nothing important in it
I found this post, would it be safe to use any of those firmwares with the phone in this state? will Odin's re-partition feature dump everything that I have now and recreate normal filesystem?
and which stock firmware should I use? there's no I9000XXJPP version in that list, would it be safe to use any other European 2.2.1 version?
I appreciate any help
well what you need to do is download a firmware with all 3 files and PIT.
Go into odin and put the correct files in the correct section, then put your pit file in, and check the repartition box.
flash that thru odin and you should be ok, this will remove the ext 4 filesystem and replace back to stock rfs.
if you are having trouble finding a firmware with all 3 files. try darkys resurrection (odin version) with 512 pit.
Thanks, I'll try to install I9000XXJPY in the evening and see how it goes
I downloaded I9000XXJPY firmware from this thread and it's only 1 file inside - JPY_JPY_JPY.tar
inside it has:
cache.rfs
factoryfs.rfs
param.lfs
zImage
modem.bin
instructions say that I shouldn't check re-partition with 1 file installation, but as I understand, I need to re-partition my phone
will this 1 file firmware installation even work in my situation?
I think I found what I need: this post describes how to install 1 file firmware with repartitioning and rooting
following those instructions solved my problems
the only problem was with voodoo... I was surprised to see that even after installing new firmware my phone still remembered password for my wifi... so I had to reset it
and voodoo wouldn't work, because there was a disable-lagfix file on the internal sd card (which also wasn't erased), so I had to remove that
Thanks for the advice
This is in response to this thread in the developers forum.
I have compiled the cifs.ko kernel module for the Droid 3 from the source code for build 5.5.1_84_D3G-20_TA-9 with kernel version 2.6.35.7-g790a33c found here. Slow-work.ko is not needed as it is built into the Droid 3 kernel.
Thanks, did it work for you?
I could insmod your cifs.ko, but the mount errored:
[email protected]_solana:/# insmod /system/lib/modules/cifs.ko
[email protected]_solana:/# busybox mkdir /sdcard/winshares
[email protected]_solana:/# busybox mount -t cifs //192.168.1.3/droid /sdcard/winshares
mount: mounting //192.168.1.3/droid on /sdcard/winshares failed: Invalid argument
Looks like my kernel version is the same: 2.6.35.7-g790a33c, but my Build# is slightly different: 5.5.1_84_D3G-55.
Could it be that?
Total noob question, but I thought we couldn't load cusom kernels with the phone being locked. What gives?
Well, it's only loading a module into the kernel, you can do that once you have root.
I think the mount needs a username. Please add "-o username=guest" to your mount command.
Yes, thanks, that did it. Looks like username is not optional.
do you have the .config from the stock rom?
It was posted here:
http://forum.xda-developers.com/showpost.php?p=17088489&postcount=10
can you provide loop and ext2 ext3 support ko? thanks
I am new to Android, want to customize the system follow the tutorials, but found the Note is different to other Android phones:
for other phone, there will be a /proc/mtd and list all the partitions with mount point, but on Note I can only found /proc/fs, with 3 folders: ext4 jbd2 nfsd
and the mount table is like this:
rootfs on / type rootfs (ro,relatime)
...
/dev/block/mmcblk0p9 on /system type ext4
/dev/block/mmcblk0p7 on /cache type ext4
/dev/block/mmcblk0p1 on /efs type ext4
for other devices, e.g., HTC Wildfire, the partition will like below:
mtd1: recovery
mtd3: system"
...
I downloaded the CF-Root flasher, by Chainfire, found basiclly it's flashing a zImage into /dev/block/mmcblk0p5. I mount the partition before flash and seems there is only some picture files there. how can we know the machine will boot to this partition in recovery mode?
nobody knows? so far what I get seems that the phone do not use the /recovery partition, but use same kernel to handle the recovery state. during boot it will search for /system/etc/install-recovery.sh, maybe that will trigger the recovery process?
The Note, like many other Samsung phones, does not use or follow the mtd layout - at all.
Indeed there is a single kernel for both normal boot and recovery. Normal boot uses init.rc script, recovery boot uses recovery.rc script.
There is a "spare" partition that is both called recovery and available, but it isn't used.
Android updates to A/B OTA way and now there is no recovery partition.
source.android.com/devices/tech/ota/ab_updates
I can get adb root on one device and push all the files in. It cannot find the init.environ.rc after running the update script. But it is acturally there.
And it may not help to root if we flash the modified boot.img back to boot_a, as the real boot image now move to system partition.
Is there any way to root on this kind of devices?
Thanks.
flamepjlh said:
Android updates to A/B OTA way and now there is no recovery partition.
source.android.com/devices/tech/ota/ab_updates
I can get adb root on one device and push all the files in. It cannot find the init.environ.rc after running the update script. But it is acturally there.
And it may not help to root if we flash the modified boot.img back to boot_a, as the real boot image now move to system partition.
Is there any way to root on this kind of devices?
Thanks.
Click to expand...
Click to collapse
Which device?
If it has fastboot, you can 'fastboot boot' TWRP and install SuperSU.
If you're already rooted, on many devices you can use the FlashFire app to update SuperSU from ZIP.
I am working on an update to the CF-Auto-Root system that can produce rooting files for these sort of devices. I thought it would be done by now, but it isn't
Chainfire said:
Which device?
If it has fastboot, you can 'fastboot boot' TWRP and install SuperSU.
If you're already rooted, on many devices you can use the FlashFire app to update SuperSU from ZIP.
I am working on an update to the CF-Auto-Root system that can produce rooting files for these sort of devices. I thought it would be done by now, but it isn't
Click to expand...
Click to collapse
I'm using a non-standard device so no TWRP can support it. I can compile the image myself.
I start this thread because I saw google updated the way of OTA. New devices will coming to market with this kind of OTA method and the system less root cannot be use anymore.
The most significant change is that the recovery will be included in boot.img, and the real rootfs ramdisk will be put into system.img.
So I think I cannot get root with the current supersu package. I need to mannually change the files with adb shell command.
flamepjlh said:
I'm using a non-standard device so no TWRP can support it. I can compile the image myself.
I start this thread because I saw google updated the way of OTA. New devices will coming to market with this kind of OTA method and the system less root cannot be use anymore.
The most significant change is that the recovery will be included in boot.img, and the real rootfs ramdisk will be put into system.img.
So I think I cannot get root with the current supersu package. I need to mannually change the files with adb shell command.
Click to expand...
Click to collapse
First, you're confusing two different changes as one. There's the A/B partition layout change, and there's the rootfs inside system.img change. Both are supported by SuperSU since last year.
However, the only common device that currently uses this (and the only device we have tested this with) is the Google Pixel (XL). That is why I ask which device you have, but you seem to be reluctant to answer.
Chainfire said:
First, you're confusing two different changes as one. There's the A/B partition layout change, and there's the rootfs inside system.img change. Both are supported by SuperSU since last year.
However, the only common device that currently uses this (and the only device we have tested this with) is the Google Pixel (XL). That is why I ask which device you have, but you seem to be reluctant to answer.
Click to expand...
Click to collapse
Sorry I didn't explain that clear. It is an engineering device running Android 7.1.1 with Qualcomm SDM660. No module number. That why I can flash the image by fastboot.
If the changes are supported already, I think that should be fine. But it cannot find init.environ.rc file the and here is the log:
Code:
----- patch check -----
Loading from cpio:[init.rc] ...
Finding [daemonsu]
-!Found
Finding [SuperSU:PATCH]
-!Found
Result: not patched
----- verity_key -----
Removing [verity_key] ...
----- fstab: [etc/recovery.fstab] -----
Loading from cpio:[etc/recovery.fstab] ...
Finding [,support_scfs]
-!Found
Finding [,verify]
[email protected] [/dev/block/bootdevice/by-name/system / ext4 ro,barrier=1 wait,slotselect,verify]
[email protected] [/dev/block/bootdevice/by-name/system / ext4 ro,barrier=1 wait,slotselect,verify]
[email protected] [/dev/block/bootdevice/by-name/system / ext4 ro,barrier=1 wait,slotselect]
Finding [,verify]
-!Found
Finding [,forceencrypt]
-!Found
Finding [,forcefdeorfbe]
-!Found
Finding [,fileencryption]
-!Found
Finding [ro,!rw,!atime|relatime]
[email protected] [/dev/block/bootdevice/by-name/system / ext4 ro,barrier=1 wait,slotselect]
[email protected] [/dev/block/bootdevice/by-name/system / ext4 ro,barrier=1 wait,slotselect]
[email protected] [/dev/block/bootdevice/by-name/system / ext4 ro,noatime,barrier=1 wait,slotselect]
Finding [ro,!rw,!atime|relatime]
-!Found
Saving to cpio:[etc/recovery.fstab] ...
----- fstab: [fstab.qcom] -----
Loading from cpio:[fstab.qcom] ...
Finding [,support_scfs]
-!Found
Finding [,verify]
[email protected] [/dev/block/bootdevice/by-name/system / ext4 ro,barrier=1,discard wait,slotselect,verify]
[email protected] [/dev/block/bootdevice/by-name/system / ext4 ro,barrier=1,discard wait,slotselect,verify]
[email protected] [/dev/block/bootdevice/by-name/system / ext4 ro,barrier=1,discard wait,slotselect]
Finding [,verify]
-!Found
Finding [,forceencrypt]
[email protected] [/dev/block/bootdevice/by-name/userdata /data ext4 nosuid,nodev,barrier=1,noauto_da_alloc,discard,lazytime wait,check,forceencrypt=footer,crashcheck]
[email protected] [/dev/block/bootdevice/by-name/userdata /data ext4 nosuid,nodev,barrier=1,noauto_da_alloc,discard,lazytime wait,check,forceencrypt=footer,crashcheck]
[email protected] [/dev/block/bootdevice/by-name/userdata /data ext4 nosuid,nodev,barrier=1,noauto_da_alloc,discard,lazytime wait,check,encryptable=footer,crashcheck]
Finding [,forceencrypt]
-!Found
Finding [,forcefdeorfbe]
-!Found
Finding [,fileencryption]
-!Found
Finding [ro,!rw,!atime|relatime]
[email protected] [/dev/block/bootdevice/by-name/system / ext4 ro,barrier=1,discard wait,slotselect]
[email protected] [/dev/block/bootdevice/by-name/system / ext4 ro,barrier=1,discard wait,slotselect]
[email protected] [/dev/block/bootdevice/by-name/system / ext4 ro,noatime,barrier=1,discard wait,slotselect]
Finding [ro,!rw,!atime|relatime]
[email protected] [/dev/block/bootdevice/by-name/modem /firmware vfat ro,shortname=lower,uid=1000,gid=1000,dmask=227,fmask=337,context=u:object_r:firmware_file:s0 wait,slotselect]
[email protected] [/dev/block/bootdevice/by-name/modem /firmware vfat ro,shortname=lower,uid=1000,gid=1000,dmask=227,fmask=337,context=u:object_r:firmware_file:s0 wait,slotselect]
[email protected] [/dev/block/bootdevice/by-name/modem /firmware vfat ro,noatime,shortname=lower,uid=1000,gid=1000,dmask=227,fmask=337,context=u:object_r:firmware_file:s0 wait,slotselect]
Finding [ro,!rw,!atime|relatime]
[email protected] [/dev/block/bootdevice/by-name/bluetooth /bt_firmware vfat ro,shortname=lower,uid=1002,gid=3002,dmask=227,fmask=337,context=u:object_r:bt_firmware_file:s0 wait,slotselect]
[email protected] [/dev/block/bootdevice/by-name/bluetooth /bt_firmware vfat ro,shortname=lower,uid=1002,gid=3002,dmask=227,fmask=337,context=u:object_r:bt_firmware_file:s0 wait,slotselect]
[email protected] [/dev/block/bootdevice/by-name/bluetooth /bt_firmware vfat ro,noatime,shortname=lower,uid=1002,gid=3002,dmask=227,fmask=337,context=u:object_r:bt_firmware_file:s0 wait,slotselect]
Finding [ro,!rw,!atime|relatime]
[email protected] [/dev/block/bootdevice/by-name/dsp /dsp ext4 ro,nosuid,nodev,barrier=1 wait,slotselect]
[email protected] [/dev/block/bootdevice/by-name/dsp /dsp ext4 ro,nosuid,nodev,barrier=1 wait,slotselect]
[email protected] [/dev/block/bootdevice/by-name/dsp /dsp ext4 ro,noatime,nosuid,nodev,barrier=1 wait,slotselect]
Finding [ro,!rw,!atime|relatime]
-!Found
Saving to cpio:[fstab.qcom] ...
----- init.rc -----
Loading from cpio:[init.rc] ...
Finding [setprop selinux.reload_policy]
-!Found
Finding [import ]
[email protected] [import /init.recovery.${ro.hardware}.rc]
[email protected] [import init.supersu.rc]
[email protected] [# SuperSU:PATCH:282]
[email protected] [# SuperSU:STOCK:2abbb76a1428595002371e5f2c540699f81370e0]
Saving to cpio:[init.rc] ...
----- init.environ.rc -----
Loading from cpio:[init.environ.rc] ...
Could not locate entry
--- Failure, aborting
And here is the content in /init.environ.rc :
Code:
# set up the global environment
on init
export ANDROID_BOOTLOGO 1
export ANDROID_ROOT /system
export ANDROID_ASSETS /system/app
export ANDROID_DATA /data
export ANDROID_STORAGE /storage
export EXTERNAL_STORAGE /sdcard
export ASEC_MOUNTPOINT /mnt/asec
export BOOTCLASSPATH /system/framework/core-oj.jar:/system/framework/core-libart.jar:/system/framework/conscrypt.jar:/system/framework/okhttp.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/telephony-common.jar:/system/framework/voip-common.jar:/system/framework/ims-common.jar:/system/framework/apache-xml.jar:/system/framework/org.apache.http.legacy.boot.jar:/system/framework/tcmiface.jar:/system/framework/telephony-ext.jar:/system/framework/WfdCommon.jar:/system/framework/oem-services.jar:/system/framework/qcom.fmradio.jar
export SYSTEMSERVERCLASSPATH /system/framework/services.jar:/system/framework/ethernet-service.jar:/system/framework/wifi-service.jar
flamepjlh said:
Sorry I didn't explain that clear. It is an engineering device running Android 7.1.1 with Qualcomm SDM660. No module number. That why I can flash the image by fastboot.
If the changes are supported already, I think that should be fine. But it cannot find init.environ.rc file the and here is the log:
Click to expand...
Click to collapse
As I said, it's only been tested on Pixel as its the only device (I know of) in the wild that uses this setup. Some tweaks may be needed to get it working on other devices.
If you can upload the (original) boot images somewhere and send me a link (in PM if necessary) I can take a look.
I received your boot image, but if I try to patch it on my system, it works without issue. I am patching it from a TWRP environment on a different device, though.
Chainfire said:
I received your boot image, but if I try to patch it on my system, it works without issue. I am patching it from a TWRP environment on a different device, though.
Click to expand...
Click to collapse
Unfortunatly I cannot use TWRP as there is no recovery partition. I think there is also something to do with the system image.
Never mind. The devices will come to market a few days later. You can have the device with this kind of software by then. I can wait for that.
Thanks for you to check that.
Hello I have the Moto z2 force and it has a/b partitioning like the Pixel XL...I have unlocked the bootloader but that's as far as I've gotten..Magisk Manager can patch our boot but not get root yet..I'll pm you my original boot.img if you happen to get some time I'd be honored..