Hi to all!
So this is my case, right now IM really desperate.
My phone is a SM-G900H I installed this ROM: https://forum.xda-developers.com/ga...-exynos/rom-resurrection-remix-5-7-4-t3526192 (that BTW is a great proyect)
This works the first time until I reboot the phone, then I get stuck in a bootloop.
So from Sammobile I downloaded 3 different firmware and I flashed to my phone, this is what happens in all cases:
When Odin set on green and the phone reboots after the Samsung logo I see this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But the progress bar always stops on "40%" and then change to this:
So what is that make me think there is something in the phone that is stopping the process..
This is what I tried to do:
- I flashed 3 different firmware including the Bl,AP,CP,PIT variation.
- I flashed TWRP, CWM and I used the recovery stock
- I try to recover my phone with OTA.
- I tried to change the kernel.
- I tried to recover a friend stock backup with twrp.
- Finally I used nand erase all
- Tried to flash STOCK ROM DEODEX of @yash92duster
- Tried the two PIT.
Data that maybe is useful:
- When I go to TWRP and I mount EFS then I go to filemanager and I click to the EFS folder, the phone reboots.
- I can't use ADB SHELL (with TWRP), if I type adb devices I don't see it, but if I use the stock recovery and I choose adb sideload I see the id and I can do sideload very well.
I have access to:
Download Mode.
ADB (Only if I flash philz recovery).
Recovery.
Folders an disk data:
drwxr-xr-x root root 2017-01-10 16:12 boot
drwxr-xr-x root root 2017-01-10 11:29 cache
drwxr-xr-x root root 2017-01-10 10:39 data
drwxr-xr-x root root 2017-01-10 16:12 datadata
-rw-r--r— root root 2982 1970-01-01 00:00 default.prop
drwxr-xr-x root root 2017-01-10 16:12 dev
drwxr-xr-x root root 2017-01-10 16:12 emmc
drwxr-xr-x root root 2017-01-10 16:12 etc
drwxr-xr-x root root 2017-01-10 16:12 external_sd
-rw-r--r— root root 10976 1970-01-01 00:00 file_contexts
-rw-r---— root root 1326 1970-01-01 00:00 fstab.universal5422
-rwxr-x--- root root 187840 1970-01-01 00:00 init
-rwxr-x--- root root 2778 1970-01-01 00:00 init.rc
drwxr-xr-x root root 2017-01-10 16:12 internal_sd
-rw-r--r— root root 2048 1970-01-01 00:00 lpm.rc
drwxrwxr-x root system 2017-01-10 16:12 mnt
drwxr-xr-x root root 2017-01-10 11:29 preload
dr-xr-xr-x root root 1970-01-01 00:00 proc
-rw-r--r— root root 2161 1970-01-01 00:00 property_contexts
drwxr-xr-x root root 2017-01-10 16:12 recovery
drwxr-xr-x root root 1970-01-01 00:00 res
drwx------ root root 2014-03-31 05:24 root
drwxr-x--- root root 1970-01-01 00:00 sbin
drwxr-xr-x root root 2017-01-10 16:12 sd-ext
lrwxrwxrwx root root 2017-01-10 16:12 sdcard -> /data/media
-rw-r--r— root root 660 1970-01-01 00:00 seapp_contexts
-rw-r--r— root root 93316 1970-01-01 00:00 sepolicy
d---r-x--- root sdcard_r 2017-01-10 16:12 storage
dr-xr-xr-x root root 2017-01-10 16:12 sys
drwxr-xr-x root root 2017-01-10 11:32 system
drwxrwxr-x root shell 2017-01-10 16:12 tmp
-rw-r--r— root root 7275 1970-01-01 00:00 ueventd.rc
-rw-r--r— root root 6626 1970-01-01 00:00 ueventd.universal5422.rc
Click to expand...
Click to collapse
---
Filesystem Size Used Free Blksize
/dev 933.0M 128.0K 932.9M 4.0K
/tmp 933.0M 12.0K 933.0M 4.0K
/storage 933.0M 0.0K 933.0M 4.0K
/mnt/secure 933.0M 0.0K 933.0M 4.0K
/mnt/fuse 933.0M 0.0K 933.0M 4.0K
/cache 192.8M 472.0K 192.4M 4.0K
/data 11.6G 2.8M 11.6G 4.0K
/system 2.4G 2.2G 191.6M 4.0K
/preload 15.7M 40.0K 15.6M 4.0K
Click to expand...
Click to collapse
---
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
tmpfs /tmp tmpfs rw,seclabel,relatime 0 0
tmpfs /storage tmpfs rw,seclabel,relatime,mode=050,gid=1028 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 0 0
tmpfs /mnt/fuse tmpfs rw,seclabel,relatime,mode=775,gid=1000 0 0
/dev/block/mmcblk0p19 /cache ext4 rw,seclabel,relatime,discard,journal_checksum,
journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/mmcblk0p21 /data ext4 rw,seclabel,relatime,discard,journal_checksum,j
ournal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/mmcblk0p18 /system ext4 rw,seclabel,relatime,data=ordered 0 0
/dev/block/mmcblk0p20 /preload ext4 rw,seclabel,relatime,discard,journal_checksu
m,journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
Click to expand...
Click to collapse
What I think:
There is something that in the "updating" process make stop the progress so android finish erasing o reverting the process.
Thanks in advance!
the image you provided only shows up with a stock recovery. download TWRP 3.0.2 and flash it in Odin. Or, better yet, get the stock tar.md5 file, flash it in Odin, let it boot, boot to download mode, flash TWRP, go to advanced options, file manager and erase the android folders from internal and external storage, root it via TWRP, wipe cache, dalvik cache and system 3 times (yes, 3 times) then flash whatever compatible ROM you wish. I run resurrection remix myself and its a bomb diggity ROM!!
youdoofus said:
the image you provided only shows up with a stock recovery. download TWRP 3.0.2 and flash it in Odin. Or, better yet, get the stock tar.md5 file, flash it in Odin, let it boot, boot to download mode, flash TWRP, go to advanced options, file manager and erase the android folders from internal and external storage, root it via TWRP, wipe cache, dalvik cache and system 3 times (yes, 3 times) then flash whatever compatible ROM you wish. I run resurrection remix myself and its a bomb diggity ROM!!
Click to expand...
Click to collapse
I will try this, is safe remove all folders?
Thanks
maardobal said:
I will try this, is safe remove all folders?
Thanks
Click to expand...
Click to collapse
all of the folders called "android". Just those folders.
youdoofus said:
all of the folders called "android". Just those folders.
Click to expand...
Click to collapse
I cant find any "android" folder on my device. Any suggestion?
Code:
drwxr-xr-x root root 2017-01-11 01:06 boot
drwxr-xr-x root root 2017-01-10 19:43 cache
drwxr-xr-x root root 2017-01-10 19:43 data
drwxr-xr-x root root 2017-01-11 01:06 datadata
-rw-r--r-- root root 2982 1970-01-01 00:00 default.prop
drwxr-xr-x root root 2017-01-11 01:06 dev
drwxr-xr-x root root 2017-01-11 01:06 emmc
drwxr-xr-x root root 2017-01-11 01:06 etc
drwxr-xr-x root root 2017-01-11 01:06 external_sd
-rw-r--r-- root root 10976 1970-01-01 00:00 file_contexts
-rw-r----- root root 1326 1970-01-01 00:00 fstab.universal5422
-rwxr-x--- root root 187840 1970-01-01 00:00 init
-rwxr-x--- root root 2778 1970-01-01 00:00 init.rc
drwxr-xr-x root root 2017-01-11 01:06 internal_sd
-rw-r--r-- root root 2048 1970-01-01 00:00 lpm.rc
drwxrwxr-x root system 2017-01-11 01:06 mnt
drwxr-xr-x root root 2016-03-14 17:26 preload
dr-xr-xr-x root root 1970-01-01 00:00 proc
-rw-r--r-- root root 2161 1970-01-01 00:00 property_contexts
drwxr-xr-x root root 2017-01-11 01:06 recovery
drwxr-xr-x root root 1970-01-01 00:00 res
drwx------ root root 2014-03-31 05:24 root
drwxr-x--- root root 1970-01-01 00:00 sbin
drwxr-xr-x root root 2017-01-11 01:06 sd-ext
lrwxrwxrwx root root 2017-01-11 01:06 sdcard -> /data/media
-rw-r--r-- root root 660 1970-01-01 00:00 seapp_contexts
-rw-r--r-- root root 93316 1970-01-01 00:00 sepolicy
d---r-x--- root sdcard_r 2017-01-11 01:06 storage
dr-xr-xr-x root root 2017-01-11 01:06 sys
drwxr-xr-x root root 2017-01-10 19:43 system
drwxrwxr-x root shell 2017-01-11 01:06 tmp
-rw-r--r-- root root 7275 1970-01-01 00:00 ueventd.rc
-rw-r--r-- root root 6626 1970-01-01 00:00 ueventd.universal5422.rc
maardobal said:
I cant find any "android" folder on my device. Any suggestion?
Code:
drwxr-xr-x root root 2017-01-11 01:06 boot
drwxr-xr-x root root 2017-01-10 19:43 cache
drwxr-xr-x root root 2017-01-10 19:43 data
drwxr-xr-x root root 2017-01-11 01:06 datadata
-rw-r--r-- root root 2982 1970-01-01 00:00 default.prop
drwxr-xr-x root root 2017-01-11 01:06 dev
drwxr-xr-x root root 2017-01-11 01:06 emmc
drwxr-xr-x root root 2017-01-11 01:06 etc
drwxr-xr-x root root 2017-01-11 01:06 external_sd
-rw-r--r-- root root 10976 1970-01-01 00:00 file_contexts
-rw-r----- root root 1326 1970-01-01 00:00 fstab.universal5422
-rwxr-x--- root root 187840 1970-01-01 00:00 init
-rwxr-x--- root root 2778 1970-01-01 00:00 init.rc
drwxr-xr-x root root 2017-01-11 01:06 internal_sd
-rw-r--r-- root root 2048 1970-01-01 00:00 lpm.rc
drwxrwxr-x root system 2017-01-11 01:06 mnt
drwxr-xr-x root root 2016-03-14 17:26 preload
dr-xr-xr-x root root 1970-01-01 00:00 proc
-rw-r--r-- root root 2161 1970-01-01 00:00 property_contexts
drwxr-xr-x root root 2017-01-11 01:06 recovery
drwxr-xr-x root root 1970-01-01 00:00 res
drwx------ root root 2014-03-31 05:24 root
drwxr-x--- root root 1970-01-01 00:00 sbin
drwxr-xr-x root root 2017-01-11 01:06 sd-ext
lrwxrwxrwx root root 2017-01-11 01:06 sdcard -> /data/media
-rw-r--r-- root root 660 1970-01-01 00:00 seapp_contexts
-rw-r--r-- root root 93316 1970-01-01 00:00 sepolicy
d---r-x--- root sdcard_r 2017-01-11 01:06 storage
dr-xr-xr-x root root 2017-01-11 01:06 sys
drwxr-xr-x root root 2017-01-10 19:43 system
drwxrwxr-x root shell 2017-01-11 01:06 tmp
-rw-r--r-- root root 7275 1970-01-01 00:00 ueventd.rc
-rw-r--r-- root root 6626 1970-01-01 00:00 ueventd.universal5422.rc
Click to expand...
Click to collapse
itll be in the external or sdccard folders
maardobal said:
Hi to all!
So this is my case, right now IM really desperate.
My phone is a SM-G900H I installed this ROM: https://forum.xda-developers.com/ga...-exynos/rom-resurrection-remix-5-7-4-t3526192 (that BTW is a great proyect)
This works the first time until I reboot the phone, then I get stuck in a bootloop.
So from Sammobile I downloaded 3 different firmware and I flashed to my phone, this is what happens in all cases:
When Odin set on green and the phone reboots after the Samsung logo I see this:
But the progress bar always stops on "40%" and then change to this:
So what is that make me think there is something in the phone that is stopping the process..
This is what I tried to do:
- I flashed 3 different firmware including the Bl,AP,CP,PIT variation.
- I flashed TWRP, CWM and I used the recovery stock
- I try to recover my phone with OTA.
- I tried to change the kernel.
- I tried to recover a friend stock backup with twrp.
- Finally I used nand erase all
- Tried to flash STOCK ROM DEODEX of @yash92duster
- Tried the two PIT.
Data that maybe is useful:
- When I go to TWRP and I mount EFS then I go to filemanager and I click to the EFS folder, the phone reboots.
- I can't use ADB SHELL (with TWRP), if I type adb devices I don't see it, but if I use the stock recovery and I choose adb sideload I see the id and I can do sideload very well.
I have access to:
Download Mode.
ADB (Only if I flash philz recovery).
Recovery.
Folders an disk data:
---
---
What I think:
There is something that in the "updating" process make stop the progress so android finish erasing o reverting the process.
in advance!
Click to expand...
Click to collapse
Change battery simple and try different data cable
youdoofus said:
itll be in the external or sdccard folders
Click to expand...
Click to collapse
Only on external sd i have .android-secure and Android folder...
But only on sdcard, my problem happend even if sdcard is not on the device.
Any idea?
maardobal said:
Only on external sd i have .android-secure and Android folder...
But only on sdcard, my problem happend even if sdcard is not on the device.
Any idea?
Click to expand...
Click to collapse
the folder is just called "android", and if youve wiped your internal and its never fully booted since, it might not have the android folder on the internal as it gets created during the initial boot process
youdoofus said:
the folder is just called "android", and if youve wiped your internal and its never fully booted since, it might not have the android folder on the internal as it gets created during the initial boot process
Click to expand...
Click to collapse
I will try that idea then.. I keep you updated.
youdoofus said:
the image you provided only shows up with a stock recovery. download TWRP 3.0.2 and flash it in Odin. Or, better yet, get the stock tar.md5 file, flash it in Odin, let it boot, boot to download mode, flash TWRP, go to advanced options, file manager and erase the android folders from internal and external storage, root it via TWRP, wipe cache, dalvik cache and system 3 times (yes, 3 times) then flash whatever compatible ROM you wish. I run resurrection remix myself and its a bomb diggity ROM!!
Click to expand...
Click to collapse
I tried this, doesnt work, is still on bootloop :crying::crying::crying::crying:
maardobal said:
I tried this, doesnt work, is still on bootloop :crying::crying::crying::crying:
Click to expand...
Click to collapse
where did you get your tar file from?
Related
Credits:
birbeck for the usual random java guidance, slushpupie for his previous java guidance, dodgejcr for extreme amounts of testing, and one_love_420 and shift for some great graphics!
testers: JT-, couga6442, happytweak and many others I might have forgot in the furry of the initial three days I built a lot of the app from scratch!
Thanks to SDX
Background:
flash_image (bmlwrite) is an extremely useful utility for flashing custom kernels, boot logos and recoveries. This binary has made it possible to easily flash all these items and is used almost everywhere behind the scenes (i.e. in custom recoveries, packaged into kernel /sbin, etc).
Description:
This Android App is a GUI interface for the linux binary, flash_image provided by google in AOSP for loading custom kernels and recovery images onto the phone.
This app allows the flashing of kernels and recovery images in normal android mode.
No recovery or adb needed!
LG Optimus One, V, S and T support includes flashing of anykernel type .zip files, boot.img type zip files and recovery.img files!
Current Device Support:
Full Kernel, Logo and Recovery flashing: Samsung Moment, Transform, Intercept and Acclaim - the s3c6410 series of devices
Full Kernel (Anykernel and boot.img) Flashing and Recovery flashing: LG Optimus, HTC EVO 3D (CDMA & GSM), HTC EVO, HTC EVO Shift & Nexus S/Nexus S 4G
Full Kernel (zImage) Flashing: Samsung Epic
Future Support:
Looking for feedback regarding making the app more user friendly or simplier to use for the HTC EVO. Thanks!
Install Directions:
Install process is the same as any other .apk. Download to computer and adb push or mount sdcard on computer and copy over or download directly to the phone. Use any file manager, adb, connectbot/terminal emulator to install.
My preferred method, maybe a bit technical: adb install c:\downloads\FlashImageGUI.apk
Download Locations
Market (99 cents!): Flash Image GUI
Release versions (free from my personal hosting): Flash Image GUI
Contact:
Any questions, comments, concerns, or issues, please post in this thread or send me an email! Thanks for all the help and support!
FAQ:
Q: Will this app support a marketplace to pick and chose kernels from?
A: No. Use Kernel Manager!
Screenshots:
Splash Screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Main Screen
Options in Main Screen
Flashing Netarchy Kernel with Progress Bar Details
Flashing Clockworkmod Custom Recovery
i know there is a thread on this already, but hey, you're the developer, so i can care less. thanks for the app!
thnx !! its a cool app
Awesome work! Kudos. Once I get home I will flash with it and test. sounds like a great front end
Sent from my LG-P500 using XDA App
yes working on my GB...thanks
P500 now appears as an unsupported device with CM9.
With CM 7.2.0., we have this in /system/build.prop
Code:
ro.build.id=GRI40
ro.build.display.id=GWK74
ro.build.version.incremental=eng.jenkins.20120615.190413
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.7
ro.build.date=Fri Jun 15 19:04:23 PDT 2012
ro.build.date.utc=0
ro.build.type=user
ro.build.user=jenkins
ro.build.host=cyanogenmod
ro.build.tags=test-keys
ro.product.model=LG-P500
ro.product.brand=lge
ro.product.name=cyanogen_p500
ro.product.device=p500
ro.product.board=p500
ro.product.cpu.abi=armeabi
ro.product.manufacturer=LGE
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm7k
# ro.build.product is obsolete; use ro.product.device
ro.build.product=p500
With CM9 RC2, we have:
Code:
ro.build.id=IMM76L
ro.build.display.id=IMM76L
ro.build.version.incremental=eng.mint.20120726.140253
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Thu Jul 26 14:03:34 EEST 2012
ro.build.date.utc=1343300614
ro.build.type=user
ro.build.user=mint
ro.build.host=androidmeda
ro.build.tags=test-keys
ro.product.model=LG-P500
ro.product.brand=lge
ro.product.name=lge_p500
ro.product.device=p500
ro.product.board=p500
ro.product.cpu.abi=armeabi-v6l
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=LGE
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm7x27
# ro.build.product is obsolete; use ro.product.device
ro.build.product=p500
I frankly do not see what it the problem here with the device identification, pretty much the only relevant difference being ro.product.name=cyanogen_p500 vs ro.product.name=lge_p500
lolphirae said:
P500 now appears as an unsupported device with CM9.
With CM 7.2.0., we have this in /system/build.prop
Code:
ro.build.id=GRI40
ro.build.display.id=GWK74
ro.build.version.incremental=eng.jenkins.20120615.190413
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.7
ro.build.date=Fri Jun 15 19:04:23 PDT 2012
ro.build.date.utc=0
ro.build.type=user
ro.build.user=jenkins
ro.build.host=cyanogenmod
ro.build.tags=test-keys
ro.product.model=LG-P500
ro.product.brand=lge
ro.product.name=cyanogen_p500
ro.product.device=p500
ro.product.board=p500
ro.product.cpu.abi=armeabi
ro.product.manufacturer=LGE
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm7k
# ro.build.product is obsolete; use ro.product.device
ro.build.product=p500
With CM9 RC2, we have:
Code:
ro.build.id=IMM76L
ro.build.display.id=IMM76L
ro.build.version.incremental=eng.mint.20120726.140253
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Thu Jul 26 14:03:34 EEST 2012
ro.build.date.utc=1343300614
ro.build.type=user
ro.build.user=mint
ro.build.host=androidmeda
ro.build.tags=test-keys
ro.product.model=LG-P500
ro.product.brand=lge
ro.product.name=lge_p500
ro.product.device=p500
ro.product.board=p500
ro.product.cpu.abi=armeabi-v6l
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=LGE
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm7x27
# ro.build.product is obsolete; use ro.product.device
ro.build.product=p500
I frankly do not see what it the problem here with the device identification, pretty much the only relevant difference being ro.product.name=cyanogen_p500 vs ro.product.name=lge_p500
Click to expand...
Click to collapse
The build.prop is generally helpful but not being used by FIG in this case.
Can you post the results of ls -l / from each version?
This information is in the kernel and also important.
joeykrim said:
The build.prop is generally helpful but not being used by FIG in this case.
Can you post the results of ls -l / from each version?
This information is in the kernel and also important.
Click to expand...
Click to collapse
Uuuuh. Cannot find a nandroid backup of CM 7.2 anywhere and unfortunately do not have time to reinstall the entire phone ATM. Hopefully someone else on official CM7 will post the info here. Meanwhile, the info from CM9:
Code:
$ adb shell ls -l /
drwxr-xr-x root root 2012-07-27 05:08 acct
drwxrwx--x system cache 2012-07-26 17:31 cache
-rwxr-x--- root root 248808 1970-01-01 02:00 charger
dr-x------ root root 2012-07-27 05:08 config
lrwxrwxrwx root root 2012-07-27 05:08 d -> /sys/kernel/debug
drwxrwx--x system system 2012-07-26 17:23 data
-rw-r--r-- root root 116 1970-01-01 02:00 default.prop
drwxr-xr-x root root 2012-07-27 05:20 dev
lrwxrwxrwx root root 2012-07-27 05:08 etc -> /system/etc
-rwxr-x--- root root 102816 1970-01-01 02:00 init
-rwxr-x--- root root 2344 1970-01-01 02:00 init.goldfish.rc
-rwxr-x--- root root 717 1970-01-01 02:00 init.p500.rc
-rwxr-x--- root root 7809 1970-01-01 02:00 init.qcom.rc
-rwxr-x--- root root 1997 1970-01-01 02:00 init.qcom.sh
-rwxr-x--- root root 2482 1970-01-01 02:00 init.qcom.usb.rc
-rwxr-x--- root root 18533 1970-01-01 02:00 init.rc
drwxrwxr-x root system 2012-07-27 05:08 mnt
dr-xr-xr-x root root 1970-01-01 02:00 proc
drwxr-xr-x root root 1970-01-01 02:00 res
drwx------ root root 2012-07-26 13:36 root
drwxr-x--- root root 1970-01-01 02:00 sbin
drwxrwx--x system system 2012-07-26 17:24 sd-ext
lrwxrwxrwx root root 2012-07-27 05:08 sdcard -> /mnt/sdcard
drwxr-xr-x root root 2012-07-27 05:08 sys
drwxr-xr-x root root 2012-07-26 17:17 system
-rw-r--r-- root root 272 1970-01-01 02:00 ueventd.goldfish.rc
-rw-r--r-- root root 5562 1970-01-01 02:00 ueventd.p500.rc
-rw-r--r-- root root 5562 1970-01-01 02:00 ueventd.qcom.rc
-rw-r--r-- root root 3825 1970-01-01 02:00 ueventd.rc
lrwxrwxrwx root root 2012-07-27 05:08 vendor -> /system/vendor
Thanks! :good:
Does this work for the optimus v
lolphirae said:
Uuuuh. Cannot find a nandroid backup of CM 7.2 anywhere and unfortunately do not have time to reinstall the entire phone ATM. Hopefully someone else on official CM7 will post the info here. Meanwhile, the info from CM9:
Code:
$ adb shell ls -l /
drwxr-xr-x root root 2012-07-27 05:08 acct
drwxrwx--x system cache 2012-07-26 17:31 cache
-rwxr-x--- root root 248808 1970-01-01 02:00 charger
dr-x------ root root 2012-07-27 05:08 config
lrwxrwxrwx root root 2012-07-27 05:08 d -> /sys/kernel/debug
drwxrwx--x system system 2012-07-26 17:23 data
-rw-r--r-- root root 116 1970-01-01 02:00 default.prop
drwxr-xr-x root root 2012-07-27 05:20 dev
lrwxrwxrwx root root 2012-07-27 05:08 etc -> /system/etc
-rwxr-x--- root root 102816 1970-01-01 02:00 init
-rwxr-x--- root root 2344 1970-01-01 02:00 init.goldfish.rc
-rwxr-x--- root root 717 1970-01-01 02:00 init.p500.rc
-rwxr-x--- root root 7809 1970-01-01 02:00 init.qcom.rc
-rwxr-x--- root root 1997 1970-01-01 02:00 init.qcom.sh
-rwxr-x--- root root 2482 1970-01-01 02:00 init.qcom.usb.rc
-rwxr-x--- root root 18533 1970-01-01 02:00 init.rc
drwxrwxr-x root system 2012-07-27 05:08 mnt
dr-xr-xr-x root root 1970-01-01 02:00 proc
drwxr-xr-x root root 1970-01-01 02:00 res
drwx------ root root 2012-07-26 13:36 root
drwxr-x--- root root 1970-01-01 02:00 sbin
drwxrwx--x system system 2012-07-26 17:24 sd-ext
lrwxrwxrwx root root 2012-07-27 05:08 sdcard -> /mnt/sdcard
drwxr-xr-x root root 2012-07-27 05:08 sys
drwxr-xr-x root root 2012-07-26 17:17 system
-rw-r--r-- root root 272 1970-01-01 02:00 ueventd.goldfish.rc
-rw-r--r-- root root 5562 1970-01-01 02:00 ueventd.p500.rc
-rw-r--r-- root root 5562 1970-01-01 02:00 ueventd.qcom.rc
-rw-r--r-- root root 3825 1970-01-01 02:00 ueventd.rc
lrwxrwxrwx root root 2012-07-27 05:08 vendor -> /system/vendor
Thanks! :good:
Click to expand...
Click to collapse
this is exactly the type of information i need. im investigating the issue. optimistic it should be a simple fix. will keep you updated here.
if it is simple as i hope, ill push some other things aside and aim for releasing an update this weekend.
smokeboy67 said:
Does this work for the optimus v
Click to expand...
Click to collapse
Yes, it should. If you have any issues, please post up the error message with a screenshot. Thanks!
Does this work on LG optimus p500?
Sent from my LG-P500 using xda premium
acerkumar said:
Does this work on LG optimus p500?
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
Yep
Sent from my LG-P509 using Tapatalk 2
I don't know why, but the two times I used this app left me in fastboot :crying:
sweetnsour said:
I don't know why, but the two times I used this app left me in fastboot :crying:
Click to expand...
Click to collapse
+1 actually it doenst work for me too i first flashed recovery with this only and gone in fastboot
i have read about this app in optimus v forum but not anywhere else for the p500
sweetnsour said:
I don't know why, but the two times I used this app left me in fastboot :crying:
Click to expand...
Click to collapse
Hmm..were you flashing a recovery or kernel? I used to use this all the time to flash kernels(Franco days) but I've never used it to flash a recovery..
EDIT: just flashed caf kernel using flash image GUI and worked without any problems.. I think at one time it wasn't working correctly on cm9 roms and Joey was gonna try and fix the issue..knowing his dedication to this app im sure he did
Sent from my LG-P509 using Tapatalk 2
jerry7389 said:
Hmm..were you flashing a recovery or kernel? I used to use this all the time to flash kernels(Franco days) but I've never used it to flash a recovery..
EDIT: just flashed caf kernel using flash image GUI and worked without any problems.. I think at one time it wasn't working correctly on cm9 roms and Joey was gonna try and fix the issue..knowing his dedication to this app im sure he did
Sent from my LG-P509 using Tapatalk 2
Click to expand...
Click to collapse
try flashing recovery
ok just joking ya i think sweetnsour tried fLashing recovery like me
androidisfuture said:
try flashing recovery
ok just joking ya i think sweetnsour tried fLashing recovery like me
Click to expand...
Click to collapse
Haha I'm sure he did..at least it isn't too hard to do it manually
Sent from my LG-P509 using Tapatalk 2
androidisfuture said:
try flashing recovery
ok just joking ya i think sweetnsour tried fLashing recovery like me
Click to expand...
Click to collapse
jerry7389 said:
Haha I'm sure he did..at least it isn't too hard to do it manually
Sent from my LG-P509 using Tapatalk 2
Click to expand...
Click to collapse
I think I was trying to flash a recovery
So I guess this is safe for kernels then? By the way, what is the difference between using a recovery and using this app to flash kernels?
sweetnsour said:
I think I was trying to flash a recovery
So I guess this is safe for kernels then? By the way, what is the difference between using a recovery and using this app to flash kernels?
Click to expand...
Click to collapse
Not much.. Its a tad bit faster and easier.. You dont have to manually boot into recovery and wipe cache and dalvik
Sent from my LG-P509 using Tapatalk 2
androidisfuture said:
+1 actually it doenst work for me too i first flashed recovery with this only and gone in fastboot
i have read about this app in optimus v forum but not anywhere else for the p500
Click to expand...
Click to collapse
androidisfuture said:
try flashing recovery
ok just joking ya i think sweetnsour tried fLashing recovery like me
Click to expand...
Click to collapse
Thanks for reporting this issue. I searched through the code and I think I know the problem area but will need a tester who is knowledgeable with ADB and using fastboot to recovery from a bad recovery flash. If any of you have time and have those skills, please send me a PM and I can work on fixing the issue!
jerry7389 said:
Hmm..were you flashing a recovery or kernel? I used to use this all the time to flash kernels(Franco days) but I've never used it to flash a recovery..
EDIT: just flashed caf kernel using flash image GUI and worked without any problems.. I think at one time it wasn't working correctly on cm9 roms and Joey was gonna try and fix the issue..knowing his dedication to this app im sure he did
Sent from my LG-P509 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for confirming the kernel flashing portion works well on the P500
Thanks to everybody for the support!
K, i've got a wii emulator, but i don't understand how to run these commands !!! +_+
To increase stability on Galaxy S4 and other Adreno 3xx devices with driver v14, you need to root and run the following commands on the device as root.
Code:
echo 0 > /sys/kernel/debug/kgsl/kgsl-3d0/fast_hang_detect
echo 0 > /sys/kernel/debug/kgsl/kgsl-3d0/ft_pagefault_policy
echo 0 > /sys/kernel/debug/kgsl/kgsl-3d0/ft_policy
echo 0 > /sys/kernel/debug/kgsl/kgsl-3d0/ib_check
echo 0 > /sys/kernel/debug/kgsl/kgsl-3d0/long_ib_detect
Can someone please educate me on how this is suppose to work? do i need an android terminal? or how do i go about running these commands?
(yes my phone is rooted)
Thanks
Ryan
milkydude12 said:
i don't understand how to run these commands
Click to expand...
Click to collapse
These are system commands and you need to run them from the "command line". The easiest way to do that would be to install a terminal application. Android Terminal Emulator by Jack Palevich is one good choice. Or you could run an adb shell.
After you install terminal emulator, enter
su [enter]
Click to expand...
Click to collapse
"su" is the command for superuser (root access). Then you can use the system configuration commands that you have for your wii emulator.
If any commands need to be reentered each time you use your emulator, then you could use a scripting app like gscript light which can be configured to enter these commands from a bookmark. i.e. just click on a bookmark and it will run a set of commands for you.
.
Hi,
Thanks for replying!!! I've a problem though , after i enter su (enter) then grant superuser, i type in echo 0 > /sys/kernel/debug/kgsl/kgsl-3d0/fast_hang_detect
then i get no such file or directory , what am i doing wrong???
milkydude12 said:
Hi,
Thanks for replying!!! I've a problem though , after i enter su (enter) then grant superuser, i type in echo 0 > /sys/kernel/debug/kgsl/kgsl-3d0/fast_hang_detect
then i get no such file or directory , what am i doing wrong???
Click to expand...
Click to collapse
Do you have those directories on your phone? Where did you get the commands to type in? Are they specific to the s4?
jd1639 said:
Do you have those directories on your phone? Where did you get the commands to type in? Are they specific to the s4?
Click to expand...
Click to collapse
I got the commands from here https://forums.dolphin-emu.org/Thread-opengl-es-3-guide i apologize if im not supposed to post link +_+
I can't add much more than jd1639 already suggested. These commands would just make a temporary configuration change to half a dozen driver settings in aid of your emulator program. The "echo 0" command ensures that a particular setting is set to "0", if the target file exists.
Check for typos. If there weren't any typos, then it would seem likely that the information from the original thread is inaccurate or out of date. What model of phone are you trying this on? The original thread refers to the i9505 and similar phones. Is your phone a i9505? The fact that you're posting this in an AT&T, et al forum suggest that you might actually have a i337 /i337m phone. Depending on what model you actually have, your phone may have a Snapdragon 800 or Exynos processor rather than the Snapdragon 600.
The drivers may or may not be the same across different phones and processors. Or the drivers names may have changed in a subsequent firmware update. You check your filesystem to see if those paths exist or if the file names can be found elsewhere. Then look to the emulator thread for further guidance.
I had a quick look at a S3 and some, but not all of those files exist. If you find the same thing on your S4, then you'll have to refer to the emulator thread to discern if you need to have all of those items to enable your emulator or if a subset will suffice.
You can probably just create any "missing" files for a workable solution. They're just text files that the drivers refer to for guidance. It's something that I'd at least try in your place. However while I don't perceive any real risk in that i.e. worst case it wouldn't boot and you'd need to restore a backup.. don't look to me if your phone unexpectedly wimpers, fails or becomes sentient and disagrees. Anything you actually do is at your own risk.
You can search paths and file names as follows below. And you should be able to use the touch, mv or cp commands (or install a text editor) to create a missing file.
$ su
# cd /sys/kernel/debug/kgsl/kgsl-3d0
# ls -la
# find / -name fast_hang_detect
.
fffft said:
I can't add much more than jd1639 already suggested. These commands would just make a temporary configuration change to half a dozen driver settings in aid of your emulator program. The "echo 0" command ensures that a particular setting is set to "0", if the target file exists.
Check for typos. If there weren't any typos, then it would seem likely that the information from the original thread is inaccurate or out of date. What model of phone are trying this on? The original thread refers to the i9505 and similar phones. Is your phone a i9505? The fact that you're posting this in an AT&T, et al forum suggest that you might actually have a i337 /i337m phone. Depending on what model you actually have, your phone may have a Snapdragon 800 or Exynos processor rather than the Snapdragon 600.
The drivers may or may not be the same across different phones and processors. Or the drivers names may have changed in a subsequent firmware update. You should look at your filesystem as jd1639 suggested to see if those paths exist or if the file names can be found elsewhere. And if necessary, re-read the emulator thread for further guidance.
I had a quick look at a S3 and some, but not all of those files exist. If you find the same thing on your S4, then you'll have to refer to the emulator thread to discern if you need to have all of those items to enable your emulator or if a subset will suffice.
You can probably just create any "missing" files for a workable solution. They're just text files that the drivers refer to for guidance. It's something that I'd at least try in your place. However while I don't perceive any real risk in that i.e. worst case it wouldn't boot and you'd need to restore a backup.. don't look to me if your phone unexpectedly wimpers, fails or becomes sentient and disagrees. Anything you actually do is at your own risk.
You can search paths and file names as follows below. And you should be able to use the touch, mv or cp commands to create a missing file.
$ su
# cd /sys/kernel/debug/kgsl/kgsl-3d0
# ls -la
# find / -name fast_hang_detect
.
Click to expand...
Click to collapse
Hi, I have the I337m variety of the Samsung S4 will that make a difference?
milkydude12 said:
Hi, I have the I337m variety of the Samsung S4 will that make a difference?
Click to expand...
Click to collapse
The answer to that will be in your emulator thread.
More to the point, you haven't done your homework yet. Do those paths and files exist on your phone? Does the emulator thread clarify if all of those settings are required? And did you try creating any missing files? People are trying to help you here, but we can't see what your phone screen actually shows. And you should be doing most of the work to see what does or doesn't work.
.
[email protected]:/ $ su
[email protected]:/ # cd /sys/kernal/debugkgsl-3d0
tmp-mksh: cd: /sys/kernal/debugkgsl-3d0: No such file or directory
2|[email protected]:/ # ls -la
-rw-r--r-- root root 4721 1969-12-31 17:00 MSM8960_lpm.rc
drwxr-xr-x root root 1970-05-26 22:16 acct
drwxrwx--- system cache 2014-02-07 20:41 cache-rwxr-x--- root root 268036 1969-12-31 17:00 charger
dr-x------ root root 1970-05-26 22:16 config
lrwxrwxrwx root root 1970-05-26 22:16 d -> /sys/kernel/debug
drwxrwx--x system system 2014-02-07 19:42 data
drwxrwx--- system system 1970-05-26 22:16 data_1
drwxrwx--- system system 1970-05-26 22:16 data_2
drwxrwx--- system system 1970-05-26 22:16 data_3
-rw-r--r-- root root 165 1969-12-31 17:00 default.prop
drwxr-xr-x root root 2014-02-07 01:35 dev
drwxrwx--x system radio 2014-01-31 20:30 efs
lrwxrwxrwx root root 1970-05-26 22:16 etc -> /system/etc
-rw-r--r-- root root 21233 1969-12-31 17:00 file_contexts
dr-xr-x--- system system 1970-05-26 22:16 firmware
dr-xr-x--- system system 1970-05-26 22:16 firmware-mdm
-rw-r----- root root 1494 1969-12-31 17:00 fstab.qcom
-rwxr-x--- root root 171036 1969-12-31 17:00 init
-rwxr-x--- root root 3068 1969-12-31 17:00 init.carrier.rc
-rwxr-x--- root root 769 1969-12-31 17:00 init.container.rc
-rwxr-x--- root root 6737 1969-12-31 17:00 init.qcom.class_core.sh
-rwxr-x--- root root 2320 1969-12-31 17:00 init.qcom.class_main.sh
-rwxr-x--- root root 4266 1969-12-31 17:00 init.qcom.early_boot.sh
-rwxr-x--- root root 5142 1969-12-31 17:00 init.qcom.lpm_boot.sh
-rwxr-x--- root root 22920 1969-12-31 17:00 init.qcom.rc
-rwxr-x--- root root 3045 1969-12-31 17:00 init.qcom.ril.sh
-rwxr-x--- root root 4486 1969-12-31 17:00 init.qcom.sh
-rwxr-x--- root root 3830 1969-12-31 17:00 init.qcom.syspart_fixup.sh
-rwxr-x--- root root 35468 1969-12-31 17:00 init.qcom.usb.rc
-rwxr-x--- root root 6004 1969-12-31 17:00 init.qcom.usb.sh
-rwxr-x--- root root 41170 1969-12-31 17:00 init.rc
-rwxr-x--- root root 9314 1969-12-31 17:00 init.target.rc
-rwxr-x--- root root 1795 1969-12-31 17:00 init.trace.rc
-rwxr-x--- root root 3915 1969-12-31 17:00 init.usb.rc
drwxrwxr-x root system 1970-05-26 22:16 mnt
drwxrwxr-x root system 1970-05-26 22:16 mnt_1drwxr-xr-x system system 1970-05-26 22:16 persdata
drwxrwx--x system system 1970-05-26 22:16 preload
dr-xr-xr-x root root 1969-12-31 17:00 proc
-rw-r--r-- root root 2838 1969-12-31 17:00 property_contexts
drwxr-xr-x root root 1969-12-31 17:00 res
drwx------ root root 2013-11-15 08:26 root
drwxr-x--- root root 1969-12-31 17:00 sbin
lrwxrwxrwx root root 1970-05-26 22:16 sdcard -> /storage/emulated/legacy
-rw-r--r-- root root 3887 1969-12-31 17:00 seapp_contexts
-rw-r--r-- root root 610434 1969-12-31 17:00 sepolicy
-rw-r--r-- root root 207 1969-12-31 17:00 sepolicy_version
dr-xr-x--- system sdcard_r 1970-05-26 22:16 storage
dr-xr-xr-x root root 1970-05-26 22:16 sys
drwxr-xr-x root root 1970-03-21 22:11 system
drwxr-xr-x root root 2014-01-31 20:30 tmp-mksh
lrwxrwxrwx root root 1970-05-26 22:16 tombstones -> /data/tombstones
-rw-r--r-- root root 6662 1969-12-31 17:00 ueventd.qcom.rc
-rw-r--r-- root root 4794 1969-12-31 17:00 ueventd.rc
lrwxrwxrwx root root 1970-05-26 22:16 vendor -> /system/vendor
[email protected]:/ # find / -namefast_hang_detect
find: unrecognized: -namefast_hang_detect
BusyBox v1.21.1-Stericson (2013-09-26 14:33:26 BST) multi-call binary.
Usage: find [PATH]... [OPTIONS] [ACTIONS]
Search for files and perform actions on them.
First failed action stops processing of current file.
Defaults: PATH is current directory, action is '-print'
-follow Follow symlinks
-xdev Don't descend directories on other filesystems
-maxdepth N Descend at most N levels. -maxdepth 0 applies
actions to command line arguments only
-mindepth N Don't act on first N levels
-depth Act on directory *after* traversing it
Actions:
( ACTIONS ) Group actions for -o / -a
! ACT Invert ACT's success/failure
ACT1 [-a] ACT2 If ACT1 fails, stop, else do ACT2
ACT1 -o ACT2 If ACT1 succeeds, stop, else do ACT2 Note: -a has higher priority than -o -name PATTERN Match file name (w/o directory name) to PATTERN
-iname PATTERN Case insensitive -name
-path PATTERN Match path to PATTERN
-ipath PATTERN Case insensitive -path
-regex PATTERN Match path to regex PATTERN
-type X File type is X (one of: f,d,l,b,c,...)
-perm MASK At least one mask bit (+MASK), all bits (-MASK),
or exactly MASK bits are set in file's mode
-mtime DAYS mtime is greater than (+N), less than (-N),
or exactly N days in the past
-mmin MINS mtime is greater than (+N), less than (-N),
or exactly N minutes in the past
-newer FILE mtime is more recent than FILE's
-inum N File has inode number N
-user NAME/ID File is owned by given user
-group NAME/ID File is owned by given group
-size N[bck] File size is N (c:bytes,k:kbytes,b:512 bytes(def.))
+/-N: file size is bigger/smaller than N
-links N Number of links is greater than (+N), less than (-N),
or exactly N
-prune If current file is directory, don't descend into it
If none of the following actions is specified, -print is assumed
-print Print file name
-print0 Print file name, NUL terminated
-exec CMD ARG ; Run CMD with all instances of {} replaced by
file name. Fails if CMD exits with nonzero
-delete Delete current file/directory. Turns on -depth option
1|[email protected]:/ #
That is what i get, for the life of me i can't figure out if that means i have it or i don't. "On the Thread it says To increase stability on Galaxy S4 and other Adreno 3xx devices with driver v14, you need to root and run the following commands on the device as root."
So I'm assuming i require all of them to work in order for any difference. Certain sites list the I337m varient as one of which supports Open Gl ES 3 so i assume it would work
All right, I can understand how a lot of this might be a challenge to understand if you have no experience with linux. But you at least need to make sure that you aren't making typos when using these commands.
e.g.
[email protected]:/ # find / -namefast_hang_detect
Click to expand...
Click to collapse
You missed a space between -name and the actual file name. And yes, that is critical. Nothing here is likely to work if you have typos. Try the following and paste the results back here. And I or someone else will better understand what is going on::
$ su
# cd /sys/kernel/debug/kgsl/kgsl-3d0
# ls -la
(exactly as above and paste the result for us).
If you are ambitious then also try the following for any "missing" files and let us know if that succeeds in getting your emulator up and running.
e.g.
# touch /sys/kernel/debug/kgsl/kgsl-3d0/fast_hang_detect
# echo 0 > /sys/kernel/debug/kgsl/kgsl-3d0/fast_hang_detect
.
:S thanks i didn't know i had missed a space, and yea i have little to no experience with linux.
[email protected]:/ $ su
[email protected]:/ # cd /sys/kernal/debug/kgsl/3d0
tmp-mksh: cd: /sys/kernal/debug/kgsl/3d0: No such file or directory
2|[email protected]:/ # ls -la
-rw-r--r-- root root 4721 1969-12-31 17:00 MSM8960_lpm.rc
drwxr-xr-x root root 1970-05-26 22:16 acct
drwxrwx--- system cache 2014-02-07 22:44 cache
-rwxr-x--- root root 268036 1969-12-31 17:00 charger
dr-x------ root root 1970-05-26 22:16 config
lrwxrwxrwx root root 1970-05-26 22:16 d -> /sys/kernel/debug
drwxrwx--x system system 2014-02-07 19:42 data
drwxrwx--- system system 1970-05-26 22:16 data_1
drwxrwx--- system system 1970-05-26 22:16 data_2
drwxrwx--- system system 1970-05-26 22:16 data_3
-rw-r--r-- root root 165 1969-12-31 17:00 default.prop
drwxr-xr-x root root 2014-02-07 01:35 dev
drwxrwx--x system radio 2014-01-31 20:30 efs
lrwxrwxrwx root root 1970-05-26 22:16 etc -> /system/etc
-rw-r--r-- root root 21233 1969-12-31 17:00 file_contexts
dr-xr-x--- system system 1970-05-26 22:16 firmware
dr-xr-x--- system system 1970-05-26 22:16 firmware-mdm
-rw-r----- root root 1494 1969-12-31 17:00 fstab.qcom
-rwxr-x--- root root 171036 1969-12-31 17:00 init
-rwxr-x--- root root 3068 1969-12-31 17:00 init.carrier.rc
-rwxr-x--- root root 769 1969-12-31 17:00 init.container.rc
-rwxr-x--- root root 6737 1969-12-31 17:00 init.qcom.class_core.sh
-rwxr-x--- root root 2320 1969-12-31 17:00 init.qcom.class_main.sh
-rwxr-x--- root root 4266 1969-12-31 17:00 init.qcom.early_boot.sh
-rwxr-x--- root root 5142 1969-12-31 17:00 init.qcom.lpm_boot.sh
-rwxr-x--- root root 22920 1969-12-31 17:00 init.qcom.rc
-rwxr-x--- root root 3045 1969-12-31 17:00 init.qcom.ril.sh
-rwxr-x--- root root 4486 1969-12-31 17:00 init.qcom.sh
-rwxr-x--- root root 3830 1969-12-31 17:00 init.qcom.syspart_fixup.sh
-rwxr-x--- root root 35468 1969-12-31 17:00 init.qcom.usb.rc
-rwxr-x--- root root 6004 1969-12-31 17:00 init.qcom.usb.sh
-rwxr-x--- root root 41170 1969-12-31 17:00 init.rc
-rwxr-x--- root root 9314 1969-12-31 17:00 init.target.rc
-rwxr-x--- root root 1795 1969-12-31 17:00 init.trace.rc
-rwxr-x--- root root 3915 1969-12-31 17:00 init.usb.rc
drwxrwxr-x root system 1970-05-26 22:16 mnt
drwxrwxr-x root system 1970-05-26 22:16 mnt_1
drwxr-xr-x system system 1970-05-26 22:16 persdata
drwxrwx--x system system 1970-05-26 22:16 preload
dr-xr-xr-x root root 1969-12-31 17:00 proc
-rw-r--r-- root root 2838 1969-12-31 17:00 property_contexts
drwxr-xr-x root root 1969-12-31 17:00 res
drwx------ root root 2013-11-15 08:26 root
drwxr-x--- root root 1969-12-31 17:00 sbin
lrwxrwxrwx root root 1970-05-26 22:16 sdcard -> /storage/emulated/legacy
-rw-r--r-- root root 3887 1969-12-31 17:00 seapp_contexts
-rw-r--r-- root root 610434 1969-12-31 17:00 sepolicy
-rw-r--r-- root root 207 1969-12-31 17:00 sepolicy_version
dr-xr-x--- system sdcard_r 1970-05-26 22:16 storage
dr-xr-xr-x root root 1970-05-26 22:16 sys
drwxr-xr-x root root 1970-03-21 22:11 system
drwxr-xr-x root root 2014-01-31 20:30 tmp-mksh
lrwxrwxrwx root root 1970-05-26 22:16 tombstones -> /data/tombstones
-rw-r--r-- root root 6662 1969-12-31 17:00 ueventd.qcom.rc
-rw-r--r-- root root 4794 1969-12-31 17:00 ueventd.rc
lrwxrwxrwx root root 1970-05-26 22:16 vendor -> /system/vendor
[email protected]:/ # find / -name fast_hang_detect
find: /proc/718/task/1014/fdinfo/459: No such file or directory
find: /proc/718/task/1015/fd/459: No such file or directory
find: /proc/718/task/1040/fd/459: No such file or directory
find: /proc/718/task/1331/fd/459: No such file or directory
find: /proc/718/task/1702/fd/459: No such file or directory
find: /proc/718/task/15245/fdinfo/459: No such file or directory
1|[email protected]:/ # touch /sys/kernal/debug/kgsl/kgsl-3d0/fast_hang_detect
gsl/kgsl-3d0/fast_hang_detect <
tmp-mksh: can't create /sys/kernal/debug/kgsl/kgsl-3d0/fast_hang_detect: No such file or directory
1|[email protected]:/ #
You're still making multiple typos, so we didn't get the information that we need.
.
.
After fixing all my typos and spending hours trying to get it to work, ive come to the conclusion, yea ive got the wrong phone model :S .... well that was a waste of time
:cyclops:
Well, many people have problems on the /persist partition, maybe because some bad rom, or maybe because by a mistake you formatted them on a recovery (a bad recovery without forbid partitions).
Before this zip, you have to copy the "WCNSS_qcom_wlan_factory_nv.bin" to /persist manually, but some file managers don't mount well /persist.
But now, only flashing this zip, it will copy the file to /persist and Wifi go back to work.
:highfive:
Download from:
MEDIAFIRE!
MEGA!
Boss442 said:
Well, many people have problems on the /persist partition, maybe because some bad rom, or maybe because by a mistake you formatted them on a recovery (a bad recovery without forbid partitions).
Before this zip, you have to copy the "WCNSS_qcom_wlan_factory_nv.bin" to /persist manually, but some file managers don't mount well /persist.
But now, only flashing this zip, it will copy the file to /persist and Wifi go back to work.
:highfive:
Download from:
MEDIAFIRE!
MEGA!
Click to expand...
Click to collapse
Bro how to flash it ?
I flashed with twrp v3.0
it gave an error at the end. unable to mount something.
wifi is not working on my mot g2013. I have tried 5-6 roms.
Pls help
does it work?
No it dint.
Twrp gave error. Also the file whicg have to copy in that persist folder gets deleted automatically.
This works
OK, this works but not exactly by flashing.
First of all, this file is a WLAN Qualcom driver which is somehow missing after flashing errors.
Step by step:
1. Enable root for ADB in developer settings in your phone
2. Connect your phone with USB
3.
Code:
adb root
4. Now adb will reconnect as root. Enter command above again to make sure it's done (you will receive confirmation)
5. /persist is not accessible by default (read-only) so we must mount it as writable partition
6.
Code:
adb shell
7.
Code:
mount -o rw,remount /persist
8.
Code:
exit
- we are exiting shell now
9.
Code:
adb push WCNSS_qcom_wlan_factory_nv.bin /persist/
- we are copying driver to phone
10. OK, drivers are now saved on our phone. Let's remount /persist again to be read only:
11.
Code:
adb shell
12.
Code:
mount -o ro,remount /persist
13.
Code:
exit
14. Reboot your phone
If you have unsufficient permissions or something, try
Code:
chmod 777 /persist
after point 7 and
Code:
chmod 771 /persist
after point 11
Tell me if it works, was ok for me.
zyzioziom said:
OK, this works but not exactly by flashing.
First of all, this file is a WLAN Qualcom driver which is somehow missing after flashing errors.
Step by step:
1. Enable root for ADB in developer settings in your phone
2. Connect your phone with USB
3.
Code:
adb root
4. Now adb will reconnect as root. Enter command above again to make sure it's done (you will receive confirmation)
5. /persist is not accessible by default (read-only) so we must mount it as writable partition
6.
Code:
adb shell
7.
Code:
mount -o rw,remount /persist
8.
Code:
exit
- we are exiting shell now
9.
Code:
adb push WCNSS_qcom_wlan_factory_nv.bin /persist/
- we are copying driver to phone
10. OK, drivers are now saved on our phone. Let's remount /persist again to be read only:
11.
Code:
adb shell
12.
Code:
mount -o ro,remount /persist
13.
Code:
exit
14. Reboot your phone
If you have unsufficient permissions or something, try
Code:
chmod 777 /persist
after point 7 and
Code:
chmod 771 /persist
after point 11
Tell me if it works, was ok for me.
Click to expand...
Click to collapse
Zyzoom Hello, first of all sorry for my poor English, I have a XT1032 with the same problem, after installing TWRP recovery and CM13 Nightly 3.0.0, and was unable to enable Wi-Fi.
I followed your steps, but in step 9 out "Read-only file system", so I resume the steps from 6 (adb shell), then "mount -o rw, remount / persist" I write "chmod 777 / persist" but I back out the error " Read-only file system. "
Would you help me please?
norte112 said:
Zyzoom Hello, first of all sorry for my poor English, I have a XT1032 with the same problem, after installing TWRP recovery and CM13 Nightly 3.0.0, and was unable to enable Wi-Fi.
I followed your steps, but in step 9 out "Read-only file system", so I resume the steps from 6 (adb shell), then "mount -o rw, remount / persist" I write "chmod 777 / persist" but I back out the error " Read-only file system. "
Would you help me please?
Click to expand...
Click to collapse
norte112, you need to write commands exactly like I wrote. Do not put space between "/" and "persist" and between "rw," and "remount".
The best is to copy them directly to terminal, I think it's CTRL+INSERT or SHIFT+INSERT on Windows
zyzioziom said:
norte112, you need to write commands exactly like I wrote. Do not put space between "/" and "persist" and between "rw," and "remount".
The best is to copy them directly to terminal, I think it's CTRL+INSERT or SHIFT+INSERT on Windows
Click to expand...
Click to collapse
The commands were copied and pasted as contained in the post directly to cmd, for an error when writing this query, add spaces, but just confirm again (no spaces) and still gives the same error message.
norte112 said:
The commands were copied and pasted as contained in the post directly to cmd, for an error when writing this query, add spaces, but just confirm again (no spaces) and still gives the same error message.
Click to expand...
Click to collapse
Code:
adb shell
ls -al
And paste the results here
Also, try whole process again but after each "adb shell" add another command: "su"
zyzioziom said:
Code:
adb shell
ls -al
And paste the results here
Also, try whole process again but after each "adb shell" add another command: "su"
Click to expand...
Click to collapse
Deputy results:
D:\xt1032\ABD-fastboot>adb shell
←7←[r←[999;999H←[6nls -al
←[email protected]:/ $
I also tried adding SU command after SHELL, but after giving intro but does not allow me to enter any other line or command (attached results):
D:\xt1032\ABD-fastboot>adb root
adbd is already running as root
D:\xt1032\ABD-fastboot>adb shell su
[email protected]:/ #
norte112 said:
Deputy results:
D:\xt1032\ABD-fastboot>adb shell
←7←[r←[999;999H←[6nls -al
←[email protected]:/ $
I also tried adding SU command after SHELL, but after giving intro but does not allow me to enter any other line or command (attached results):
D:\xt1032\ABD-fastboot>adb root
adbd is already running as root
D:\xt1032\ABD-fastboot>adb shell su
[email protected]:/ #
Click to expand...
Click to collapse
You have strange results here :/
Here is my console:
Code:
Patryks-MacBook-Air:platform-tools patryk$ ./adb devices
List of devices attached
TA9290KDJ1 device
Patryks-MacBook-Air:platform-tools patryk$ ./adb root
adbd is already running as root
Patryks-MacBook-Air:platform-tools patryk$ ./adb shell
[email protected]:/ # ls -al
total 2382
drwxr-xr-x 19 root root 0 1970-06-28 19:00 .
drwxr-xr-x 19 root root 0 1970-06-28 19:00 ..
drwxr-xr-x 44 root root 0 1970-06-28 19:00 acct
drwxrwx--- 6 system cache 4096 2016-03-05 03:28 cache
lrwxrwxrwx 1 root root 13 1970-01-01 01:00 charger -> /sbin/healthd
dr-x------ 2 root root 0 1970-06-28 19:00 config
lrwxrwxrwx 1 root root 17 1970-06-28 19:00 d -> /sys/kernel/debug
drwxrwx--x 35 system system 4096 2016-03-09 18:37 data
-rw-r--r-- 1 root root 555 1970-01-01 01:00 default.prop
drwxr-xr-x 15 root root 15300 1970-06-28 19:00 dev
lrwxrwxrwx 1 root root 11 1970-06-28 19:00 etc -> /system/etc
-rw-r--r-- 1 root root 53465 1970-01-01 01:00 file_contexts
drwxr-xr-x 4 root root 4096 1970-01-01 01:00 firmware
drwxr-xr-x 3 root root 1024 1970-01-01 01:00 fsg
-rw-r----- 1 root root 2468 1970-01-01 01:00 fstab.qcom
-rwxr-x--- 1 root root 639808 1970-01-01 01:00 init
-rwxr-x--- 1 root root 8581 1970-01-01 01:00 init.cm.rc
-rwxr-x--- 1 root root 983 1970-01-01 01:00 init.environ.rc
-rwxr-x--- 1 root root 3816 1970-01-01 01:00 init.mmi.boot.sh
-rwxr-x--- 1 root root 4562 1970-01-01 01:00 init.mmi.touch.sh
-rwxr-x--- 1 root root 29483 1970-01-01 01:00 init.qcom.rc
-rwxr-x--- 1 root root 4561 1970-01-01 01:00 init.qcom.ssr.sh
-rwxr-x--- 1 root root 11797 1970-01-01 01:00 init.qcom.usb.rc
-rwxr-x--- 1 root root 26983 1970-01-01 01:00 init.rc
-rwxr-x--- 1 root root 1399 1970-01-01 01:00 init.recovery.qcom.rc
-rwxr-x--- 1 root root 319 1970-01-01 01:00 init.superuser.rc
-rwxr-x--- 1 root root 2764 1970-01-01 01:00 init.target.rc
-rwxr-x--- 1 root root 1921 1970-01-01 01:00 init.trace.rc
-rwxr-x--- 1 root root 9283 1970-01-01 01:00 init.usb.configfs.rc
-rwxr-x--- 1 root root 5339 1970-01-01 01:00 init.usb.rc
-rwxr-x--- 1 root root 342 1970-01-01 01:00 init.zygote32.rc
drwxr-xr-x 9 root system 200 1970-06-28 19:00 mnt
drwxr-xr-x 2 root root 0 1970-01-01 01:00 oem
drwxr-xr-x 12 root root 1024 1970-01-01 01:01 pds
drwxrwx--x 4 system system 4096 2016-03-09 12:01 persist
dr-xr-xr-x 220 root root 0 1970-01-01 01:00 proc
-rw-r--r-- 1 root root 6049 1970-01-01 01:00 property_contexts
drwx------ 2 root root 0 2016-03-05 03:29 root
drwxr-x--- 2 root root 0 1970-01-01 01:00 sbin
lrwxrwxrwx 1 root root 21 1970-06-28 19:00 sdcard -> /storage/self/primary
-rw-r--r-- 1 root root 2182 1970-01-01 01:00 seapp_contexts
-rw-r--r-- 1 root root 69 1970-01-01 01:00 selinux_version
-rw-r--r-- 1 root root 258562 1970-01-01 01:00 sepolicy
-rw-r--r-- 1 root root 14812 1970-01-01 01:00 service_contexts
drwxr-xr-x 4 root root 80 2016-03-09 11:57 storage
dr-xr-xr-x 14 root root 0 1970-06-28 19:00 sys
drwxr-xr-x 16 root root 4096 2016-03-08 21:09 system
lrwxrwxrwx 1 root root 16 1970-06-28 19:00 tombstones -> /data/tombstones
-rw-r--r-- 1 root root 12478 1970-01-01 01:00 ueventd.qcom.rc
-rw-r--r-- 1 root root 7606 1970-01-01 01:00 ueventd.rc
lrwxrwxrwx 1 root root 14 1970-06-28 19:00 vendor -> /system/vendor
Your "ls -al" displayed nothing, am I right?
zyzioziom said:
You have strange results here :/
Here is my console:
Code:
Patryks-MacBook-Air:platform-tools patryk$ ./adb devices
List of devices attached
TA9290KDJ1 device
Patryks-MacBook-Air:platform-tools patryk$ ./adb root
adbd is already running as root
Patryks-MacBook-Air:platform-tools patryk$ ./adb shell
[email protected]:/ # ls -al
total 2382
drwxr-xr-x 19 root root 0 1970-06-28 19:00 .
drwxr-xr-x 19 root root 0 1970-06-28 19:00 ..
drwxr-xr-x 44 root root 0 1970-06-28 19:00 acct
drwxrwx--- 6 system cache 4096 2016-03-05 03:28 cache
lrwxrwxrwx 1 root root 13 1970-01-01 01:00 charger -> /sbin/healthd
dr-x------ 2 root root 0 1970-06-28 19:00 config
lrwxrwxrwx 1 root root 17 1970-06-28 19:00 d -> /sys/kernel/debug
drwxrwx--x 35 system system 4096 2016-03-09 18:37 data
-rw-r--r-- 1 root root 555 1970-01-01 01:00 default.prop
drwxr-xr-x 15 root root 15300 1970-06-28 19:00 dev
lrwxrwxrwx 1 root root 11 1970-06-28 19:00 etc -> /system/etc
-rw-r--r-- 1 root root 53465 1970-01-01 01:00 file_contexts
drwxr-xr-x 4 root root 4096 1970-01-01 01:00 firmware
drwxr-xr-x 3 root root 1024 1970-01-01 01:00 fsg
-rw-r----- 1 root root 2468 1970-01-01 01:00 fstab.qcom
-rwxr-x--- 1 root root 639808 1970-01-01 01:00 init
-rwxr-x--- 1 root root 8581 1970-01-01 01:00 init.cm.rc
-rwxr-x--- 1 root root 983 1970-01-01 01:00 init.environ.rc
-rwxr-x--- 1 root root 3816 1970-01-01 01:00 init.mmi.boot.sh
-rwxr-x--- 1 root root 4562 1970-01-01 01:00 init.mmi.touch.sh
-rwxr-x--- 1 root root 29483 1970-01-01 01:00 init.qcom.rc
-rwxr-x--- 1 root root 4561 1970-01-01 01:00 init.qcom.ssr.sh
-rwxr-x--- 1 root root 11797 1970-01-01 01:00 init.qcom.usb.rc
-rwxr-x--- 1 root root 26983 1970-01-01 01:00 init.rc
-rwxr-x--- 1 root root 1399 1970-01-01 01:00 init.recovery.qcom.rc
-rwxr-x--- 1 root root 319 1970-01-01 01:00 init.superuser.rc
-rwxr-x--- 1 root root 2764 1970-01-01 01:00 init.target.rc
-rwxr-x--- 1 root root 1921 1970-01-01 01:00 init.trace.rc
-rwxr-x--- 1 root root 9283 1970-01-01 01:00 init.usb.configfs.rc
-rwxr-x--- 1 root root 5339 1970-01-01 01:00 init.usb.rc
-rwxr-x--- 1 root root 342 1970-01-01 01:00 init.zygote32.rc
drwxr-xr-x 9 root system 200 1970-06-28 19:00 mnt
drwxr-xr-x 2 root root 0 1970-01-01 01:00 oem
drwxr-xr-x 12 root root 1024 1970-01-01 01:01 pds
drwxrwx--x 4 system system 4096 2016-03-09 12:01 persist
dr-xr-xr-x 220 root root 0 1970-01-01 01:00 proc
-rw-r--r-- 1 root root 6049 1970-01-01 01:00 property_contexts
drwx------ 2 root root 0 2016-03-05 03:29 root
drwxr-x--- 2 root root 0 1970-01-01 01:00 sbin
lrwxrwxrwx 1 root root 21 1970-06-28 19:00 sdcard -> /storage/self/primary
-rw-r--r-- 1 root root 2182 1970-01-01 01:00 seapp_contexts
-rw-r--r-- 1 root root 69 1970-01-01 01:00 selinux_version
-rw-r--r-- 1 root root 258562 1970-01-01 01:00 sepolicy
-rw-r--r-- 1 root root 14812 1970-01-01 01:00 service_contexts
drwxr-xr-x 4 root root 80 2016-03-09 11:57 storage
dr-xr-xr-x 14 root root 0 1970-06-28 19:00 sys
drwxr-xr-x 16 root root 4096 2016-03-08 21:09 system
lrwxrwxrwx 1 root root 16 1970-06-28 19:00 tombstones -> /data/tombstones
-rw-r--r-- 1 root root 12478 1970-01-01 01:00 ueventd.qcom.rc
-rw-r--r-- 1 root root 7606 1970-01-01 01:00 ueventd.rc
lrwxrwxrwx 1 root root 14 1970-06-28 19:00 vendor -> /system/vendor
Your "ls -al" displayed nothing, am I right?
Click to expand...
Click to collapse
I found the problem, after writing the adb shell command, the console brings me the following result: ← 7 ← [r ← [999; ← 999H [6n
I just click on INTRO and I recently enabled the line: ← 8root @ falcon: / #
After that, I entered the commands and could properly install the drivers !!!
Problem solved.
Thank you very much for the support, help and above all, patience.
Boss442 said:
Well, many people have problems on the /persist partition, maybe because some bad rom, or maybe because by a mistake you formatted them on a recovery (a bad recovery without forbid partitions).
Before this zip, you have to copy the "WCNSS_qcom_wlan_factory_nv.bin" to /persist manually, but some file managers don't mount well /persist.
But now, only flashing this zip, it will copy the file to /persist and Wifi go back to work.
:highfive:
Download from:
MEDIAFIRE!
MEGA!
Click to expand...
Click to collapse
Worked perfect with flashify and twrp (copy first to a safe location)
Many thanks!
Didn't work for me
I tried flashing the zip, copying manually in CM file explorer and twrp and adb.
The driver is present in /persist but my Mac is stil 02:00:00:00:00
edit:
it's working after doing this:
http://forum.xda-developers.com/showpost.php?p=64771901&postcount=6
My wifi bug is kinda weird.
When I turn on and off my wifi 2-3times,the wifi I connected previously disappear.
Solution is to wipe everything including internal storage to have it working.But still I don't know what's the problem...
I had trouble installing the file no matter how it I flash the wifi did not return to work until I found a solution that apparently functioned normally every time I performed the procedure.
1. Make a full wipe on your smartphone (System / data / cache / dalvik and internal storage) I did the procedure using TWRP 3.0.2-0 on my bike G XT1033
2. Then copy the file persist_repair.zip and some version of CM13 I used (cm 13.0-20160708-NIGHTLY-falcon)
3. After placing the files in the memory of the first flash persist_repair.zip phone and then the CM13 (You can do using the option to install multiple zips the TWRP also the right)
4. Restart your phone and its wifi should resume functioning
Note: I performed the procedure 4 times here and it worked perfectly.
Sorry for the English I used the google translator
NoobByn-tek said:
I had trouble installing the file no matter how it I flash the wifi did not return to work until I found a solution that apparently functioned normally every time I performed the procedure.
1. Make a full wipe on your smartphone (System / data / cache / dalvik and internal storage) I did the procedure using TWRP 3.0.2-0 on my bike G XT1033
2. Then copy the file persist_repair.zip and some version of CM13 I used (cm 13.0-20160708-NIGHTLY-falcon)
3. After placing the files in the memory of the first flash persist_repair.zip phone and then the CM13 (You can do using the option to install multiple zips the TWRP also the right)
4. Restart your phone and its wifi should resume functioning
Note: I performed the procedure 4 times here and it worked perfectly.
Sorry for the English I used the google translator
Click to expand...
Click to collapse
I faced same problem after flashed custom rom; searching high and low, tried many method, and finally, bumped this thread, and specifically NoobByn-tek post. I followed exactly what your have done (but with different version CM13 [cm-13.0-20160820-SNAPSHOT-ZNH5YAO0J1-falcon] because could not find the version you used), and multiple flashed with TWRP 3.0.2. With only one attempt, wifi connection is back.:victory:
Big thank you all.:good::good:
NoobByn-tek said:
I had trouble installing the file no matter how it I flash the wifi did not return to work until I found a solution that apparently functioned normally every time I performed the procedure.
1. Make a full wipe on your smartphone (System / data / cache / dalvik and internal storage) I did the procedure using TWRP 3.0.2-0 on my bike G XT1033
2. Then copy the file persist_repair.zip and some version of CM13 I used (cm 13.0-20160708-NIGHTLY-falcon)
3. After placing the files in the memory of the first flash persist_repair.zip phone and then the CM13 (You can do using the option to install multiple zips the TWRP also the right)
4. Restart your phone and its wifi should resume functioning
Note: I performed the procedure 4 times here and it worked perfectly.
Sorry for the English I used the google translator
Click to expand...
Click to collapse
tried this still no luck...:crying::crying:
Boss442 said:
Well, many people have problems on the /persist partition, maybe because some bad rom, or maybe because by a mistake you formatted them on a recovery (a bad recovery without forbid partitions).
Before this zip, you have to copy the "WCNSS_qcom_wlan_factory_nv.bin" to /persist manually, but some file managers don't mount well /persist.
But now, only flashing this zip, it will copy the file to /persist and Wifi go back to work.
:highfive:
Download from:
MEDIAFIRE!
MEGA!
Click to expand...
Click to collapse
Holy cow!!! After 2 weeks of trying everything under the sun this actually worked!!! I really really appreciate you posting this. Thank you so much!!!
My mac address was 00:00:00:00:02 or whatever it was and nothing would work. I simply flashed this and was back up and running. THANK YOU!
update link please
hey everyone,
i reflashed the stock 5.1.1 image today, but after booting (in recovery it works just fine) my /sdcard is read-only:
Code:
p backup-2015-09-22-1442949879837.kiikb ./kii-kb <
cp: ./kii-kb/backup-2015-09-22-1442949879837.kiikb: Permission denied
1|[email protected]:/sdcard #
here are the outputs of ls -l and mount
Code:
1|[B][email protected]:/sdcard # ls -l[/B]
drwxrwx--- root sdcard_r 2015-09-23 13:14 !ReadyToFlash
drwxrwx--- root sdcard_r 2015-09-23 13:15 Alarms
drwxrwx--x root sdcard_r 2015-09-23 13:16 Android
drwxrwx--- root sdcard_r 2015-09-23 13:25 DCIM
drwxrwx--- root sdcard_r 2015-09-23 13:26 Documents
drwxrwx--- root sdcard_r 2015-09-23 21:08 Download
drwxrwx--- root sdcard_r 2015-09-23 13:28 Files
drwxrwx--- root sdcard_r 2015-09-23 12:46 Movies
drwxrwx--- root sdcard_r 2015-09-23 13:42 Music
drwxrwx--- root sdcard_r 2015-09-23 13:42 Notifications
drwxrwx--- root sdcard_r 2015-09-23 13:46 Pictures
drwxrwx--- root sdcard_r 2015-09-23 12:46 Podcasts
drwxrwx--- root sdcard_r 2015-09-23 13:46 Ringtones
drwxrwx--- root sdcard_r 2015-09-23 13:46 TWRP
drwxrwx--- root sdcard_r 2015-09-23 13:16 backup
-rwxrwx--- root sdcard_r 1626 2015-09-22 21:32 backup-2015-09-22-1442949879837.kiikb
drwxrwx--- root sdcard_r 2015-09-23 13:16 com.facebook.katana
drwxrwx--- root sdcard_r 2015-09-23 13:16 com.facebook.orca
drwxrwx--- root sdcard_r 2015-09-23 13:16 data
drwxrwx--- root sdcard_r 2015-09-23 12:54 flash
drwxrwx--- root sdcard_r 2015-09-23 13:28 kii-kb
drwxrwx--- root sdcard_r 2015-09-23 13:28 media
drwxrwx--- root sdcard_r 2015-09-23 13:46 runtasticPRO
-rwxrwx--- root sdcard_r 54859 2015-09-22 21:32 sms-20150922212654.xml
-rwxrwx--- root sdcard_r 2929 2015-09-22 21:32 sms.xsl
drwxrwx--- root sdcard_r 2015-09-23 13:47 viber
[B][email protected]:/ # ls -l[/B]
drwxr-xr-x root root 2015-09-23 20:56 acct
drwxrwx--- system cache 2015-09-23 20:31 cache
lrwxrwxrwx root root 1970-01-01 01:00 charger -> /sbin/healthd
dr-x------ root root 2015-09-23 20:56 config
lrwxrwxrwx root root 2015-09-23 20:56 d -> /sys/kernel/debug
drwxrwx--x system system 2015-09-23 20:56 data
-rw-r--r-- root root 341 1970-01-01 01:00 default.prop
drwxr-xr-x root root 2015-09-23 20:56 dev
lrwxrwxrwx root root 2015-09-23 20:56 etc -> /system/etc
-rw-r--r-- root root 18941 1970-01-01 01:00 file_contexts
dr-xr-x--- system system 1970-01-01 01:00 firmware
-rw-r----- root root 2625 1970-01-01 01:00 fstab.mako
-rwxr-x--- root root 227652 1970-01-01 01:00 init
-rwxr-x--- root root 944 1970-01-01 01:00 init.environ.rc
-rwxr-x--- root root 15680 1970-01-01 01:00 init.mako.rc
-rwxr-x--- root root 5957 1970-01-01 01:00 init.mako.usb.rc
-rwxr-x--- root root 1945 1970-01-01 01:00 init.performance_profiles.rc
-rwxr-x--- root root 22022 1970-01-01 01:00 init.rc
-rwxr-x--- root root 1927 1970-01-01 01:00 init.trace.rc
-rwxr-x--- root root 3885 1970-01-01 01:00 init.usb.rc
-rwxr-x--- root root 301 1970-01-01 01:00 init.zygote32.rc
drwxrwxr-x root system 2015-09-23 20:56 mnt
drwxrwx--x system system 2015-09-16 10:15 persist
dr-xr-xr-x root root 1970-01-01 01:00 proc
-rw-r--r-- root root 2870 1970-01-01 01:00 property_contexts
drwxr-xr-x root root 1970-01-01 01:00 res
drwx------ root root 2015-04-14 23:26 root
drwxr-x--- root root 2015-09-23 21:09 sbin
lrwxrwxrwx root root 2015-09-23 20:56 sdcard -> /storage/emulated/legacy
-rw-r--r-- root root 826 1970-01-01 01:00 seapp_contexts
-rw-r--r-- root root 50 1970-01-01 01:00 selinux_version
-rw-r--r-- root root 129888 1970-01-01 01:00 sepolicy
-rw-r--r-- root root 129294 1970-01-01 01:00 sepolicy_bk
-rw-r--r-- root root 9854 1970-01-01 01:00 service_contexts
drwxr-x--x root sdcard_r 2015-09-23 20:56 storage
dr-xr-xr-x root root 2015-09-23 20:56 sys
drwxr-xr-x root root 2015-09-23 13:48 system
drwxr-xr-x root root 2015-09-23 20:56 tmp-mksh
-rw-r--r-- root root 2342 1970-01-01 01:00 ueventd.mako.rc
-rw-r--r-- root root 4464 1970-01-01 01:00 ueventd.rc
lrwxrwxrwx root root 2015-09-23 20:56 vendor -> /system/vendor
[B][email protected]:/ # mount[/B]
rootfs / rootfs ro,seclabel,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 rw,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,nodelalloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,context=u:object_r:radio_efs_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
i tried the following:
Code:
adb root
adb remount
#mount -o remount,rw /sdcard
#mount -o remount,rw rootfs /
#chmod 755 /sdcard/*
nothing did the trick, even tried to fix permissions via twrp.
can anyone help me get this solved please without a fw reflash?
Hi,
Unrooted phone fell in the water and failed to power on.
I send it to a lab (not an LG lab). Laboratory cleaned of corrosion but didn't change any part.
The phone works now, but without Baseband and IMEI.
I tried to root/flash (KDZ and TOT)/erase (data/dalvik etc) but nothing works. Obviously I don't have a backup since the phone was unrooted.
Tried with Qualcomm NV tool and EFS professional, but I'm unable to change IMEI (I know it).
Please advise.
I'm attaching some details about the file system and the mounts:
Code:
[email protected]:/ $ mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,noatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,resuid=1000,errors=continue,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/sns /sns ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/drm /persist-lg ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/mpt /mpt ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/cust /cust ext4 ro,seclabel,nosuid,nodev,relatime,noauto_da_alloc,data=ordered 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
Code:
[email protected]:/dev/block/platform/msm_sdcc.1/by-name $ls -l
lrwxrwxrwx root root 1970-01-01 02:00 DDR -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-01 02:00 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-01 02:00 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-01 02:00 cache -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-01 02:00 cust -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-01 02:00 dbi -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-01 02:00 dbibak -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-01 02:00 drm -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-01 02:00 encrypt -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-01 02:00 fota -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-01 02:00 fsc -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-01 02:00 fsg -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-01 02:00 grow -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-01 02:00 laf -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-01 02:00 misc -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-01 02:00 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-01 02:00 modemst1 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-01 02:00 modemst2 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-01 02:00 mpt -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-01 02:00 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-01 02:00 pad1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-01 02:00 pad2 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-01 02:00 persist -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-01 02:00 rct -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-01 02:00 recovery -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-01 02:00 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-01 02:00 rpmbak -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-01 02:00 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-01 02:00 sns -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-01 02:00 spare -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-01 02:00 ssd -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-01 02:00 system -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-01 02:00 tombstones -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-01 02:00 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-01 02:00 tzbak -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-01 02:00 userdata -> /dev/block/mmcblk0p35
Code:
[email protected]:/ $ls -l
drwxr-xr-x root root 1970-01-01 02:00 acct
drwxrwx--- system cache 2015-09-29 19:39 cache
-rwxr-x--- root root 271856 2014-04-25 14:39 charger
dr-x------ root root 1970-01-01 02:00 config
drwxr-xr-x root root 1970-01-01 02:00 cust
lrwxrwxrwx root root 1970-01-01 02:00 d -> /sys/kernel/debug
drwxrwx--x system system 2009-01-02 15:00 data
-rw-r--r-- root root 133 2014-04-25 13:58 default.prop
drwxr-xr-x root root 2009-01-02 13:00 dev
lrwxrwxrwx root root 1970-01-01 02:00 etc -> /system/etc
-rw-r--r-- root root 9471 2014-04-25 14:36 file_contexts
dr-xr-x--- system system 1970-01-01 02:00 firmware
-rw-r----- root root 1944 2014-04-25 14:18 fstab.g2
-rwxr-x--- root root 202260 2014-04-25 14:39 init
-rwxr-x--- root root 1041 2014-04-25 14:18 init.environ.rc
-rwxr-x--- root root 6097 2014-04-25 14:18 init.g2.rc
-rwxr-x--- root root 3184 2014-04-25 14:18 init.g2_product.rc
-rwxr-x--- root root 2344 2014-04-25 14:18 init.galbi-sensor.sh
-rwxr-x--- root root 6847 2014-04-25 14:18 init.galbi.class_core.sh
-rwxr-x--- root root 2518 2014-04-25 14:18 init.galbi.class_main.sh
-rwxr-x--- root root 2687 2014-04-25 14:18 init.galbi.crash.sh
-rwxr-x--- root root 6466 2014-04-25 14:18 init.galbi.early_boot.sh
-rwxr-x--- root root 37883 2014-04-25 14:18 init.galbi.rc
-rwxr-x--- root root 5914 2014-04-25 14:18 init.galbi.sh
-rwxr-x--- root root 3206 2014-04-25 14:18 init.galbi.syspart_fixup.sh
-rwxr-x--- root root 29210 2014-04-25 14:18 init.galbi.usb.rc
-rwxr-x--- root root 6120 2014-04-25 14:18 init.galbi.usb.sh
-rwxr-x--- root root 2063 2014-04-25 14:18 init.lge.cmm.usb.sh
-rwxr-x--- root root 664 2014-04-25 14:18 init.lge.early.rc
-rwxr-x--- root root 3588 2014-04-25 14:18 init.lge.log.rc
-rwxr-x--- root root 2795 2014-04-25 14:18 init.lge.rc
-rwxr-x--- root root 22330 2014-04-25 14:18 init.lge.usb.rc
-rwxr-x--- root root 3029 2014-04-25 14:18 init.lge.usb.sh
-rwxr-x--- root root 21154 2014-04-25 14:19 init.rc
-rwxr-x--- root root 0 2014-04-25 14:18 init.recovery.galbi.rc
-rwxr-x--- root root 9173 2014-04-25 14:18 init.target.rc
-rwxr-x--- root root 1795 2014-04-25 14:18 init.trace.rc
-rwxr-x--- root root 5397 2014-04-25 14:18 init.usb.rc
-rwxr-x--- root root 67824 2014-04-25 14:18 initlogo_fhd.rle
-rw-r--r-- root root 506 2014-04-25 14:19 lgdms.fota.rc
-rw-r--r-- root root 1463 2014-04-25 14:19 lgdms.fota_update.rc
drwxrwxr-x root system 1970-01-01 02:00 mnt
drwxrwxr-x system system 2015-09-30 16:28 mpt
drwxrwx--x system system 2015-09-30 12:50 persist
drwxrwx--x system system 1970-01-02 08:48 persist-lg
lrwxrwxrwx root root 1970-01-01 02:00 pkg -> /storage/sdcard0
-rw-r--r-- root root 1702 2014-04-25 14:18 preload_sl.sh
dr-xr-xr-x root root 1970-01-01 02:00 proc
-rw-r--r-- root root 2324 2014-04-25 14:36 property_contexts
drwxr-xr-x root root 2014-04-25 14:18 res
drwx------ root root 2014-04-25 14:20 root
drwxr-x--- root root 2014-04-25 14:39 sbin
lrwxrwxrwx root root 1970-01-01 02:00 sdcard -> /storage/emulated/legacy
-rw-r--r-- root root 774 2014-04-25 14:36 seapp_contexts
-rw-r--r-- root root 82342 2014-04-25 14:19 sepolicy
-rw-r--r-- root root 1 1970-01-01 02:00 smpl_boot
drwxr-xr-x root root 1970-01-01 02:00 sns
drwxr-x--x system sdcard_r 1970-01-01 02:00 storage
dr-xr-xr-x root root 1970-01-01 02:00 sys
drwxr-xr-x root root 1970-01-01 02:00 system
drwxr-xr-x root root 1970-01-01 02:00 tmp-mksh
lrwxrwxrwx root root 1970-01-01 02:00 tombstones -> /data/tombstones
-rw-r--r-- root root 9098 2014-04-25 14:18 ueventd.g2.rc
-rw-r--r-- root root 4083 2014-04-25 14:18 ueventd.rc
lrwxrwxrwx root root 1970-01-01 02:00 vendor -> /system/vendor