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.
Related
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
HI, I have an S3 9300 which was damaged by water. I finally managed to revive it by using Isopropyl Alcohol and cleaning it. The piece worked perfectly fine except for the display screen which kept blurring out. Unfortunately, the S3 display gave up and i cannot see anything or even use the touch. I tried opening the display to clean out any moisture, but again unfortunately even after carefully removing the display it wont work. Now the S3 is working with no display or Touch. repairing it here in India is costing me more than a second hand unit available. so i decided to not repair it. But since the motherboard and the rest are working fine, i thought i could use it for something else like a security IP camera.
Now i have a problem, the USB debugging was not enabled before the display konked off. the S3 is not rooted either. Can anyone help me how can i get the USB debugging enabled somehow so i can operate the phone from the desktop PC using MyPhoneExplorer. this way i can install apps, use the phone for SMS, calls and use the camera too.
I just need the USB debugging on so i can do the needful.
Anybody has any ideas? how can you help me here?
i have tried putting it in download mode and flashing a rooted stock firmware. this will at least have USB debugging on by default (i think).
Please help. what can i do?
If anyone has a working display with a busted motherboard, can i buy it? how much? i live in mumbai - India
Please reply in the thread or PM me
Thanks guys.
try connecting s3 to tv via hdmi and goto settings>developer option>enabled usb debugging ?
MoonBlade said:
try connecting s3 to tv via hdmi and goto settings>developer option>enabled usb debugging ?
Click to expand...
Click to collapse
would have tried it. but the digitizer does not work either. cannot use the display or touch. secondly i dont have the MHL HDMI connector too.
francisdsa said:
would have tried it. but the digitizer does not work either. cannot use the display or touch. secondly i dont have the MHL HDMI connector too.
Click to expand...
Click to collapse
looks like you are in a bit of a trouble.. i would have suggested flashing any other rom with usb debugging already enabled like cm10.1 . but with screen not working accessing recovery to flash rom will be tricky.
MoonBlade said:
looks like you are in a bit of a trouble.. i would have suggested flashing any other rom with usb debugging already enabled like cm10.1 . but with screen not working accessing recovery to flash rom will be tricky.
Click to expand...
Click to collapse
Ha ha ha. Actually the issue is that USB debugging is not enabled. that is the reason i am jumping around trying stuff. in fact i am on ODIN FU##ng around and now the device just wont go off the download mode. still fooling around.
i think i may brick the phone... anyways, the piece was a lab rat for me...
can i salvage anything from it? can i use the camera elsewhere? anything???
do let me know
francisdsa said:
Ha ha ha. Actually the issue is that USB debugging is not enabled. that is the reason i am jumping around trying stuff. in fact i am on ODIN FU##ng around and now the device just wont go off the download mode. still fooling around.
i think i may brick the phone... anyways, the piece was a lab rat for me...
can i salvage anything from it? can i use the camera elsewhere? anything???
do let me know
Click to expand...
Click to collapse
i heard somewhere that you can use usb keyboard with your s3. but then i am not sure whether u need usb debugging to be ON for this to work. if its not needed then i think you can use the keyboard to navigate to settings to enable usb debugging.
i have never tried this though try searching a bit in google. might find a solution.
http://forum.xda-developers.com/showthread.php?t=1749902
You cannot use input device and video output simultaneously. This means you cannot change any settings. Only bet is to try to find an adaptor that allows MHL and usb simultaneously.
Sent from my GT-I9300 using Tapatalk 4
rootSU said:
You cannot use input device and video output simultaneously. This means you cannot change any settings. Only bet is to try to find an adaptor that allows MHL and usb simultaneously.
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
You are right.
Well, please let me know if there is any other method to control the phone from the PC and enable the USB debugging settings.......I would be delighted and thankful
any ADB command mode to start USB vai command prompt
francisdsa said:
You are right.
Well, please let me know if there is any other method to control the phone from the PC and enable the USB debugging settings.......I would be delighted and thankful
Click to expand...
Click to collapse
There's no other method.
Heres a thread about MHL and OTG : http://forum.xda-developers.com/showthread.php?t=1741583
rootSU said:
There's no other method.
Heres a thread about MHL and OTG : http://forum.xda-developers.com/showthread.php?t=1741583
Click to expand...
Click to collapse
Need to know something.
What if i flash a pre-rooted ROM from ODIN? USB debugging should be enabled on it by default.
but will i get a rooted custom ROM in odin flashable format?
will i be able to flash the ROM if the device is not rooted and USB debugging disabled?
have never tried this method and hence asking a nooby question
Please help
francisdsa said:
Need to know something.
What if i flash a pre-rooted ROM from ODIN? USB debugging should be enabled on it by default.
but will i get a rooted custom ROM in odin flashable format?
will i be able to flash the ROM if the device is not rooted and USB debugging disabled?
have never tried this method and hence asking a nooby question
Please help
Click to expand...
Click to collapse
i was just googling around . i found something interesting. i think you can enable usb debugging via adb in CWM if u have proper knowledge of adb commnads. just do a search for enabling usb debugging by changing value of a property in the settings.db file located in data/data/com.android.providers.settings/databases/settings.db
rootSU said:
There's no other method.
Heres a thread about MHL and OTG : http://forum.xda-developers.com/showthread.php?t=1741583
Click to expand...
Click to collapse
MoonBlade said:
i was just googling around . i found something interesting. i think you can enable usb debugging via adb in CWM if u have proper knowledge of adb commnads. just do a search for enabling usb debugging by changing value of a property in the settings.db file located in data/data/com.android.providers.settings/databases/settings.db
Click to expand...
Click to collapse
Thanks dude, but the issue is i dont have root or CWM installed. With no display this is will be even painful as i will blindly be shooting around and possibly brick the device.
i have spoken to a few friends if they can arrange an S3 and maybe with the USB keyboard over OTG i can enable the developer settings. Secondly have also spoken around with a few service centers and mobile repair shops if they can temporarily swap a working display from a repair piece and enable the mode for me. no one has a piece at present. fingers crossed...
by the way, you are from india.. Where are you from? which city? I am from Mumbai
francisdsa said:
Thanks dude, but the issue is i dont have root or CWM installed. With no display this is will be even painful as i will blindly be shooting around and possibly brick the device.
i have spoken to a few friends if they can arrange an S3 and maybe with the USB keyboard over OTG i can enable the developer settings. Secondly have also spoken around with a few service centers and mobile repair shops if they can temporarily swap a working display from a repair piece and enable the mode for me. no one has a piece at present. fingers crossed...
by the way, you are from india.. Where are you from? which city? I am from Mumbai
Click to expand...
Click to collapse
Flashing CWM is easy. You just need to be in download mode which is easy enough to bet into blind.
ADB is done from a computer. If the settings.db has the answer, all you do is adb pull it, make the change and adb push it. Seems simple enough to me.
rootSU said:
Flashing CWM is easy. You just need to be in download mode which is easy enough to bet into blind.
ADB is done from a computer. If the settings.db has the answer, all you do is adb pull it, make the change and adb push it. Seems simple enough to me.
Click to expand...
Click to collapse
could try that. but i read elsewhere that the settings change will not affect ti as the boot.img file also needs to be stripped and modified to work with it.
francisdsa said:
could try that. but i read elsewhere that the settings change will not affect ti as the boot.img file also needs to be stripped and modified to work with it.
Click to expand...
Click to collapse
Can't you just flash a supported custom kernel then? That's all boot image is. A kernel available in .tar? Siyah 1.9.1 tar flashed from Odin.
Then boot into recovery:
Code:
adb shell
mount system
sqlite3 /data/data/com.android.providers.settings/databases/settings.db
SELECT * FROM global;
update global set value=1 where name='adb_enabled';
SELECT * FROM global;
CTRL + C
adb shell
mount system
echo "persist.service.adb.enable=1" >> /system/build.prop
This should work. Yes, adb_enabled is the value set as 0 or 1 when turning usb debugging on or off, I tested it all
Note SELECT * FROM global; shows all the values in the global table which is where adb_enabled is. It should say 0. Then you run the update command and then SELECT again to witness the change. I noticed that this did not persist after booting into android, which is why we need to put persist in the build prop. Hope this helps.
rootSU said:
Can't you just flash a supported custom kernel then? That's all boot image is. A kernel available in .tar? Siyah 1.9.1 tar flashed from Odin.
Then boot into recovery:
Code:
adb shell
mount system
sqlite3 /data/data/com.android.providers.settings/databases/settings.db
SELECT * FROM global;
update global set value=1 where name='adb_enabled';
SELECT * FROM global;
CTRL + C
adb shell
mount system
echo "persist.service.adb.enable=1" >> /system/build.prop
This should work. Yes, adb_enabled is the value set as 0 or 1 when turning usb debugging on or off, I tested it all
Note SELECT * FROM global; shows all the values in the global table which is where adb_enabled is. It should say 0. Then you run the update command and then SELECT again to witness the change. I noticed that this did not persist after booting into android, which is why we need to put persist in the build prop. Hope this helps.
Click to expand...
Click to collapse
Huh. That's seeming a bit tough fer me especially after I left linux almost 10 years ago. But am eager to try it out. Will try so and check. yhanks fot the great info. Will revert
francisdsa said:
Huh. That's seeming a bit tough fer me especially after I left linux almost 10 years ago. But am eager to try it out. Will try so and check. yhanks fot the great info. Will revert
Click to expand...
Click to collapse
You can literally copy and paste that (line by line) into windows cmd prompt, once you have adb.exe dropped in c:\windows\system32
But yeah let me know please. I did test successfully so works for me
rootSU said:
You can literally copy and paste that (line by line) into windows cmd prompt, once you have adb.exe dropped in c:\windows\system32
But yeah let me know please. I did test successfully so works for me
Click to expand...
Click to collapse
Yea yea. Surely. I shall try tomorrow itself.
francisdsa said:
Yea yea. Surely. I shall try tomorrow itself.
Click to expand...
Click to collapse
Did not work. Flashes the Siyah kernel via odin, the phone went into a boot loop.
went into recovery mode
started ADB
here is the output
====================
C:\>adb devices
List of devices attached
4df7dfa9572f3051 recovery
C:\>adb shell
[email protected]:/ $ mount system
mount system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]:/ $
=============================
here are the mount paths
================
C:\>adb shell
[email protected]:/ $ mount
mount
rootfs / rootfs rw 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
/dev/block/mmcblk0p9 /system ext4 rw,nodev,noatime,nodiratime,barrier=1,data=ord
ered 0 0
[email protected]:/ $
=========================
Am stuck please help
Hi guys,
I don't know what piece of info is relevant or not, so I will outline as much as I can.
I was running the latest stable Slimbean with stock kernel, a couple of weeks ago my external sdcard stopped being recognized and would not mount. In Clockworkmod it would show an error mounting what I later learned were 3 different partitions.
Yesterday I installed freegee to try and restore my original partitions, but it would give me an error that my device was not supported. So I uninstalled freegee. The next time I rebooted my phone, it would get stuck on a black screen after the LG logo. I was able to get into recovery and download mode, so I tried the original teenybin with lgpnst and I could not get into recovery, only the LG logo. I then tried the alternate teenybin that boots up with the Google logo and I was able to get into TWRP.
I then sideloaded Houston's aosp KitKat and was able to successfully boot up the phone. I now have no system sounds, no music or media sounds, through the speaker or the headphone jack. Phone audio works through earpiece, speaker and headphones.
Tried wiping and reflashing. I don't know what else to do.
Any ideas would be appreciated.
Thanks.
I also noticed that sensors were not working.
I flashed the W84C27MO84.zip hybrid modem.
This solved the problem with sounds and audio not working and fixed the sensors.
Post your partition table here!!!
Enter in CWM Recovery, connect your phone to computer, open terminal in administrator mode. open adb shell and run this command.
parted /dev/block/mmcblk0
press P and put your result partition screenshot here.
XDFernando said:
Post your partition table here!!!
Enter in CWM Recovery, connect your phone to computer, open terminal in administrator mode. open adb shell and run this command.
parted /dev/block/mmcblk0
press P and put your result partition screenshot here.
Click to expand...
Click to collapse
I wasn't able to do it exactly as you described, but I think I got what you asked for. Hope it helps.
Thanks,
Im so sorry my steps was with Special CWM.
Try this 3 steps on ADB shell.
Code:
dd if=/dev/block/mmcblk0p17 of=/sdcard/mmcblk0p17.bak
mke2fs -T ext4 /dev/block/mmcblk0p17
reboot
good luck!!
XDFernando said:
Im so sorry my steps was with Special CWM.
Try this 3 steps on ADB shell.
Code:
dd if=/dev/block/mmcblk0p17 of=/sdcard/mmcblk0p17.bak
mke2fs -T ext4 /dev/block/mmcblk0p17
reboot
good luck!!
Click to expand...
Click to collapse
Thank you for the response.
What exactly will this do?
I ran what you suggested.
I received "Not enough space to build proposed file system while setting up superblock"
How much free space is required? I have almost 2gigs free
you need to do separate steps. One line is one command. Enter every one line.
And Dont copy paste i see another extra simbols
XDFernando said:
you need to do separate steps. One line is one command. Enter every one line.
And Dont copy paste i see another extra simbols
Click to expand...
Click to collapse
Hello,
Thank you for your responses.
I tried doing it again, one line at a time, but still got the same message after the second line.
Try add -F to the second line like this:
mke2fs -F -T ext4 /dev/block/mmcblk0p17
XDFernando said:
Try add -F to the second line like this:
mke2fs -F -T ext4 /dev/block/mmcblk0p17
Click to expand...
Click to collapse
Hi Fernando,
I tried again with the -F added, but I received the same message about "not enough space..."
Hello everybody, I'm Dejan and I could use some help please.
I have Samsung Galaxy SII GT 9100 with broken screen and I have some very important stuff in it. Screen is totally broken and I cant see a thing. Long story short i used Fuzzy Meep's app but I'm stuck deep in the mud so thats off. I booted phone in my custom recovery , installed ADB on PC and managed to connect to the device. But I can't make my way thru the sdcard. Here is what I did:
G:\ADB>adb.exe shell
~ # cd etc
cd etc
/etc # ls
ls
recovery.fstab
/etc # cat recovery.fstab
cat recovery.fstab
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options
> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
# data partition must be located at the bottom for supporting device encryption
/dev/block/mmcblk0p9 /system ext4 ro,noatime
wait
/dev/block/mmcblk0p7 /cache ext4 noatime,nosuid,nodev,j
ournal_async_commit,errors=panic wait,check_spo
/dev/block/mmcblk0p1 /efs ext4 noatime,nosuid,nodev,j
ournal_async_commit,errors=panic wait,check_spo
/dev/block/mmcblk0p10 /data ext4 noatime,nosuid,nodev,d
iscard,noauto_da_alloc,journal_async_commit,errors=panic wait,check_spo,encryptable=/efs/metadata
/dev/block/mmcblk0p12 /preload ext4 noatime,nosuid,nodev,j
ournal_async_commit wait
# vold-managed volumes ("block device" is actually a sysfs devpath)
/devices/platform/dw_mmc/mmc_host/mmc0/mmc0 auto auto defaults voldmanaged=sdcard0:
11,nonremovable,noemulatedsd
/devices/platform/s3c-sdhci.2/mmc_host/mmc1 auto auto defaults voldmanaged=sdcard1:
auto
/devices/platform/s3c_otghcd/usb auto auto defaults voldmanaged=usbdisk0
:auto
# recovery
/dev/block/mmcblk0p5 /boot emmc defaults recovery
only
/dev/block/mmcblk0p6 /recovery emmc defaults recovery
only
How do i mount internal memory and pull out my data? Any help is appreciated. Thanks
It's a CM LInaro Kitkat 4.4.2 with custom kernel. With older versions of Android I was able to do what I was attempting to do but I've read somewhere about certain change when mounting storage on 4.4.2.
Thanks in advance.
Noone? Reallu? At least some info about device reading out data directly from the storage chip?
denkodenko said:
Noone? Reallu? At least some info about device reading out data directly from the storage chip?
Click to expand...
Click to collapse
That isn't even remotely possible for an end user. The only people who might be able to do that is a company which specialises in recovery of data from dead HDDs'. If it is possible, expect it to be very very expensive. I've never seen a single person post here in 2.5 yrs saying they've had this done successfully. Even if this is was possible, fixing your screen would be cheaper.
Very few people here have attempted to do what you're doing with ADB (me included; frankly, if the data was that important to me, I'd pay $120 for a new screen to save myself hassles, but I wouldn't be in that situation to begin with because I back stuff up). Unfortunately, you're going to be in for a rather long wait if you don't manage to work this out on your own, many people who may have been able to help you don't post here anymore, they've moved onto other phones given it's been 3 yrs since this phone was released.
MistahBungle said:
That isn't even remotely possible for an end user. The only people who might be able to do that is a company which specialises in recovery of data from dead HDDs'. If it is possible, expect it to be very very expensive. I've never seen a single person post here in 2.5 yrs saying they've had this done successfully. Even if this is was possible, fixing your screen would be cheaper.
Very few people here have attempted to do what you're doing with ADB (me included; frankly, if the data was that important to me, I'd pay $120 for a new screen to save myself hassles, but I wouldn't be in that situation to begin with because I back stuff up). Unfortunately, you're going to be in for a rather long wait if you don't manage to work this out on your own, many people who may have been able to help you don't post here anymore, they've moved onto other phones given it's been 3 yrs since this phone was released.
Click to expand...
Click to collapse
Well at least I gave it a shot but yeah... you are probably right I shouldn't have bothered posting and I was pretty sure someone somewhere might have asked the exact same question unfortunately I couldn't find it. I know how annoying these questions can be and I'm very sorry if I made someone angry. Long story short - I managed to get my pictures and videos back, as well as contacts. I do back those stuff up. however I had some .bin files for work that I lost but I've been living with that. It just might take some time browsing on the Internet finding them again but I'd rather do that than trying to do anything with the phone. I bought it $100 last year, the screen alone is that much, there's no point in fixing it. And at last but not least, thanksfor the reply.
Nah, they're not annoying It's just a very unusual situation, and as I said, if you want help with that sort of stuff with this phone on here, because so many people have moved on, you need to be really patient, that's all.
Same story
Shortly broken display no touch input. I had custom KitKat rom.
I had almost given up trying to mount the internal sd card with ADB, following numerios forum post instructions
here is my solution using windows pc and ADB
I rebooted in recovery (I think it was 6,0xx)
Using command prompt (you also need adb.exe) :
adb remount
adb root
adb usb
Those 3 command somehow mounted the internal storage and I was able to use the "adb pull" comand to copy the whole internal sd card to my hard drive
After that I went with "adb shell" to check how the sd card was mounted and here is what I found:
"
/dev/block/vold/259:3 on /storage/sdcard0 type vfat (rw,dirsync,nosuid,nodev,noe
xec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=c
p437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/mmcblk0p11 on /emmc type vfat (rw,dirsync,relatime,uid=1023,gid=1023,
fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortn
ame=mixed,utf8,errors=remount-ro)
"
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...