If anybody here doesn't mind testing, could you check out the following thread and test the new z4mod app on your Fascinate? I only have an I9000, but the app (and lagfix) should work fine on the Fascinate as well. Let me know please!
http://forum.xda-developers.com/showthread.php?p=9307467#post9307467
I'm looking at z4zipgen.sh..
I see this..
Code:
sed -i 's|run_program("/sbin/z4mod".*|run_program("/sbin/z4mod", "data", "mmcblk0p2", "'$1'");|g' "${script}"
which makes me think that i9000 data is on mmcblk0p2? Because that is our data/fota...
This is mount from our devices.
Code:
mount
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
/dev/block/stl6 /mnt/.lfs j4fs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
/dev/block/stl9 /system rfs rw,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p1 /data rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,ioc
harset=utf8 0 0
/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocha
rset=utf8 0 0
/dev/block/mmcblk0p2 /data/fota rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rw
x,iocharset=utf8 0 0
/dev/block/mmcblk0p3 /preinstall rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/r
wx,iocharset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iochar
set=utf8 0 0
/dev/block//vold/179:9 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=
1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,s
hortname=mixed,utf8,errors=remount-ro 0 0
RyanZA said:
If anybody here doesn't mind testing, could you check out the following thread and test the new z4mod app on your Fascinate? I only have an I9000, but the app (and lagfix) should work fine on the Fascinate as well. Let me know please!
http://forum.xda-developers.com/showthread.php?p=9307467#post9307467
Click to expand...
Click to collapse
Tried, No such luck
Should I be running a stock kernal?
Doesn't matter, really. z4mod doesn't use the correct mountpoints for us.
I used it with no problems. It installed clockworkmod for me.
jeffbeagley said:
I used it with no problems. It installed clockworkmod for me.
Click to expand...
Click to collapse
What are your quadrant scores?
If it roots and installs clockwork, it is already an easier root than the manual method.
Frankly, it would be less useful to me if it installed voodoo...
Sent from my stupidfast blackish hole...
I am fairly new to Android (just switched from iPhone). Will rooting a phone break the ability to receive OTA updates?
Is stupidfast compatible with this I tried patching but it failed
Chuban7 said:
Is stupidfast compatible with this I tried patching but it failed
Click to expand...
Click to collapse
This is an un root method from what I understand. If you're using an alternate kernel, you are already un rooted.
eriknokc said:
I am fairly new to Android (just switched from iPhone). Will rooting a phone break the ability to receive OTA updates?
Click to expand...
Click to collapse
Root just means to 'gain root access' to your phone, usually by having a 'su' (superuser) binary in your bin/xbin directory, and by having a Superuser.apk (Superuser App) that uses this binary when an app wants Superuser permissions. (in other words, you can delete system files, do things with the hardware that the original manufacturer did not intend, etc etc).
Unrooting technically just involves deleting the 'su' binary and uninstalling/deleting the Superuser App.
NOW
If you install a custom Recovery (it's a separate partition on your phone - basically like a second hard drive on your computer) which you can boot up from, such as ClockworkMod, you can install custom ROMs (such as the ones you'll see in this development section), and SOME of those may or may not have OTA updates disabled.
Typically developers will set up ROMs with all of the latest OTA fixes and things anyway, or the ROMs will be based on the latest OTA builds. So not having OTA updates is virtually meaningless if you keep your ROM up to date. Once in a while OTA updates will do what Apple's iOS updates do - which means fixing a security hole that allowed Rooting.
So in short, just having root access does NOTHING to OTA updates. Installing a custom ROM that has OTA updates disabled, and/or going into whatever directories necessary to delete the OTA Certs file by using your root access CAN disable OTA updates.
Chuban7 said:
Is stupidfast compatible with this I tried patching but it failed
Click to expand...
Click to collapse
did you flash clockworkmod recovery through odin first? lastest stupidfast 1.5.4 test version should work on stock kernel but you'll lose haptic feedback, unless you have DJ05 handy.
I just got a white fascinate from bestbuy on Friday. For only $1 I thought it was time to upgrade from the original Droid. I have experience with rooting, my Droid was rooted since day one. I don't consider myself a noob but I also wouldn't consider myself a master at it. I've been reading all the root methods but they require a PC, which I don't currently have access to. So I found z4root and fired it up. Got root and it seemed simple. Installed busybox and super user.
I attempted to install clockwork through rom manager and it said it was successful so I downloaded super clean rom. Rebooted into recovery to find it didn't install, researched and found an update.zip to access clockwork and that didnt work. Got a signature verification error.
Downloaded root explorer to apply the 3g speed fix. Went to remount system as r/w but can not do that. Root explorer has super user permissions but I can not change folders or files to r/w access.
I'm not sure if its a problem with z4root or if having a white fascinate is to blame? Any input is grately appreciated. Thanks!
ms262c said:
I just got a white fascinate from bestbuy on Friday. For only $1 I thought it was time to upgrade from the original Droid. I have experience with rooting, my Droid was rooted since day one. I don't consider myself a noob but I also wouldn't consider myself a master at it. I've been reading all the root methods but they require a PC, which I don't currently have access to. So I found z4root and fired it up. Got root and it seemed simple. Installed busybox and super user.
I attempted to install clockwork through rom manager and it said it was successful so I downloaded super clean rom. Rebooted into recovery to find it didn't install, researched and found an update.zip to access clockwork and that didnt work. Got a signature verification error.
Downloaded root explorer to apply the 3g speed fix. Went to remount system as r/w but can not do that. Root explorer has super user permissions but I can not change folders or files to r/w access.
I'm not sure if its a problem with z4root or if having a white fascinate is to blame? Any input is grately appreciated. Thanks!
Click to expand...
Click to collapse
You have to flash CWM through Odin my friend.http://forum.xda-developers.com/showthread.php?t=788099
z4root makes no different.
good luck
Need help unrooting!
How do I unroot my phone to take it back to stock? I have tried the unroot option in Z4root, but it doesn't seem to have done anything. Any suggestions? Thank you.
slvrevoix said:
You have to flash CWM through Odin my friend.http://forum.xda-developers.com/showthread.php?t=788099
z4root makes no different.
good luck
Click to expand...
Click to collapse
Thanks for letting me know that! My only other problem is no r/w access to the system files. Any suggestions?
ms262c said:
Thanks for letting me know that! My only other problem is no r/w access to the system files. Any suggestions?
Click to expand...
Click to collapse
are you using root explorer? does it give you the option to set r/w? i just used z4root from the market and it seems to work fine for me. completed and got asked for superuser access when i loaded up root explorer
Related
How to Voodoo
As long as you have the new CWM for all ROM's these instructions should work for 2.1 AND 2.2.
New CWM for all ROM's:
http://forum.xda-developers.com/showthread.php?t=942021
Thank JT1134 for this.
Make sure to thank Adrynalyne, Jt1134, times_infinity, imnuts and nemesis2all for the great kernels we have.
If you flash a ROM that has a voodoo kernel built in to the .zip, flash that ROM and skip to step 5.
I thought it was time I stopped saying “Stay away from voodoo!!!!”. While I still think noobs should stay away, at least until they gain experience and confidence with their phones, I no longer hate voodoo. In fact I will admit, very grudgingly, I do notice a little, not much, but a little extra zip in my phone. It actually isn’t that hard to figure out as long as you follow some simple rules:
1. Don’t panic. I seriously doubt you can screw up your phone worse than I have screwed up mine. Everything is un-screw-able.
2. Don’t flash a non-voodoo kernel over a voodoo kernel. If you do stupid crap will happen to your phone. It won’t boot for one, and you will break CWM.
Voodoo is a kernel replacement. Our phones use a proprietary RFS file system built as a legacy FAT, adding indexing and POSIX permission on the internal 2gb SD card. There is nothing wrong with RFS, but it’s slow. From what I understand it indexes everything. This takes time, causing lag. Voodoo reformats the internal SD card with standard Linux EXT4. EXT4 is a faster. This filing system is what is reffered to as the lag fix.
Voodoo also makes the screen sharper, and has some improvemnets to sound quality as well. These have nothing to do with the lag fix portion of voodoo.
Note: Voodoo screen and sound enhancements are now available in Froyo as we have the source code.
To utilize Voodoo sound enhancement you need to download Voodoo Control from the market.
To utilize BLN you need to download BLN control from the market.
Voodoo color is passive, however you the brightness needs to be set to 100% and auto brightness turned off.
This is step by step what I did. I will assume you have an intermediate understanding of how to root and mess around with your phone. You will need to know how to use Odin, flash back to stock, hot to boot into recovery and how to put your phone into download mode. If you are not completely comfortable with ALL of these procedures, DO NOT TRY THIS!!
1. I wanted to start with out of the box new. So I formatted my SD card and flashed back to stock. I flashed to stock DJ05, but this should work for DL09 and DI01 as well DL30 and EB01.
NOTE: It is not nessicarry to start from stock, it jsut the place i picked so all steps would be covered.
2. Now that we are back to stock we need to root. I used the “Gunnermike53 lazy root” method. I dropped Superdark ROM v1 for DJ05 and Test 6 Low voltage voodoo from Adrynalyne (you can use whatever ROM and kernel you want) on my SD Card. I put the phone into download mode and flashed CWM Red.
NOTE: If you already have the new RED CWM it is not nessicarry to flash CWM again.
3. Boot into recovery. You will go straight to CWM Red, no blue. Clear your data and cache. Then select “install zip from sdcard”. Select “choose zip from sdcard”. Select your ROM then hit yes. When it’s finished you will be back at the second menu page again. If you restart your phone at this point you will have a fully rooted phone, with a stock kernel. But don’t reboot.
4. Next you will select “choose zip from sdcard”, select your kernel and then yes.
5. When it’s done, press the menu soft button on the bottom left of the phone. This will take you back to the first page.
Go down and select voodoo. Then you will select “enable lag fix”.
6. When that’s done, press the soft menu button and then reboot.
7. Wait.
8. Wait.
9. Wait.
10. Seriously, it takes anywhere 2 to 15 minutes. During this time you will hear a female robot (or perhaps, a female android ) talking.
11. Once the phone restarts you are done!
It’s that easy. The key to all the simple-ness is Red CWM.
Thanks to Adrynalyne for the kernel and bringing our attention to the Red CWM, and to Thatdudebutch for superdark, and I don’t know who to thank for Red CWM, somebody help me out here. Let me know if I missed anything or got something wrong and I will fix it.
How to UnVoodoo
How to UnVoodoo
The key to uninstalling voodoo is Red CWM. To be specific you don’t uninstall voodoo, you disable the lag fix. Once that’s done you can flash a new non-voodoo kernel.
1. Boot into recovery. You should be in Red CWM.
2. Select “voodoo”.
3. Select “disable lag fix”.
4. Press soft menu button.
5. Select “reboot system now”
6. Wait.
7. Wait.
8. Wait.
9. Wait. Just like during the install, this will take 2-15 minutes, while its reformatting your internal SD card.
10. Your phone will then restart. At this point you still have a voodoo kernel, the lag fix has just been disabled. Red CWM is now broke. No biggie.
11. Re-flash Red CWM with Odin.
12. Reboot into recovery.
13. Flash non-voodoo kernel of your choice.
Note: If you are flashing from one voodoo kernel to another, you do not need to disable lag fix.
Just a couple notes to the first timers: (The credit for this clairifacation goes to GizmoDroid)
1.Most ROM's currently are bundled with a kernel. For example, SuperClean installs CWM, kernel, and system image all in one flash, so no need to flash a separate kernel or CWM after flashing the ROM.
2.Currently, in the newest RED CWM, there are two enable options in the voodoo menu:
•"enable lagfix" - this converts all rfs partitions to ext4 except your "system" partition
•"/system lagfix" - this converts your "system" rfs partition to ext4
You will need to hit both of them for full optimization.
After selecting "enable lagfix", the text at the bottom will change to:
Code:
Voodoo lagfix is actually: disabled
next boot: enabled
Options:
/system lagfix conversion: yes
debug mode: no
Unfortunately, the current CWM has a little glitch that can be confusing. After rebooting, "Voodoo lagfix is actually:" is supposed to change to "enabled" but it will always say "disabled". Rest assured though, it is enabled.
Hopefully this will get fixed when a new version comes along.
OOPS!!!!
Trouble Shooting.
In order to trouble shoot i had to create some trouble to shoot. So i decided to break the rules.
Rule # 1. Dont panic. I started with rule number one because that seemed the logical place to start. However i had nothing to panic about, so i just looked silly. We wont talk about that.
Rule # 2. Dont flash a non voodoo kernel over a voodoo kernel without disableing the lag fix first. I got some results out of this. I bricked my phone. As I have done this 5000000000 times before, I still had no luck with rule number one. My phone how would no longer boot past the Samsung screen. so i rebooted into recovery, and got blue CWM. I tried to apply update.zip and got E:fail blah blah blah.
The reason for this is the filing system is still EXT4. A non voodoo kernel does not know how to talk EXT4, it only speaks RFS. In order to fix the brick we have to do the missing step, disable lag fix.
1. Put the phone in download mode and flash Red CWM.
2. Reboot into recovery. You should now have Red CWM.
3. Select "voodoo"
4. Select "disable lag fix"
5. When you return to the menu, press the menu soft button
6. Reboot. Again this will take 2-15 minutes as the filing system is converted from EXT4 to RFS.
Thats it. That is the only problem I could make happen related to voodoo. I am having a hard time believing its that easy, but it is.
It is often asked "How do I know if I have voodoo?" The simplest way is to run an app called Quadrent. Quadrent is a benchmark app. Scores above 1000 means you have voodoo. Quadrent is not the proper way to check. The more I think about this, the more I think you should learn the proper way. It will give you a greater understanding of what is going on with your phone.
The proper way is to use a terminal emulator and type "mount".
You will see this:
Code:
mount
rootfs / rootfs rw 0 0
proc /proc proc rw,relatime 0 0
sys /sys sysfs rw,relatime 0 0
/dev/block/stl9 /system ext4 rw,relatime,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/stl11 /cache ext4 rw,noatime,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/stl10 /dbdata ext4 rw,noatime,barrier=0,nodelalloc,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p1 /data ext4 rw,noatime,barrier=1,data=ordered,noauto_da_alloc
the ext4 is what you are looking for. If you see RFS in any of the 4 locations you dont have voodoo or just one of the partitions has voodoo.
Wow, good job spelling this out. I'm not on voodoo yet but when I feel I'm ready I'll be heading to this thread to make sure I don't screw anything up.
Zacisblack said:
Wow, good job spelling this out. I'm not on voodoo yet but when I feel I'm ready I'll be heading to this thread to make sure I don't screw anything up.
Click to expand...
Click to collapse
hope it helps. just ask if yuou have questions.
You did a really GOOD JOB in spelling out voodoo / non voodoo.
Thanks
I was under the impression that the new versions of Voodoo only had the lagfix for EB01 and DL30 because we didn't have a source kernel from Samsung for the Fascinate. I know I haven't been able to access voodoo sound yet and am really anticipating that feature, but if I'm behind or missing something that I can do to get that feature PLEASE let me know.
I made a note regaurding that. When I get to a computer I will make it bold.
Sent from my SCH-I500 using XDA App
Whenever I boot the phone I get the electronic female voice telling me "Convert data partition: System not available. Convert system partition: System not available." What am I doing wrong?
Never mind. It wasn't working under SC 2.7.1, but after flashing to 2.8 it converted and seems to be working.
gunnermike said:
4. Next you will select “choose zip from sdcard”, select your kernel and then yes.
5. When it’s done, press the menu soft button on the bottom left of the phone. This will take you back to the first page.
Go down and select voodoo. Then you will select “enable lag fix”.
6. When that’s done, press the soft menu button and then reboot.
Click to expand...
Click to collapse
Just a couple notes to the first timers:
Most ROM's currently are bundled with a kernel. For example, SuperClean installs CWM, kernel, and system image all in one flash, so no need to flash a separate kernel or CWM after flashing the ROM.
Currently, in the newest RED CWM, there are two enable options in the voodoo menu:
"enable lagfix" - this converts all rfs partitions to ext4 except your "system" partition
"/system lagfix" - this converts your "system" rfs partition to ext4
You will need to hit both of them for full optimization.
After selecting "enable lagfix", the text at the bottom will change to:
Code:
Voodoo lagfix is actually: disabled
next boot: enabled
Options:
/system lagfix conversion: yes
debug mode: no
Unfortunately, the current CWM has a little glitch that can be confusing. After rebooting, "Voodoo lagfix is actually:" is supposed to change to "enabled" but it will always say "disabled". Rest assured though, it is enabled.
Hopefully this will get fixed when a new version comes along.
GizmoDroid said:
Just a couple notes to the first timers:
Most ROM's currently are bundled with a kernel. For example, SuperClean installs CWM, kernel, and system image all in one flash, so no need to flash a separate kernel or CWM after flashing the ROM.
Currently, in the newest RED CWM, there are two enable options in the voodoo menu:
"enable lagfix" - this converts all rfs partitions to ext4 except your "system" partition
"/system lagfix" - this converts your "system" rfs partition to ext4
You will need to hit both of them for full optimization.
After selecting "enable lagfix", the text at the bottom will change to:
Code:
Voodoo lagfix is actually: disabled
next boot: enabled
Options:
/system lagfix conversion: yes
debug mode: no
Unfortunately, the current CWM has a little glitch that can be confusing. After rebooting, "Voodoo lagfix is actually:" is supposed to change to "enabled" but it will always say "disabled". Rest assured though, it is enabled.
Hopefully this will get fixed when a new version comes along.
Click to expand...
Click to collapse
Thanks for the clairification. i will update the OP as soon as i get back back from fixing this ladies internet and replaceing a DVR.
good job explaining voodoo. i love the extra it gives i have been using voodoo for months since i got this phone. this would have been helpful then cuz man i cant tell you how many times i cranked up odin because of voodoo. but i have to say i wont be without voodoo on my phone.
I just upgraded to from non-voodoo SuperClean to voodoo SC2.8 with eb01 radio. I've enabled voodoo/lagfix several times from clockwork but only get Quadrant scores in the 900's. Any idea if something is wrong?
harpdoc said:
I just upgraded to from non-voodoo SuperClean to voodoo SC2.8 with eb01 radio. I've enabled voodoo/lagfix several times from clockwork but only get Quadrant scores in the 900's. Any idea if something is wrong?
Click to expand...
Click to collapse
which cwm are you using?
The latest Red one
harpdoc said:
The latest Red one
Click to expand...
Click to collapse
ok. first are you sure that you dl'ed the the voodoo version?
if so reflash the rom. restart the phone. reboot to recovery. enable lag fix.
It's called super_frankenclean_2_8v_final.zip, so I think it's the right one. I reflashed it but no change. Just to be safe I'm re-downloading the rom and will try again. Strange.
I didn't hear a females voice. I went from 2.8nv to 2.8 V following this verbatim, with the exception of the blue CWM, instead of red, but I fixed that. I scored a 926. I'm a little nervous to do much, because my phones my internet. I brick it, I wait....
thanks for any advice
EDIT: 2nd try, i get quadrant score at 946, but the phone feels a lot faster. took about 2 mins to reboot and still no female voice.
For those that didn't hear a robot voice, and getting low quadrant scores: I'm sorry but you haven't successfully activated the lagfix... but it might not be your fault (maybe ).
Right now, there seems to be something not working for some people. I haven't had any problems myself, but several are not able to trigger the data conversion. Adrynalyne has posted the EB01 voodoo kernel to flash after sc2.8, if you are having problems.
The actual way to test to see if you have the lagfix enabled is not quadrant, but to open up adb or a terminal emulator and type "mount".
This is what a successful lagfix enabled system looks like:
Code:
mount
rootfs / rootfs rw 0 0
proc /proc proc rw,relatime 0 0
sys /sys sysfs rw,relatime 0 0
/dev/block/stl9 /system [COLOR="Red"][B]ext4 [/B][/COLOR]rw,relatime,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/stl11 /cache [COLOR="Red"][B]ext4 [/B][/COLOR]rw,noatime,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/stl10 /dbdata [COLOR="Red"][B]ext4 [/B][/COLOR]rw,noatime,barrier=0,nodelalloc,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p1 /data [COLOR="Red"][B]ext4 [/B][/COLOR]rw,noatime,barrier=1,data=ordered,noauto_da_alloc 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,relatime,size=4096k 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p2 /data/fota rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p3 /preinstall rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/vold/179:9 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,code
page=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:9 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,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
If you run "mount" and it says "rfs" where the red is above, then you do not have voodoo lagfix successfully enabled.
I just reflashed the EB01 Voodoo kernel, enabled lagfix, and rebooted. Wallah, I have the lady robot voice! I can't wait for my phone to reboot and get my first taste of Voodoo! Thanks to everyone for the help!
Please Click me to go to my latest post . i need serious help now .. im scared i really screwed up .. :'(
Try the signing hack in the following thread
forum.xda-developers.com/showthread.php?t=1111476
allisterw said:
Try the signing hack in the following thread
forum.xda-developers.com/showthread.php?t=1111476
Click to expand...
Click to collapse
I cant boot the phone at all .. do you know if there is a fastboot option on the device ??? that would be awesome .
I am unfamiliar with your phone nor which
custom recovery you installed.
See this post http://forum.xda-developers.com/showpost.php?p=22278362&postcount=212
for way to get the latest firmware specific to your phone.
If you don't mind losing the data on the phone,
you can try a factory reset.
Instructions on Pg 96 in the manual here:
http://www.net10.com/Common/Both/Digital_Assets/16899.pdf
Good luck.
allisterw said:
I am unfamiliar with your phone nor which
custom recovery you installed.
See this post http://forum.xda-developers.com/showpost.php?p=22278362&postcount=212
for way to get the latest firmware specific to your phone.
If you don't mind losing the data on the phone,
you can try a factory reset.
Instructions on Pg 96 in the manual here:
http://www.net10.com/Common/Both/Digital_Assets/16899.pdf
Good luck.
Click to expand...
Click to collapse
There is no custom recovery , thats the whole problem . If there were a custom recovery i could easily toggle signature verification and boom it would flash . But thanks for the links i'll check them out ! Oh and a factory reset will not work because the file i edited is in system partition NOT data partition .
Have you tried ADB?
http://developer.android.com/guide/developing/tools/adb.html
adb devices
adb remount
adb push <local filename> <remote filename>
allisterw said:
Have you tried ADB?
http://developer.android.com/guide/developing/tools/adb.html
adb devices
adb remount
adb push <local filename> <remote filename>
Click to expand...
Click to collapse
Lol a day late and a dollar short i literally just did the exact same thing last night . however , adb remount fails .. i did adb shell and then su and it wont let me get superuser rights even though the device was rooted . so i just did adb push and pushed the original framework-res.apk to the device and now instead of staying at the splash screen im in an ifinite boot loop at the boot animation .
is there any way i can boot the device into fastboot mode so i can flash a custom ROM i found ? i tried adb reboot-bootloader and it just reboots regularly . Im at a loss of things to do other than contact straight talk and cross my fingers .
Oh also is there a way i can backup the data partition on the device ? That way if i have to get a new phone i wont lose anything ? Like can i make a .img from my data partition ?
elesbb said:
Lol a day late and a dollar short i literally just did the exact same thing last night . however , adb remount fails .. i did adb shell and then su and it wont let me get superuser rights even though the device was rooted .
Click to expand...
Click to collapse
So if adb works, you should try rerooting via lge_adb.conf trick and superoneclick
http://androidflip.com/how-to-root-lg-optimus-one-p500-android-2-3-3-gingerbread/
elesbb said:
is there any way i can boot the device into fastboot mode so i can flash a custom ROM i found ? i tried adb reboot-bootloader and it just reboots regularly . Im at a loss of things to do other than contact straight talk and cross my fingers .
Click to expand...
Click to collapse
Fastboot on the P500 is Home Key + Power. YMMV.
elesbb said:
Oh also is there a way i can backup the data partition on the device ? That way if i have to get a new phone i wont lose anything ? Like can i make a .img from my data partition ?
Click to expand...
Click to collapse
from the shell you should be able to use dd command to backup the partitions.
do a cat /proc/mounts to find out the block devices names.
read http://forum.xda-developers.com/showthread.php?t=1124939
allisterw said:
So if adb works, you should try rerooting via lge_adb.conf trick and superoneclick
http://androidflip.com/how-to-root-lg-optimus-one-p500-android-2-3-3-gingerbread/
Click to expand...
Click to collapse
Havent tried this yet but i tried the original root that i did for my phone which is an LG Optimus Q remember ..
Fastboot on the P500 is Home Key + Power. YMMV.
Click to expand...
Click to collapse
It didnt work for my LG Optimus Q .. Home + Vol Down + Power gets me to recovery :/
from the shell you should be able to use dd command to backup the partitions.
do a cat /proc/mounts to find out the block devices names.
read http://forum.xda-developers.com/showthread.php?t=1124939
Click to expand...
Click to collapse
Of course .. i cant freaking mount the sdcard -.- i wonder why its not working when i adb pushed the original file .. ugh fml
elesbb said:
Havent tried this yet but i tried the original root that i did for my phone which is an LG Optimus Q remember ..
Click to expand...
Click to collapse
Wasn't saying it would definitely work with the lg55c but your original rooting appeared to put your phone in a strange state.
adb push should not have worked if you weren't able to remount /system as rw.
elesbb said:
It didnt work for my LG Optimus Q .. Home + Vol Down + Power gets me to recovery :/
Click to expand...
Click to collapse
There are 3 other key combos you could try.
Menu + Power.
Back + Power. (This combo puts my HTC G1 into fastboot)
Search + Power.
elesbb said:
Of course .. i cant freaking mount the sdcard -.- i wonder why its not working when i adb pushed the original file .. ugh fml
Click to expand...
Click to collapse
Your sdcard should have automounted at /mnt/sdcard if you turned off usb storage.
allisterw said:
adb push should not have worked if you weren't able to remount /system as rw.
Click to expand...
Click to collapse
Opps... it appears I was wrong regarding adb remount.
ezterry said:
http://forum.xda-developers.com/showthread.php?t=811620
* adb remount doesn't work and this rom doesn't have root.. yes 'adb remount' fails because this is a stock rom.. however NO just because that fails doesn't mean there is no root.
Click to expand...
Click to collapse
If your phone is not rooted, go to a service center
I was born in the '90's... 1290's >
vlt96 said:
If your phone is not rooted, go to a service center
I was born in the '90's... 1290's >
Click to expand...
Click to collapse
Straight Talk has a service center ?
allisterw said:
Your sdcard should have automounted at /mnt/sdcard if you turned off usb storage.
Click to expand...
Click to collapse
Well my luck it doesnt as seen by mount command listed below
Code:
$ mount
mount
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
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
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mtdblock6 /system yaffs2 rw,relatime 0 0
/dev/block/mtdblock7 /data yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock9 /persist yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock1 /cache yaffs2 rw,nosuid,nodev,relatime 0 0
And the error when i try to mount the sd card
Code:
$ mount -o remount, rw /mnt/sdcard
mount -o remount, rw /mnt/sdcard
mount: Operation not permitted
elesbb said:
Well my luck it doesnt as seen by mount command listed below
Click to expand...
Click to collapse
Go into the Storage settings. Make sure that it is not set to Mass storage only.
I don't know what else to suggest anymore.
Sorry and Good Luck.
allisterw said:
Go into the Storage settings. Make sure that it is not set to Mass storage only.
I don't know what else to suggest anymore.
Sorry and Good Luck.
Click to expand...
Click to collapse
remember ... the phone is stuck in an infinate boot loop .... and i know same here but i thank you very much for all of your help
I have two suggestions:
Can you phone boot in emergency mode? If yes you can try flash the stock rom....
And wen you moved your modied file to your phone did you put proper permissions??
Sorry for my bad english and good luck
Sent from my LG-P500 using xda premium
elesbb said:
remember ... the phone is stuck in an infinate boot loop .... and i know same here but i thank you very much for all of your help
Click to expand...
Click to collapse
Read about and used this trick to bypass Google setup when rooting the HTC Dream.
It brings up the Settings menu to allow you to turn on wifi.
But you could try it to check on the other settings.
adb usb
adb devices
adb shell
am start -a android.intent.action.MAIN -n com.android.settings/.Settings
Ok. This is THE final suggestion.
Out of curiosity couldn't we just use a command line to mount the system as R/W and push Busybox, Su app and Su binary to the proper locations.
Sent from my ADR6410LVW using xda app-developers app
Or atleast use a recovery exploit
Sent from my ADR6410LVW using xda app-developers app
No the system wont allow it... We have to find a way in right now the system just overrides everything
Sent from my ADR6410LVW using xda app-developers app
Have you guys tried this?
http://forum.xda-developers.com/showthread.php?t=1706588
-viperboy- said:
Have you guys tried this?
http://forum.xda-developers.com/showthread.php?t=1706588
Click to expand...
Click to collapse
It has been attempted.
http://forum.xda-developers.com/showthread.php?p=30394502&highlight=debugfs#post30394502
What about writing a custom hboot and hex editing it as an upgrade? It's been successful on other devices example is the blackrose hboot for nexus, incredible s and others
Sent from my ADR6410LVW using xda app-developers app
IceDragon59 said:
It has been attempted.
http://forum.xda-developers.com/showthread.php?p=30394502&highlight=debugfs#post30394502
Click to expand...
Click to collapse
RevolutionaryPC said:
What about writing a custom hboot and hex editing it as an upgrade? It's been successful on other devices example is the blackrose hboot for nexus, incredible s and others
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
check out viperboy's thread in general hes looking for testers/help to try some things
RevolutionaryPC said:
What about writing a custom hboot and hex editing it as an upgrade? It's been successful on other devices example is the blackrose hboot for nexus, incredible s and others
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
Could potentially work, but that is VERY risky as it can perma-brick the device.
... I'm going to try the replacing the recovery.IMG in stock ruu with an open source One..if it goes sideways I've always got the 15 month warranty
Sent from my ADR6410LVW using xda app-developers app
RevolutionaryPC said:
... I'm going to try the replacing the recovery.IMG in stock ruu with an open source One..if it goes sideways I've always got the 15 month warranty
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
Good luck
RevolutionaryPC said:
... I'm going to try the replacing the recovery.IMG in stock ruu with an open source One..if it goes sideways I've always got the 15 month warranty
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
That's not going to work man. It checks the signature before you flash it.
-viperboy- said:
Have you guys tried this?
http://forum.xda-developers.com/showthread.php?t=1706588
Click to expand...
Click to collapse
I tried the debugfs trick with no success. I studied all the methods described in the following threads as well. I even have a rooted TF101 and did some comparisons on the file structures, haven't found anything useful there.
http://forum.xda-developers.com/showthread.php?t=1704209
http://forum.xda-developers.com/showthread.php?t=1622628
I'm no debugfs expert, though, so I might have missed something. I was seeing permission denied when debugfs tried to get write access. I suspect this is because the system wasn't mounting the symlink target as R/W on boot like on other devices. I can try it some more if you have ideas I might have missed though... I still have all the binaries pushed via adb to the device to /data/local/tmp/ (which, on this device, is a folder where shell user can write; though, unfortunately, I can't move or rename the folder itself, likely due to parent permissions). All my symlink attempts have been to targets inside this dir since I can't find any others that will allow it. For example:
Code:
ln -s /dev/block/mmcblk0p33 /data/local/tmp/mmcblk0p33
If we knew a dir on /data that gives shell user or adb group enough permission to symlink to /system with write access, then that trick might still work. Only /data partition (or perhaps /cache or /devlog) will work since they are ext4... All other partitions are types that don't support symlinks.
On Ubuntu 12.04, I tried mounting partitions from the RUU. I can mount /system on my machine, but I still can't figure out how to mount /data outside of the device. I thought this might give me a way to list all contents of /data on a system where I have root already, and then I could try each one as a symlink target on the device. So far I'm not having luck with that approach... Anyone with more Rom knowledge know how I can do that? Ideally, I'd like to mount the ENTIRE filesystem for this device (/data in particular) from the RUU onto my Ubuntu system and poke around more.
On a separate type of attempt, I dug into some scripts inside the /system dir (from the RUU, but mounted on Ubuntu 12.04 so I can view everything). I'm looking in /system/etc/init.qcom.dsps_links.sh, line 77. I see that, if no results are returned trying to list /firmware_dsps/dsps*, then the system will be remounted RW long enough to create the symlinks. A similar case statement also exists in init.qcom.modem_links.sh, for the same reason (a check if links are missing, then a remount in RW mode to create them). How we exploit that is another consideration. Anyone know how we might take advantage of this? It seems like it will be difficult without (a) removing the symlinks, and (b) "pausing" the bootup process just after that step long enough to push su binary to /system/xbin. Since we would already need root to do either of those things, I'm not convinced this is even worth pursuing unless somebody has ideas I'm missing.
Any other ideas? One other I've been looking at is setting ro.kernel.qemu=1 in a file called /data/local.prop. This would make the OS boot as if it's an AVD, thus giving shell root by default. Again, you need to be rooted already (or somehow elevated, e.g. via some other exploit) to write this file, so maybe another dead end here.
Also, I'm sure I'm not the first to try this, but I've also checked all known exploits using the "X-Ray" app at http://www.xray.io/. Normally, I'd be quite pleased to learn that I'm patched against all those exploits. Unfortunately, not this time.
And then, of course, there was my attempt to use mempodroid (before I discovered X-Ray and learned that it's not vulnerable). The kernel version "should" support it, but they must have applied Linus' patch to their kernel before this device hit the market. I've suspected ever since that this was the reason the Fireball release date kept getting pushed back, but we can't know for sure.
Sent from my ADR6410LVW using xda app-developers app, edited from a device where I have Admin rights
CaptainRewind said:
I tried the debugfs trick with no success. I studied all the methods described in the following threads as well. I even have a rooted TF101 and did some comparisons on the file structures, haven't found anything useful there.
http://forum.xda-developers.com/showthread.php?t=1704209
http://forum.xda-developers.com/showthread.php?t=1622628
I'm no debugfs expert, though, so I might have missed something. I was seeing permission denied when debugfs tried to get write access. I suspect this is because the system wasn't mounting the symlink target as R/W on boot like on other devices. I can try it some more if you have ideas I might have missed though... I still have all the binaries pushed via adb to the device to /data/local/tmp/ (which, on this device, is a folder where shell user can write; though, unfortunately, I can't move or rename the folder itself, likely due to parent permissions). All my symlink attempts have been to targets inside this dir since I can't find any others that will allow it. For example:
Code:
ln -s /dev/block/mmcblk0p33 /data/local/tmp/mmcblk0p33
If we knew a dir on /data that gives shell user or adb group enough permission to symlink to /system with write access, then that trick might still work. Only /data partition (or perhaps /cache or /devlog) will work since they are ext4... All other partitions are types that don't support symlinks.
On Ubuntu 12.04, I tried mounting partitions from the RUU. I can mount /system on my machine, but I still can't figure out how to mount /data outside of the device. I thought this might give me a way to list all contents of /data on a system where I have root already, and then I could try each one as a symlink target on the device. So far I'm not having luck with that approach... Anyone with more Rom knowledge know how I can do that? Ideally, I'd like to mount the ENTIRE filesystem for this device (/data in particular) from the RUU onto my Ubuntu system and poke around more.
On a separate type of attempt, I dug into some scripts inside the /system dir (from the RUU, but mounted on Ubuntu 12.04 so I can view everything). I'm looking in /system/etc/init.qcom.dsps_links.sh, line 77. I see that, if no results are returned trying to list /firmware_dsps/dsps*, then the system will be remounted RW long enough to create the symlinks. A similar case statement also exists in init.qcom.modem_links.sh, for the same reason (a check if links are missing, then a remount in RW mode to create them). How we exploit that is another consideration. Anyone know how we might take advantage of this? It seems like it will be difficult without (a) removing the symlinks, and (b) "pausing" the bootup process just after that step long enough to push su binary to /system/xbin. Since we would already need root to do either of those things, I'm not convinced this is even worth pursuing unless somebody has ideas I'm missing.
Any other ideas? One other I've been looking at is setting ro.kernel.qemu=1 in a file called /data/local.prop. This would make the OS boot as if it's an AVD, thus giving shell root by default. Again, you need to be rooted already (or somehow elevated, e.g. via some other exploit) to write this file, so maybe another dead end here.
Also, I'm sure I'm not the first to try this, but I've also checked all known exploits using the "X-Ray" app at http://www.xray.io/. Normally, I'd be quite pleased to learn that I'm patched against all those exploits. Unfortunately, not this time.
And then, of course, there was my attempt to use mempodroid (before I discovered X-Ray and learned that it's not vulnerable). The kernel version "should" support it, but they must have applied Linus' patch to their kernel before this device hit the market. I've suspected ever since that this was the reason the Fireball release date kept getting pushed back, but we can't know for sure.
Sent from my ADR6410LVW using xda app-developers app, edited from a device where I have Admin rights
Click to expand...
Click to collapse
This might help a little bit, but I don't think you can touch anything in DxDrm, but almost all those files are world writable:
/data/DxDrm:
total 28
-rwxrwxrwx 1 0 0 16 Aug 24 05:11 DxDeviceKey
-rw-rw---- 1 0 0 403 Sep 7 16:27 DxDrmConfig_Server.txt
-rwxrwxrwx 1 0 0 1284 Sep 7 16:27 DxSecureDB
-rwxrwxrwx 1 0 0 8504 Sep 7 16:27 DxSecureDB_secondary
-rwxrwxrwx 1 0 0 80 Aug 24 05:11 NVS
drwxr-xr-x 20 0 0 0 Sep 7 16:27 fuse
srwxrwxrwx 1 0 0 0 Sep 7 16:27 socket_5000.tmp
Click to expand...
Click to collapse
Also, this folder was world-writable:
/data/data/com.google.android.apps.maps:
drwxrwx-wx 2 10161 10161 4096 Sep 6 22:49 app_da_speech
Click to expand...
Click to collapse
And another file that was world-writable but was a symlinked:
/data/system
lrwxrwxrwx 1 0 0 30 Sep 6 22:49 wpa_supplicant -> /data/misc/wifi/wpa_supplicant
Click to expand...
Click to collapse
Maybe that helps a little bit
-viperboy- said:
This might help a little bit, but I don't think you can touch anything in DxDrm, but almost all those files are world writable:
Also, this folder was world-writable:
And another file that was world-writable but was a symlinked:
Maybe that helps a little bit
Click to expand...
Click to collapse
How are you able to see that, or are you looking at a different device?
I tried every dir and file you listed. I can't move/delete any of those files to even try and see if it gets recreated on reboot. And of course I can't just symlink over-top of any without getting "File exists".
Also, when I do successfully create a symlink (as I mentioned before), and even after rebooting, I get this message from debugfs:
Code:
1|[email protected]:/data $ /data/local/tmp/debugfs -w /data/local/tmp/mmcblk0p33
/data/local/tmp/debugfs -w /data/local/tmp/mmcblk0p33
debugfs 1.42 (29-Nov-2011)
/data/local/tmp/mmcblk0p33: Permission denied while opening filesystem
I've found another folder (by greping for "/data" in all text files that exist in the /system image I have mounted in Ubuntu) where I can symlink, as you can see here:
Code:
1|[email protected]:/ $ ls -l /data/wpstiles
ls -l /data/wpstiles
lrwxrwxrwx shell shell 2012-09-08 22:05 mmcblk0p33 -> /dev/block/mmcblk0p33
lrwxrwxrwx shell shell 2012-09-08 22:09 p33 -> /dev/block/platform/msm_sdcc.1/by-num/p33
But, I'm still getting the same error from debugfs as above on all of those I've tried, even after trying reboots to see if permissions are getting assigned on boot. What we need is a file that has permissions changed on boot, which we've been unable to find thus far.
CaptainRewind said:
How are you able to see that, or are you looking at a different device?
I tried every dir and file you listed. I can't move/delete any of those files to even try and see if it gets recreated on reboot. And of course I can't just symlink over-top of any without getting "File exists".
Also, when I do successfully create a symlink (as I mentioned before), and even after rebooting, I get this message from debugfs:
Code:
1|[email protected]:/data $ /data/local/tmp/debugfs -w /data/local/tmp/mmcblk0p33
/data/local/tmp/debugfs -w /data/local/tmp/mmcblk0p33
debugfs 1.42 (29-Nov-2011)
/data/local/tmp/mmcblk0p33: Permission denied while opening filesystem
I've found another folder (by greping for "/data" in all text files that exist in the /system image I have mounted in Ubuntu) where I can symlink, as you can see here:
Code:
1|[email protected]:/ $ ls -l /data/wpstiles
ls -l /data/wpstiles
lrwxrwxrwx shell shell 2012-09-08 22:05 mmcblk0p33 -> /dev/block/mmcblk0p33
lrwxrwxrwx shell shell 2012-09-08 22:09 p33 -> /dev/block/platform/msm_sdcc.1/by-num/p33
But, I'm still getting the same error from debugfs as above on all of those I've tried, even after trying reboots to see if permissions are getting assigned on boot. What we need is a file that has permissions changed on boot, which we've been unable to find thus far.
Click to expand...
Click to collapse
I went through a huge list of files on an Inc 4G by doing an ls -lR /data. Also, the way you would wanna symlink is ln -s
Sent from my EVO using Tapatalk 2
-viperboy- said:
I went through a huge list of files on an Inc 4G by doing an ls -lR /data. Also, the way you would wanna symlink is ln -s
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
I did that ls -lR, too, a few weeks ago, but must have missed a few files. Or I may have tried them all and forgotten. None of them work anyways.
Right I was using busybox and doing an ln -s to create the symlinks. The ls -l above was just to display the symlink source for this audience.
So, it seems that the symlink trick is officially a bust.
Sent from my ADR6410LVW using xda app-developers app
I applaud everyone's efforts to get root for this device. Someone posted a possibility earlier in the Q&A subforum, so I thought I'd link it here since no one has commented yet. It potentially has merit.
http://forums.androidcentral.com/ne...ide-factory-image-restore-your-nexus-7-a.html
Maybe it could be adapted for us. At least some fastboot ideas. I don't know... I'm going crazy without root!
IceDragon59 said:
I don't know... I'm going crazy without root!
Click to expand...
Click to collapse
This.
I just upgraded from my original HTC Incredible (with cyanogenmod, though I had to fight with it sometimes, I loved it), to the Incredible 4G. I don't have a ton of developing experience, but would be willing to help.
They might just unlock us via HTCDev after the iphone5 goes on sale on September 25th.
IceDragon59 said:
I applaud everyone's efforts to get root for this device. Someone posted a possibility earlier in the Q&A subforum, so I thought I'd link it here since no one has commented yet. It potentially has merit.
http://forums.androidcentral.com/ne...ide-factory-image-restore-your-nexus-7-a.html
Maybe it could be adapted for us. At least some fastboot ideas. I don't know... I'm going crazy without root!
Click to expand...
Click to collapse
z4root has been patched for a while on HTC devices. The way that they restored the phone in AC is not something you can do with a locked (S-ON) HTC device.
htc quick root
has anyone read that article on htc quick root, or tried this on our phone, probably doesn't work for us
I've got a device and need either root or su for system app development, but want to do this in the least invasive way possbile. The twist... this is likely a pre-release device and came from HTC with S-OFF (HBOOT-1.01.0000).
With S-OFF (but no root) what are the options for getting root and/or SU installed?
pukebag said:
I've got a device and need either root or su for system app development, but want to do this in the least invasive way possbile. The twist... this is likely a pre-release device and came from HTC with S-OFF (HBOOT-1.01.0000).
With S-OFF (but no root) what are the options for getting root and/or SU installed?
Click to expand...
Click to collapse
Least invasive: Install superuser/su from adb, leaving stock recovery in place. LMGTFY: http://www.equisoforum.com/Thread-ADB-Shell-Pro-Root-method
Better route: Flash CWM or TWRP recovery to phone, then flash superuser/su package from recovery.
junkmail9 said:
Least invasive: Install superuser/su from adb, leaving stock recovery in place. LMGTFY: no_urls_from_noobs
Better route: Flash CWM or TWRP recovery to phone, then flash superuser/su package from recovery.
Click to expand...
Click to collapse
(please forgive if anything I have below is nonsense... I'm slowly building my understanding)
I don't believe the 1st method will work. I can't 'adb remount' because I don't have root on the device ('remount failed: Operation not permitted'). If remount worked I'd be good, because as you suggest I could push the su apk/permission/scripts to the device. I also tried remounting the /system partition as RW but no luck ('mount: Operation not permitted').
I'll try the 'traditional' CWM route. I just wasn't sure if having S-OFF opened up any other options for getting root, mounting /system as RW, or...
Thanks much.
pukebag said:
(please forgive if anything I have below is nonsense... I'm slowly building my understanding)
I don't believe the 1st method will work. I can't 'adb remount' because I don't have root on the device ('remount failed: Operation not permitted'). If remount worked I'd be good, because as you suggest I could push the su apk/permission/scripts to the device. I also tried remounting the /system partition as RW but no luck ('mount: Operation not permitted').
I'll try the 'traditional' CWM route. I just wasn't sure if having S-OFF opened up any other options for getting root, mounting /system as RW, or...
Thanks much.
Click to expand...
Click to collapse
I have always used the "Better Route". However, I was under the impression that s-off unlocked the partitions.
Out of curiosity, did you try the following command anyway: (adb push su /system/bin) ?
junkmail9 said:
I have always used the "Better Route". However, I was under the impression that s-off unlocked the partitions.
Out of curiosity, did you try the following command anyway: (adb push su /system/bin) ?
Click to expand...
Click to collapse
At least in this case /system is mounted RO:
- adb shell mount | grep system -> /dev/block/mmcblk0p33 /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0
- adb push foobar.txt /system/bin -> 'failed to copy foobar.txt to /sytem/bin/foobar.txt : Read-only file system
This isn't a regular consumer device so it's at least a little funky. For example, it doesn't get OTA updates and is stuck with an old RUU (htc sense 4.0... ruu 1.31.605.1 (? not sure where exactly to get RUU version). It also has the 'normal' CID (VZW__001).
It might get a little interesting digging up workable bootloader and supercid method, now out-of-date for basically everyone else.
pukebag said:
At least in this case /system is mounted RO:
- adb shell mount | grep system -> /dev/block/mmcblk0p33 /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0
- adb push foobar.txt /system/bin -> 'failed to copy foobar.txt to /sytem/bin/foobar.txt : Read-only file system
This isn't a regular consumer device so it's at least a little funky. For example, it doesn't get OTA updates and is stuck with an old RUU (htc sense 4.0... ruu 1.31.605.1 (? not sure where exactly to get RUU version). It also has the 'normal' CID (VZW__001).
It might get a little interesting digging up workable bootloader and supercid method, now out-of-date for basically everyone else.
Click to expand...
Click to collapse
If you're already S-OFF, you shouldn't need to do anything with supercid. Just put the phone into fastboot and flash a custom recovery - either CWM (link) or TWRP (link), depending on your preference. Follow the "manual installation" steps in the thread of your choice. I have been very happy with PhilZ's Touch CWM.
Also - first thing to do after installing the recovery is to make a nandroid backup of the (semi) pristine state of your phone.
Hi All,
I have purchased a leagoo lead 1 http://www.leagoo.cc/c51181.html (slick design and under 150$) but now I'm trying to get it rooted.
I've tries Kingo root, V Root, Shuame, Towel root, Framaroot and none of it is working.
The phone operates on 4.4.2 with an MTK 6582 processor..
When holding Vol up + power I get a fastboot option though.
Would extracting boot.img and rework it mean something? or has anyone usefull tips?
Thnks in advance.
Check this topic: http://forum.xda-developers.com/showthread.php?t=2783157
Could you throw in some review, particularly WiFi and GSM signal strength, GPS strength, battery? Thanks!
boyanpa said:
Check this topic: http://forum.xda-developers.com/showthread.php?t=2783157
Could you throw in some review, particularly WiFi and GSM signal strength, GPS strength, battery? Thanks!
Click to expand...
Click to collapse
First of all .. I managed to root it.
Needed: Kingosoft Sony bootloader unlocker, Kingosoft one click root, (www.kingoapp.com) Mobile uncle tools
Start sony bootloader unlocker and run it with your phone connected.
It will restart your phone to fastboot and then it remains idle.
Keep your phone plugged in, switch it off and boot manually into the fastboot (power + vol up)
From here the unlocker will proceed unlocking.
Step 1 done.
Now open kingosoft root connect the phone and let it do its thing.
At restart of the phone kingosoft will show on screen a message like "checking root status"
Launch mtk uncle and enter engineer mode.
Go to log and debugging tab ans select user2root
Select Root.
Now kingosoft will tell you that root is succesfull and restarts the phone.
That's that. Phone is rooted. For recovery see the posts 22 and 24 from Vampirefo who did the real hard work in creating 2 flavours of recovery. [emoji106][emoji106]
Non linux users can also flash the img through MTK uncle from sdcard if that doesn't work. See post 40 for flashing recovery via SP tools
The phone runs smooth on what seems to be Yun Os aka Aliyun. Gapps and all android functionalities are working well. At first it seemed that the WIFI reception was poor but with an OTA update seems this has been fixed.
Only trouble I have is getting a GPS fix. It does see 11-13 sattelites but I'm unable to get a proper fix on it. Also the EPO function is not acessible from 4.4.2 . so now with root I'm trying to inject the GPS.CONF file into system/etc and see if it gets a fix or not.
For the time I've been playing around with it... it seems a pretty decent phone with a good response for a reasonable price.
de vetnek said:
First of all ..Looks like I (accidentaly) managed to root it.
Needed: Kingosoft Sony bootloader unlocker, Kingo soft one click root, Mobile uncle tools
I Downloaded from kingosoft the sony bootloader unlocker.
It puts the phone in fastboot mode and then it hangs. I unplugged my phone, switch it off (keep the unlocker running) and manually booted into fastboot (vol up+power) the bootloader unlocker then proceeded untill finished.
Next I installed this root tool and started it while the phone was still in the fastboot mode. after a couple of restarts it says checking for Root, then I decided to start MTK uncle tools and scroll to "log and debugging" and select User2Root. then clicked Root and all of a sudden the phone was sucessfully rooted.. Smiling Smiling I don't know what exactly sparked the root access but It's rooted and works!
If anyone can reproduce this in a correct order. please feel free to share.
The phone runs smooth on what seems to be Yun Os aka Aliyun. Gapps and all android functionalities are working well. At first it seemed that the WIFI reception was poor but with an OTA update seems this has been fixed.
Only trouble I have is getting a GPS fix. It does see 11-13 sattelites but I'm unable to get a proper fix on it. Also the EPO function is not acessible from 4.4.2 . so now with root I'm trying to inject the GPS.CONF file into system/etc and see if it gets a fix or not.
For the time I've been playing around with it... it seems a pretty decent phone with a good response for a reasonable price.
Click to expand...
Click to collapse
You state you next installed this root tool, what is this root tool? a link to tool would be nice.
vampirefo said:
You state you next installed this root tool, what is this root tool? a link to tool would be nice.
Click to expand...
Click to collapse
http://www.kingoapp.com/ :angel:
Also found the solution for the GPS.
In Engineer mode, Switch AGPS from User plane to Control plane.
de vetnek said:
http://www.kingoapp.com/ :angel:
Also found the solution for the GPS.
In Engineer mode, Switch AGPS from User plane to Control plane.
Click to expand...
Click to collapse
Thanks, GPS was working great on my phone out of box.
vampirefo said:
Thanks, GPS was working great on my phone out of box.
Click to expand...
Click to collapse
Mine wasn't but probably due to a factory reset from recovery? OR it wasn't fit yet to see the dutch sky
Managed to root the thing?
Yes mine is rooted also, Similar to the way you rooted yours.
I used Linux and wine to run the bootloader tool from there, I had to use another tool to get temp root, then I pushed su and set permissions.
The bootloader tool you used works via wine but the root tool doesn't.
Sent from my Leagoo Lead1 via taptak.
So we can carefully state that the (accidental) rooting method works.
Btw. I figured out that /system is ro and not rw
Also with adbd insecure it remains ro. Means it has to be scripted to rw at every boot or.... Can try to run framaroot exploit.
System is supposed to be ro this is normal, to get rw add busybox and then remount rw.
Also you can edit the boot.img and make a insecure boot.img and flash, I have done this myself, this enables adb remount, you can add a script to /system/xbin, to force rw or ro.
I wouldn't want rw all this time, as this can cause instability use ro until you need rw, es filemanger with root also allows you to mount system rw as needed.
Added some pics of phone showing it's rooted.
http://postimg.org/gallery/6ol04a9i/
Sent from my Leagoo Lead1 via taptak.
Check
Noticed that the 1GB Rom quickly runs full if you are not keen on the installation location of apps.
Facebook though can't be moved to SD card.
libvc1dec.sa.ca7.so has text relocations . This is wasting memory and is a security risk. please fix
I have been able to hack through recovery, I now have root in recovery mode, so can do backups and restore, dual boot and should be able to increase the size of data partition.
Code:
[email protected]:~/Desktop$ adb devices
List of devices attached
0123456789ABCDEF recovery
[email protected]:~/Desktop$ adb shell
/system/bin/sh: /system/etc/mkshrc[9]: getprop: not found
/system/bin/sh: /system/etc/mkshrc[10]: id: not found
@android:/ #
vampirefo said:
I have been able to hack through recovery, I now have root in recovery mode, so can do backups and restore, dual boot and should be able to increase the size of data partition.
Code:
[email protected]:~/Desktop$ adb devices
List of devices attached
0123456789ABCDEF recovery
[email protected]:~/Desktop$ adb shell
/system/bin/sh: /system/etc/mkshrc[9]: getprop: not found
/system/bin/sh: /system/etc/mkshrc[10]: id: not found
@android:/ #
Click to expand...
Click to collapse
Below shows data is now 4GB, as I am running data from sdcard, I can of course make data any size I want, only limited by size of sdcard, I think this phone supports 64GB, so data could be 64GB.
Code:
[email protected]:/ # busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 481.6M 128.0K 481.4M 0% /dev
none 481.6M 12.0K 481.5M 0% /sys/fs/cgroup
tmpfs 481.6M 0 481.6M 0% /mnt/secure
tmpfs 481.6M 0 481.6M 0% /mnt/asec
tmpfs 481.6M 0 481.6M 0% /mnt/obb
/[email protected] 885.8M 819.2M 66.6M 92% /system
/dev/block/mmcblk1p3 4.0G 999.8M 2.8G 26% /data
/[email protected] 123.0M 4.1M 119.0M 3% /cache
/[email protected]_f 8.8M 4.1M 4.8M 46% /protect_f
/[email protected]_s 8.8M 4.1M 4.8M 46% /protect_s
/dev/block/loop0 1.5M 1.5M 0 100% /mnt/cd-rom
I use Vocano support MTK chipset root but not done, VOcano have support new version, you can test, good luck
tunglethanh90 said:
I use Vocano support MTK chipset root but not done, VOcano have support new version, you can test, good luck
Click to expand...
Click to collapse
No ideal what you are saying, Have you rooted your leagoo lead1? if so by what? what is VOcano? Post more details, you say you root but not done, what does that mean?
Hacking through the recovery is a bit out of my league.
Is there a tut how to do this on a windows machine?
Another way I could think of is to create an ext2 partition (with an external program) on the SD card and use link2SD to utilize that as internal memory.
But I'm open for smarter ways of doing so.
de vetnek said:
Hacking through the recovery is a bit out of my league.
Is there a tut how to do this on a windows machine?
Another way I could think of is to create an ext2 partition (with an external program) on the SD card and use link2SD to utilize that as internal memory.
But I'm open for smarter ways of doing so.
Click to expand...
Click to collapse
There isn't a tut for Linux, so I doubt there is one for Windows, hacking comes from one's mind, lol. If link2SD works for you that would be just fine.
My method requires pulling stock recovery from phone unpacking recovery, adding adb support adding busybox support repacking stock recovery then flash to phone.
From the repacked recovery, full access to phone is possible, dual booting, running from phone from sdcard, creating and restoring backups.
vampirefo said:
There isn't a tut for Linux, so I doubt there is one for Windows, hacking comes from one's mind, lol. If link2SD works for you that would be just fine.
My method requires pulling stock recovery from phone unpacking recovery, adding adb support adding busybox support repacking stock recovery then flash to phone.
From the repacked recovery, full access to phone is possible, dual booting, running from phone from sdcard, creating and restoring backups.
Click to expand...
Click to collapse
Things just got worse hehe.. Did the whole link2sd thing and linked a couple of apps and voila. playstore, facebook, whatsapp gone.. and nowhere to be found back........... doubting whether a factory reset would fix the thing? So in short.... nope.. link2SD does not work.
wouldn't posting the repacked recovery and flashing it to another phone be possible?
Yes the recovery can be flashed on another rooted tablet, but there is more to getting data on sdcard that just flashing a recovery.
I just now modified cwm recovery to work on leagoo lead1, cwm recovery is bigger than my packed stock recovery, but I am able to squeeze in it, lol.
In Utopia..... This would be a good solution for the Leagoo too
http://forum.xda-developers.com/showthread.php?t=2020677
Don't know exactly how they fixed it.. but..... there you also went from 1 to 2.5 GB internal...