Related
breaking..ok, old news: RC30 (jailbreak fix)
http://www.tgdaily.com/content/view/40063/140
Curious about this. Im not in the know enough to do anything with root, but for all of you that have access, if others update, will they be able to use anything that you develop or create with access to root? hopefully....
I 'm wondering how can I prevent this. I'm in about the same boat as you honda. Root is a stranger to me... But, I'm sure it would suck if I get stuck out side of the loop :/
sonikamd said:
I 'm wondering how can I prevent this. I'm in about the same boat as you honda. Root is a stranger to me... But, I'm sure it would suck if I get stuck out side of the loop :/
Click to expand...
Click to collapse
If you look there is another thread where someone else posts what to do... although he hasn't got the files on the forum yet he is having some issues uploading them.
sonikamd said:
I 'm wondering how can I prevent this. I'm in about the same boat as you honda. Root is a stranger to me... But, I'm sure it would suck if I get stuck out side of the loop :/
Click to expand...
Click to collapse
JUST DON'T UPDATE TO RC30. It's that simple.
If you don't understand how to get root, just wait till someone (I would but haven't had time) makes a very detailed yet simple method.
Ah, I'm still running RC19 and have yet to experience Google's update process.
I thought the update was mandatory and done without user input, just a "congratulations, you phone is now a little slower!"
So we can just deny the update with the stock sw?
sonikamd said:
So we can just deny the update with the stock sw?
Click to expand...
Click to collapse
When you get the OTA update, it pops up a message window asking if you want to install. You say either say yes, or "not right now". I think it will keep bugging you to install, and possibly go ahead and automatically install it if you say "not right now" enough times. (I'm not positive about that.. I just remember seeing something like that when I was looking through the source for the updater app).
I think it works like Windows updates, it gives you option to update now or later and if neither is hit in a certain time it will install it automatically. I am going to test this when my update comes. I will hit Update later and see what it does. but i have read others comments saying they never seen the update now or later window and got the new version anyhow.
I'm on the train right now so someone else (or me) can post detailed directions. But if you get root and rename/remove /etc/security/otakeys.zip they (probably) can't update you automatically.
While that file is in place they might be able to upgrade without prompting (anyone want to search the code for info?)
UPDATE: They -can- forcibly update you: http://forum.xda-developers.com/showthread.php?goto=newpost&t=443328
google should wonder ppl do thing themselves...wen they have to come up with 3 update in less than a month....there always worried about security and not functionality..lol...i mean cmon i had to buy a new sdcard jus to get RC 29...cause it sure wasnt commin to me via OTA....i wonder wat i have to do to get RC 30..
SmartBrother90 said:
google should wonder ppl do thing themselves...wen they have to come up with 3 update in less than a month....there always worried about security and not functionality..lol...i mean cmon i had to buy a new sdcard jus to get RC 29...cause it sure wasnt commin to me via OTA....i wonder wat i have to do to get RC 30..
Click to expand...
Click to collapse
Correct spelling and punctuation may be a good place to start
sonikamd said:
Ah, I'm still running RC19 and have yet to experience Google's update process.
I thought the update was mandatory and done without user input, just a "congratulations, you phone is now a little slower!"
So we can just deny the update with the stock sw?
Click to expand...
Click to collapse
Well, I accepted RC29 and I've noticed the phone is faster and has better battery life.
I've also been very conservative with usage because I'm waiting to install and run apps from the SD card.
jailbreaking the t-mobile RC30 update
From what I have read so far it is not possible to re do the images on the G1 because of the RC30 patch from T-Mobile. Mainly because you do not have root, and the second because without root you can't remount the /system partition as RO.
adb allows you to mount the /system partition as RW. Would this not do the trick.
Code:
./adb shell
#mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mtdblock3 /system yaffs2 ro 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block/mmcblk0p1 /sdcard vfat ro,dirsync,nosuid,nodev,noexec,uid=1000,gid=1000,fmask=0711,dmask=0700,codepage=cp437,iocharset=iso8859-1,utf8 0 0
This was the out put that I got. Now to run the remount from adb.
Code:
adb remount
-
remount succeeded
now to make sure that this really worked.
Code:
./adb shell
-
# mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mtdblock3 /system yaffs2 rw 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block/mmcblk0p1 /sdcard vfat ro,dirsync,nosuid,nodev,noexec,uid=1000,gid=1000,fmask=0711,dmask=0700,codepage=cp437,iocharset=iso8859-1,utf8 0 0
as you can see the /system directory is not in rw mode and not ro mode.
To test to see if this is the case.
Code:
vi test.push (:wq)
adb push test.push /system
adb shell
# cd /system
# ls
test.push
lib
media
framework
fonts
etc
build.prop
bin
usr
sounds
recovery.img
app
lost+found
As we can see this did seem to work. I do not have a T-Mobile RC30. I have mine jailbroken already. with the steps that JesusFreke laid out.
I was wondering if it would be possible to do the same steps but with using adb to mount the fs in rw, and then using adb push to push the recovery.img to the device into the /system dir.
doing another push of the test.push file seems to take.
Code:
adb push test.push /system
vi test.push (i incerted the leter i)
adb push test.push /system
0 KB/s (2 bytes in 0.048s)
adb shell
# cat /system/test.push
i
#
So this might be the break that people are looking for that have the T-Mobile RC30. JesusFreke I know that you said that you have one with an RC30 from T-Mobile. Would you be willing to try this at the risk of bricking the phone? I know that is a $400 question, or anyone else for that matter.
If you do try it, please let me know the results. I have a friend, whos wife has the RC30 from T-Mobile. He is not willing to risk his wife's wrath.
It works on emulator.exe but will the live RC30 adb server accept remount? I notice that there are no references to remount in the official documentation. Alas I don't have any official RC30 G1 to test with.
Id bewilling to trythis right now. I have a Modded RC30 that I will update to the official RC30 that I am sending back anyways for defects. Anyone wanna tell me how to flash mine back to Official RC30 and Ill get to trying.
mouseclone said:
From what I have read so far it is not possible to re do the images on the G1 because of the RC30 patch from T-Mobile. Mainly because you do not have root, and the second because without root you can't remount the /system partition as RO.
adb allows you to mount the /system partition as RW. Would this not do the trick.
Code:
./adb shell
#mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mtdblock3 /system yaffs2 ro 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block/mmcblk0p1 /sdcard vfat ro,dirsync,nosuid,nodev,noexec,uid=1000,gid=1000,fmask=0711,dmask=0700,codepage=cp437,iocharset=iso8859-1,utf8 0 0
This was the out put that I got. Now to run the remount from adb.
Code:
adb remount
-
remount succeeded
now to make sure that this really worked.
Code:
./adb shell
-
# mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mtdblock3 /system yaffs2 rw 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block/mmcblk0p1 /sdcard vfat ro,dirsync,nosuid,nodev,noexec,uid=1000,gid=1000,fmask=0711,dmask=0700,codepage=cp437,iocharset=iso8859-1,utf8 0 0
as you can see the /system directory is not in rw mode and not ro mode.
To test to see if this is the case.
Code:
vi test.push (:wq)
adb push test.push /system
adb shell
# cd /system
# ls
test.push
lib
media
framework
fonts
etc
build.prop
bin
usr
sounds
recovery.img
app
lost+found
As we can see this did seem to work. I do not have a T-Mobile RC30. I have mine jailbroken already. with the steps that JesusFreke laid out.
I was wondering if it would be possible to do the same steps but with using adb to mount the fs in rw, and then using adb push to push the recovery.img to the device into the /system dir.
doing another push of the test.push file seems to take.
Code:
adb push test.push /system
vi test.push (i incerted the leter i)
adb push test.push /system
0 KB/s (2 bytes in 0.048s)
adb shell
# cat /system/test.push
i
#
So this might be the break that people are looking for that have the T-Mobile RC30. JesusFreke I know that you said that you have one with an RC30 from T-Mobile. Would you be willing to try this at the risk of bricking the phone? I know that is a $400 question, or anyone else for that matter.
If you do try it, please let me know the results. I have a friend, whos wife has the RC30 from T-Mobile. He is not willing to risk his wife's wrath.
Click to expand...
Click to collapse
The RC30 you have from JesusFreke gives the adb daemon root permissions. What you listed will not work on a Google RC30.
Koush said:
The RC30 you have from JesusFreke gives the adb daemon root permissions. What you listed will not work on a Google RC30.
Click to expand...
Click to collapse
Meaning that as soon as you type in adb shell and hit enter it will not even start the daemon?
Get official RC30 zip (here), use SignApk.jar from AndroidMod.zip (here) on it and place it in root of sdcard as update.zip. Reboot into recovery and Alt+S.
ballaholyk84 said:
Meaning that as soon as you type in adb shell and hit enter it will not even start the daemon?
Click to expand...
Click to collapse
Most likely it just gives the shell at $ instead of #.
Edit: gah, dyslexic.
Koush said:
The RC30 you have from JesusFreke gives the adb daemon root permissions. What you listed will not work on a Google RC30.
Click to expand...
Click to collapse
I was thinking that was just for the adb shell command. The adb remount is something that is in the helpfile from the SDK. Just typing in adb will give you the list of commands to use.
If not going though the shell how ever, did they disable all of adb's root privs? If you have one and try the remount and get a success, the adb still has root privies, just not on with the adb shell command.
Really this is just a thought. I wish that I really had a device to test it on.
Trying to get Dexter's native ext2 support working.
I pulled my SD card (8gb) and using GParted within Ubuntu, deleted my FAT32 partition, created 1st partition FAT32 ~7gb, 2nd partition ext2 (1gb), 3rd partition SWAP (64mb)
I understand that with Dexter's 1.1b, when the phne is booted with the card in, it should find the ext2 partition and proceed to move my apps to this partition.
Note, I also tried ext3 in the same partition configuration.
Under memory/sd card sotrage, phone is reading ~6.9GB as expected of the FAT32 partition.
Am I missing a step? Nothing ever gets moved from the phone to the card's ext2 partition.
ext2,3 problem on dexters rom
Sorry first post noob, hopefully im doing this right
I used mini tool partition wizard... i tried ext2 then ext3, made them logical and primary, with the swap partition. (do we need that swap ..i haven't tried it without it).
And the entire memory card wouldn't be recognised/mount at all when turning on the phone. I had to remove the partitions to be able to use the memory card in the normal manner.
is there another step? i was hoping all i had to do was make the partition and it would be done.
help!
did u guys set the ext partition to active?
I did not mark any partition active (none of the many guides on the net say anything about setting partition flags). My layout (per parted) looks like this:
Code:
Number Start End Size Type File system Flags
1 1049kB 6818MB 6817MB primary fat32
2 6818MB 7892MB 1074MB primary ext2
3 7892MB 7959MB 67.1MB primary linux-swap
Which matches every screenshot I have seen of parted/Gparted in any formatting guide.
I did find one that had fat32 marked as lba, but that makes no difference.
R-D said:
I understand that with Dexter's 1.1b, when the phne is booted with the card in, it should find the ext2 partition and proceed to move my apps to this partition.
Note, I also tried ext3 in the same partition configuration.
Click to expand...
Click to collapse
What is the output of "mount" after your phone boots up? Check if it is mounted already. If not try to mount it manually. At least we'll know if the issue is in phone recognizing the partitions.
I realised what i did wrong ..I tried to make the ext2 partition after I 'installed/flashed' dexters rom ...this messed everything up for me.
So I re-did the entire process but made my ext2 partition first. Now its allgood
Don't know if that helps
Sent from my XT720 using XDA App
kousik said:
What is the output of "mount" after your phone boots up? Check if it is mounted already. If not try to mount it manually. At least we'll know if the issue is in phone recognizing the partitions.
Click to expand...
Click to collapse
Here's the default mount output:
Code:
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
/dev/block/mtdblock7 /system yaffs2 ro 0 0
/dev/block/mtdblock9 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock8 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock6 /cdrom yaffs2 rw 0 0
tmpfs /tmp tmpfs rw,size=2048k 0 0
tmpfs /skttmp tmpfs rw,size=2048k 0 0
/dev/block/mtdblock0 /pds yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock7 /system/lw yaffs2 ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
none /acct cgroup rw,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
tmpfs /tmp tmpfs rw,size=2048k 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,size=0k,mode=000 0 0
When I try and mount it manually, which device name is preferred? I found the partitions (1 = fat32, 2 = ext2, 3 = swap) as these names:
/dev/block/vold/179:1
/dev/block/mmcblk0p1
/dev/block/vold/179:2
/dev/block/mmcblk0p2
/dev/block/vold/179:3
/dev/block/mmcblk0p3
I can mount partition 1 manually referencing either device name, but when I try to mount partition 2 it says: mount: No such device
I know it is the right device because I can mount the fat32 partition.
Thanks for your help.
Edit: I saw in dateno1's script in the dev thread, he is doing insmod /system/lib/modules/ext2.ko before the mount, I do not have this module (I know he has it in his download package) but should I already have this in /system/lib/modules? Does this exist already for anyone else? Or am I guessing at the wrong thing?
R-D said:
I can mount partition 1 manually referencing either device name, but when I try to mount partition 2 it says: mount: No such device
I know it is the right device because I can mount the fat32 partition.
Edit: I saw in dateno1's script in the dev thread, he is doing insmod /system/lib/modules/ext2.ko before the mount, I do not have this module (I know he has it in his download package) but should I already have this in /system/lib/modules? Does this exist already for anyone else? Or am I guessing at the wrong thing?
Click to expand...
Click to collapse
"No such device" is indication that the kernel module is not loaded properly.
You may have to insmod ext2.ko yourself to get it to work. If you do not have the .ko files, you can download from http://dateno1.egloos.com/27191 yourself and copy to /system/lib/modules. Also you can see this thread http://forum.xda-developers.com/showthread.php?t=929871 for reference.
Okay, mystery solved!
I am missing these modules as I grabbed the "original" 1.1b update (1.1a-update.zip). This original file was missing these modules and had an incorrect overclock module.
I just re-downloaded 1.1b again, and found that if I look in the ZIP file, it has the missing modules I didnt initially get.
In speaking with Dexter, it seems that he updated the 1.1b (1.1a-update.zip) file twice, but kept the same file and version name. So the 1.1b everyone else is using, is newer than the 1.1b I downloaded, as I downloaded it right after it was first posted and missed the next update as it had the same filename.
Essentially, what amounted to 1.1c was also released as 1.1b ...
So lesson is, either redownload and apply the 1.1b update, or update to 1.2 (or newer as they come).
Thanks for your help.
Oh ! Confusing this 1.1a/b/c !
is it nid to do it manually? 1.1b did detect my ext2.. but in 1.2 did not detect.. i try put ext2 and ext4 ald..
Hello,
I developed a guide and software package to boot a phone with a fried emmc.
The trick is to use modified kernel files and mount all partitions to image files on SD card - however, kernel files and software are different from phone to phone.
My guide already works nice for HTC Desire Z / G2:
http://forum.xda-developers.com/showthread.php?t=1572924
To port that guide and the linked package to HTC Desire Z I need a tester with a custom rom (ClockworkMod recovery, 3Ext ...). For porting the package I need someone with a full working phone. For testing later someone with a fried emmc would be helpful.
If you want to support me then send me a private message on XDA or visit me on freenode IRC channel #G2ROOT (web interface: http://webchat.freenode.net - channel #G2ROOT)
Best regards,
Catherall
Excellent idea !
If you need tester with fully working phone - I'm in .
Especially as we can use this as some sort of dual boot on working phones to test new roms without installing it
R.
Hello,
I have fried emmc on htc desire s. I sent my phone about 10 days ago to local service. I will get my phone soon. If they don't succeed I will be your tester.
I had a call with service man 2 days ago and he said to me that they can repair it and repair will cost 15€. He said that they will reprogram emmc or something like that and they are waiting to receive 1 file for phone software and when it comes phone will be repaired.
If you need aditional info PM me.
How about the progress on porting to desire s?. I´m available if you look for a tester with a fried chip
All is working as I can say. But not sure if I can post needed files... Lets wait for catherall answer .
R.
He is offline since 23. april so if anyone know to make this work do it
Ok, all credits going to catheral. I'm tested this with working desire s and phone is booting from recovery without any problems. You just need to extract downloaded files to sdcard root and apply update.zip from recovery ...
https://www.dropbox.com/s/e5nusi7ojg65q8e/Saga_recovery_boot.rar
R.
Great! Thank you. This is big thing for desire s now because emmc problem is now fixed.
One question: When I restart or turn off phone do I need to do update in recovery again or this will be permanent ?
So im confused what does this do? Is there anyway to port it to the htc incredible s?
Sent from my Incredible S using XDA
first thanks for the great work which catherall has done.
Just put this on my sdcard and booted from recovery via update.zip. I can confirm that this rom is booting on my desire s with fried emmc. Overall the performance is pretty fast but there are few limitations:
Wlan doesn´t work
Each time when an app is trying to acess the internal memory, it crashes(since there is no internal memory due emmc brick)
Working (tested):
phone calls
text messages
acessing internet via HDSPA,Umts,...
everything which doesn´t need access to internal storage
app installs
Great!
Rolf can you fix wlan ?
Hey catherall.
I was just thinking when reading your thread..i don't have a fried emmc but it might help you or someone else develop a permanent fix for this issue.
If you can boot the phone from the sdcard via this "temp fix" which is brilliant btw (hats off to you)..i guess that you could try to do this natively.
Bear with me as i am no expert in android or any other programming development but i do have a technical inclination.
To my understanding the emmc holds these partitions: /system; /data; /cache
Also, the partition layout is dictated by the HBOOT (am i right?).
Thus, if HBOOT is functional after frying the emmc can't the hboot be reprogrammed so as to allocate the /system; /data; /cache to the sdcard thus natively run them on the sd and by this fixing the current issues? I'm thinking yes because if the rom is installed with the mentioned partitions being on the sd it will not try to access the emmc thus no failures, issues, kernel oops or panics.
Keep in mind that i'm not properly educated in this domain of expertise and what i wrote might just be a huge load of *$#& and that what i said is purely a principle based on what i understand about the android platform.. no idea how to code or reprogram HBOOT so i might be wrong.
P.S. sorry about cloning posts..
Hands up to the original Dev of this great project. this will help a lot of people. who are having problems with their fried chip. however once this ROM is stable you wont be able to upgrade it or anything so you will be stuck with this Rom. now. you can replace your chip for very little cash. you just need the brains to replace it with the old 1. Is this rom even good enough. i mean in eyes of people who are serial flasher's they are going to want to flash a new rom lol. and 2 is there any way we could just have a new development section that is FOCUSED on development with fried chip roms like this 1. i think this could be extended. i think if this can be done with cyanogen then it can be done with stock Rom also. im very intrested in asking the mod to set up a dev section for this so we can develope roms that are aimed at peple with fried chips. as this will help a lot of people. we could develope or mod the roms out at the moment for the people with fried chips. if anyone else agree's with me then please reply if enough peole on this forum want it done i say we get on it now
hey Paul.
Im with you 100% but i think that there needn't be specific emmc-fried roms (the rom components can be extracted and installed to the sd manually by each user if a guide is made). The problem i believe are the kernels as they are the subsystem that communicate to the hardware, not the rom itself.. if my previous post is right though, then i believe that the roms can be flashed normally and be directed to new partitions on the SD automatically.
xxmorph3u5xx said:
hey Paul.
Im with you 100% but i think that there needn't be specific emmc-fried roms (the rom components can be extracted and installed to the sd manually by each user if a guide is made). The problem i believe are the kernels as they are the subsystem that communicate to the hardware, not the rom itself.. if my previous post is right though, then i believe that the roms can be flashed normally and be directed to new partitions on the SD automatically.
Click to expand...
Click to collapse
in that case there would have to be a new kernel with every rom made for this. im my experience i would say that i wouldnt go ahead as ask for a dev section for this to be opend. i will infact tho test this out and see if the rom itself can be installed to a new partition on the sdcard. i will let you know if the rom is able to install onto the sdcard later tonight. i very much dont think it will tho. but worth a shot. if it does work then does that mean we could get this more stable and without crashes ?
The rom will definetly not boot if you just install it to sd..no need to test that.. The partition table needs to be rewritten for this to work (the partition layout being stored in the HBOOT to my knowledge). This is why i suggested rewriting the HBOOT, because if i am right the recovery will flash every rom and kernel to the new partitions on the "fake" emmc (SD that is).
xxmorph3u5xx said:
The rom will definetly not boot if you just install it to sd..no need to test that.. The partition table needs to be rewritten for this to work (the partition layout being stored in the HBOOT to my knowledge). This is why i suggested rewriting the HBOOT, because if i am right the recovery will flash every rom and kernel to the new partitions on the "fake" emmc (SD that is).
Click to expand...
Click to collapse
hmmmmm im curious about this. but then again would anyone with a fried emmc chip be willing to flash a re written hboot that has a chance or 50% bricking there phone lol ? too messy for me im going to stick to making my sense tablet rom for now
Hboot 0.98.00000 and 0.980002
Mount list:
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mmcblk0p25 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p26 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p27 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p28 /devlog ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /app-cache tmpfs rw,relatime,size=8192k,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
htcfs /data/htcfs fuse.htcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other 0 0
/dev/block/vold/179:65 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,
uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharse
t=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:65 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.eamobile.nfsshift_na_wf-1 vfat ro,dirsync,nosuid,n
odev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,
shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/com.rovio.angrybirds-1 vfat ro,dirsync,nosuid,nodev,re
latime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortna
me=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-2 /mnt/asec/com.fridgecat.android.atilt-1 vfat ro,dirsync,nosuid,n
odev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,
shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-3 /mnt/asec/pl.idreams.skyforcereloaded-1 vfat ro,dirsync,nosuid,n
odev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,
shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-4 /mnt/asec/com.ArtInGames.AirAttackHD-1 vfat ro,dirsync,nosuid,no
dev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,s
hortname=mixed,utf8,errors=remount-ro 0 0
HBOOT 2.xxxxx
mount list:
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mmcblk0p25 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p26 /data ext4 rw,relatime,barrier=1,nodelalloc,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p27 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,nodelalloc,data=ordered 0 0
/dev/block/mmcblk0p30 /devlog ext4 rw,nosuid,nodev,noatime,barrier=1,nodelalloc,data=ordered 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /app-cache tmpfs rw,relatime,size=8192k,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
htcfs /data/htcfs fuse.htcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other 0 0
/dev/block/vold/179:65 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:65 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
Hehe, good luck with your port..i really like your ICS tab_mod!
As for the "who would risk bricking their phone"...i don't think that with a fried emmc there's anything else to brick.
Anyway, on a serious note though, i have no idea how hard rewriting a HBOOT would be, nor if it will actually work..i am no experienced programmer, this is why i recommended the "method" to a more experienced user in hope that the emmc damaged guys could catch a break.
Sure, as you said, replacing the emmc is a waaaay better solution but hardware modifications are not that easy and should be done only by specialized personnel which can be $$$.
xxmorph3u5xx said:
Hehe, good luck with your port..i really like your ICS tab_mod!
As for the "who would risk bricking their phone"...i don't think that with a fried emmc there's anything else to brick.
Anyway, on a serious note though, i have no idea how hard rewriting a HBOOT would be, nor if it will actually work..i am no experienced programmer, this is why i recommended the "method" to a more experienced user in hope that the emmc damaged guys could catch a break.
Sure, as you said, replacing the emmc is a waaaay better solution but hardware modifications are not that easy and should be done only by specialized personnel which can be $$$.
Click to expand...
Click to collapse
above is the mount info from desire s hboot 0.98.0000 and below is for hboot 2.xxxxx.
Thanks my rom is nice lol . im making the same rom but with sense its going well just need to port rosie from flyer then its done
This information is available in this sticky
http://forum.xda-developers.com/showthread.php?t=1180513
Looking forward to sense tablet version
Sent from my HTC Desire S using xda premium
Hi, my phone is a samsung galaxy y PRO. Android 2.3.6 rooted
I am trying to disable the keypad backlights...
In here:
\sys\class\backlight\keypad-led\brightness
when i set it to 0, the lights turn off, and after that i change the file permissons to 444 with chmod.
But when i turn off screen and turn on again (stand by mode) the keypad lights turn on again, and when i go to edit the brightness file again, it shows the value 255.
Any solutions?? Also when i try to remove the file (via terminal with SU) i get a operation not permitted message.
Help please.
Thanks!
BTW, i will donate do the guy that makes it work!
Dumb question, is /system set as r/w?
Sent from my LG-P999 using xda premium
Yes, i tryied with total comander, setting system to r/w
Well, then the alternative is copy it via cwm and set the permissions in the script. I can't do it right now, I about to start work, but if no one has handled this by the time I am off and home, about 9:00pm CA time, I will get it set up.
Sent from my LG-P999 using xda premium
Please do that! I will get in here asap. Cya in a few hours.
Thank you for trying to help!
BTW, i tryed to install ClockworkMod via Rom Manager but it says that there is no support with my samsung galaxy y Pro (GT-B5510)...
Ok, i got a temporary ClockworkMod that i can use when needed...
Ok, did some researching of my own for your phone, check your pm.
Ok, this is sort of simple, the file is called "brightness" and its content must be a zero "0". Thats it. The file must be placed in "/sys/class/backlight/keypad-led/".
I don't know how the script you need should look like, but commands to change the file to disable keypad light should be:
echo 0 > /sys/class/backlight/keypad-led/brightness
And the permission command:
chmod 444 /sys/class/backlight/keypad-led/brightness
I know the basic of how it should look and what is needed for it to work, I have a zip I made for myself for copying over ringtones and notifications from a flashable zip. I need to have what partition it's on and (since I guess it's /sys and not /system) be able to mount /sys so Tue file can be copied. The ROM I found it's for your phone. There seems to be very limited data on your phone. Like I said, I have the zip mostly set up, I just need to make sure my mount command will work and for that I need more info. I think I have it but I can't verify that I do.
Sent from my LG-P999 using xda premium
How can i help? I have sent you some info about partition on private msg...
Here is the file... It is zipped, just extract it...
About the partition, Mount command shows: "sysfs /sys sysfs rw, relatime 0 0 "
BTW, i have been checking and the correct path to the file is: "/sys/devices/platform/keypad-led.0/backlight/keypad-led"
The other path i told you before was a link to this one... Sorry...
Complete result of mount command:
$ mount
rootfs / rootfs rw,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/stl9 /system rfs rw,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=cp4370 0
/dev/stl10 /cache rfsrw,nosuid,nodev,relatime,vfat,llw,gid/uid/rwx,iocharset=cp437 0 0
/dev/stl6 /mnt/.lfs j4fs rw,relatime 0 0
/dev/stl12 /efs rfsrw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=cp437 0 0
/dev/stl11 /data rfsrw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=cp437 0 0
Can you do something with this? I hope so...
hmm, we may have to change our strategy, maybe not. I need to see about a couple of things before I have you try anything.
On an interesting note, I noticed that for /sys the values after realtime are 0 0, I'm mostly familiar with PC's and learn as I go on Android, but if that means what I think it means, that partition can't be modified at all while the system is booted.
On my phone that directory is mounted, but there are no files that I am able to view either via Droid Explorer or Root Explorer.
Do you know anyone else that could join us on this adventure? do you have anything else in mind? I am able to set the file to 0, but there are some events that set it back again to a certain value, like screen off and on, etc...
I dunno why or how, but i set it to 0, i apply chmod 444 but it still changes the file to a certain value...
News?
Yes.
Place the attached script in: /system/etc/init.d/
reboot and you should be good. Found the info here:
http://forum.xda-developers.com/showthread.php?t=1488492&page=4
Some say it works, some say it doesn't.
edit: file attached, just take it out of the zip file.
I don't have the folder /init.d/ in the /system/etc/ folder :|
This means i don't have init.d support...
Ok, i found a way to run it during boot time:
How to run the scripts during the boot using SManager:
Steps to run the scripts during the boot:
1. Test the scripts out completely before start to run on boot.
2. From the SManager tool, select su and boot icon. Exit the application and reboot the phone.
3. If you did not change the SManger config, then you will see the SManager log after the boot. Check if everything is fine. If the scripts run OK many times without any issue, then you can uncheck the option showing SManager log after the boot.
And during boot it writes 0 to the file and it changes its permissions to 444. But even without the permission to write on the file, the system is able to change the value in the file!
What is Link2SD?
Link2SD is an app for Android 2.0+ users on their phone to move applications to the SD card by dual-partitioning the card. First partition gets mounted as external SD and remains available for general use, while the second partition (preferably formatted with an *NIX type file-system, e.g. ext2, ext3, ext4 etc.) holds executable(.apk), data, dalvik-cache(.dex) and library files(.so) for linked/moved application.
Link2SD mounts the second partition of your SD card as /data/sdext2 and makes OS mounts it at boot time. When you select an application and press "Create Link" button you can select which files of the application will be linked and moved to SD card. Apk, dex and lib files can be moved and you can select all three or any two of three or even only one of them. Depending on what you select, Link2SD moves apk file, dalvik-cache (.dex) file and lib files (.so) to SD card's second partition and creates symbolic links in original directories. Phone must be Rooted, of course.
How does mounting of second SD partition work?
After the partitioned SD card is put in the phone, Link2SD asks you to select the file-system of the second partition on SD, just chose the one you used. Once /system/etc/init.d/11link2sd script is created, you have to restart the phone.
What is init.d support and why is it needed?
init.d directory is the container of start-up scripts in a *NIX type system. These scripts are execute during system boot.
Link2SD relies on the execution of /system/etc/init.d/11link2sd script which, in turn, mounts the second partition of SD card as /data/sdext2.
What is the Boot-Loop problem?
The SD card storage is dual-partitioned and put in the phone. Then, Link2SD generates mount script for the second partition of SD card and phone needs to be re-started. Some phones, e.g. Sony Xperia-L runs into infinite boot-sequence a.k.a. boot-loop. In this state, phone boot sequence starts, manufacturer logo is displayed proceeds for a few seconds and restarts. Only solution is to long press the power button or taking out the battery to switch the phone off.
Interestingly, if the dual-partitioned SD card is taken out and the phone is booted without SD card inserted, it boots normally.
What did I do with my Xperia-L so that it started boot-looping?
Rooted Xperia using Rootkit method. It leaved /system/etc/install_recovery.sh and /system/etc/init.d/00stop_ric scripts on the phone's file-system. (Script code listed below). I am using the rooted phone for months without any trouble.
Using an un-partitioned 32GB microSD card, formatted with FAT32, in the phone.
Deciding to give a try to Link2SD, I dual-partitioned the SD using Minitool Partition Manager. First partition was formatted with FAT32 while the second one was formatted with ext4. Sizes of partitions were around ~25GB and ~4.5GB respectively.
Installed Link2SD on phone.
Switched the phone OFF.
Put the dual-partitioned SD back in the phone slot.
Switched the phone ON.
Opened Link2SD app.
Link2SD immediately recognized the second partiton, asking me for its file-system type.
Selected ext4 from the list.
Link2SD generated the mount script and prompted for restart.
Restarted the phone.
Boot-Loop!!!
Switched the phone OFF by taking out battery.
Took the dual-partitioned memory card out.
Switched the phone ON.
Phone starts normally!!!
How did I solve the problem?
I installed Init.d Toggler app as described here.
As described here, I experienced the problem of first partition not being mounted. The error was related to SD Card being empty or the file-system damaged.
I re-formatted the first partition of SD with NTFS.
Installed Paragon exFAT, NTFS & HFS+ app.
Now, the first partition got mounted.
What does Init.d Toggler do?
Appends the following command at the end of /system/etc/install_recovery.sh: /system/bin/sysinit
Creates /system/bin/sysinit script.
Creates /system/etc/init.d directory to put the start-up scripts in.
Does REALLY lack of init.d support cause boot-loop problem?
As the Init.d Toggler solution says,
One of the requirements to use the Link2SD is the support to init.d scripts. Most of the custom roms support this, but not the stock one, giving a boot loop.
Click to expand...
Click to collapse
I doubt that to be the "real" problem underlying the hood. Why?
How come lack of init.d support cause the mount script /system/etc/init.d/11link2sd malfunction? At most, what could have happened is, it would NOT mount the second partition, that's it. Right? But, isn't it surprising to crash or the like during boot?
As stated, even prior to installing Link2SD, there always existed /system/etc/init.d/00stop_ric, which contains almost similar set of commands as that of mount script /system/etc/init.d/11link2sd created by Link2SD. It used to work like a charm. I guess, because of init.d support not being there in stock ROM, the script had never been executed before I used Init.d Toggler.
Had the lack of init.d support been the reason of boot-loop, how did the phone manage itself to boot normally with the dual partitioned SD card taken out? Please note that, the mount script was still residing in init.d directory.
To be noted that, Xperia L (Stock ROM) boots fine with a dual-partitioned SD card put in, though it never mounts the second partition.
At this point, can anyone help me investigate the root-cause behind the boot-loop problem? Can anyone come up with any idea or satisfactory answer to the query? Does anyone have any idea on how to approach the issue at hand?
Please find the relevant scripts below.
00stop_ric
Code:
#!/system/bin/sh
/system/xbin/busybox pkill /sbin/ric
mount -o remount,rw /
rm /sbin/ric
mount -o remount,ro /
/system/xbin/busybox pkill /sbin/ric
11link2sd
Code:
#!/system/bin/sh
#added by link2sd
LOG=/data/link2sd-11link2sd.log
echo "$(date) mounting..." > $LOG
sleep 2
mount -t ext4 -o rw /dev/block/vold/179:34 /data/sdext2 1>>$LOG 2>>$LOG
mount -t ext4 -o rw /dev/block/mmcblk1p2 /data/sdext2 1>>$LOG 2>>$LOG
mount >> $LOG
echo "$(date) mount finished" >> $LOG
install-recovery
Code:
#!/system/bin/sh
# If you're implementing this in a custom kernel/firmware,
# I suggest you use a different script name, and add a service
# to launch it from init.rc
# Launches SuperSU in daemon mode only on Android 4.3+.
# Nothing will happen on 4.2.x or older, unless SELinux+Enforcing.
# If you want to force loading the daemon, use "--daemon" instead
/system/xbin/daemonsu --auto-daemon &
# Some apps like to run stuff from this script as well, that will
# obviously break root - in your code, just search this file
# for "install-recovery-2.sh", and if present, write there instead.
/system/bin/sysinit
sysinit
Code:
#!/system/bin/sh
export PATH=/sbin:/system/sbin:/system/bin:/system/xbin
/system/bin/logwrapper /system/xbin/run-parts /system/etc/init.d
link2sd-11link2sd
Code:
Wed Jul 23 16:23:57 IST 2014 mounting...
mount: Device or resource busy
mount: Device or resource busy
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,nosuid,nodev,relatime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/ftmd /ftmd ext4 rw,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/LTALabel /lta-label ext4 rw,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/ftma /ftma ext4 ro,relatime,nobarrier,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk1p1 /storage/sdcard1 fuseblk rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096 0 0
/dev/block/vold/179:34 /data/sdext2 ext4 rw,relatime,data=ordered 0 0
/dev/block/vold/259:0 /storage/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/259:0 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /storage/sdcard0/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/uk.co.aifactory.chessfree-2 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-1 /mnt/asec/com.wave18.adbwireless-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-2 /mnt/asec/com.rerware.android.MyBackupRoot-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-3 /mnt/asec/com.rootuninstaller.free-2 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
Wed Jul 23 16:23:59 IST 2014 mount finished