So, in a nutshell, Moto decided to update the Wi-Fi firmware on the feb 22 leaked .sbf and broke it.
Attached are the 2 firmware files from stock ROM to fix it (there are 3 in total, but only 2 changed)
Turn off Wi-Fi, replace the same files in /system/etc/firmware/wifi using adb or Root Explorer, turn Wi-Fi back on, et voila, working 5GHz.
Working hard at more hacks
so this is for better wifi? and if i have the adeo rom will this work?
The Atrix features a dual-band Wi-Fi radio capable of operating at both 2.4GHz and 5GHz. 5GHz is typically used in high-interference areas like my city which provides free Wi-Fi access city-wide. I can't get any range at all on 2.4GHz.
The leaked February 22 .sbf introduced a new Wi-Fi firmware which (probably not purposefully) disables 5GHz support. I've supplied the stock Atrix Wi-Fi firmware in which 5GHz support works correctly.
This won't help you at all if you don't have a router that supports 5GHz But you never know when you might get an opportunity to hop on a network that does, and your Atrix won't see it running the Feb 22 firmware.
optimaljam said:
so this is for better wifi? and if i have the adeo rom will this work?
Click to expand...
Click to collapse
No leaked SBF kills 5ghz wifi. So you need to push the old files back on to get 5ghz back.
It's the stock wifi firmware. The leaked SBF had a problem with 5Ghz wifi.
Another great hack... thanks much!
SBF??? sorry noob here kinda. XD
optimaljam said:
SBF??? sorry noob here kinda. XD
Click to expand...
Click to collapse
.sbf: Summation Briefcase File
File that allows you to restore phone to out of box condition if something goes wrong i.e. bricked phone.
Sent from my MB860 using XDA App
Mustang302LX said:
.sbf: Summation Briefcase File
File that allows you to restore phone to out of box condition if something goes wrong i.e. bricked phone.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
+100000000000
Sent from my MB860 using XDA App
Da_G said:
So, in a nutshell, Moto decided to update the Wi-Fi firmware on the feb 22 leaked .sbf and broke it.
Attached are the 2 firmware files from stock ROM to fix it (there are 3 in total, but only 2 changed)
Turn off Wi-Fi, replace the same files in /system/etc/firmware/wifi using adb or Root Explorer, turn Wi-Fi back on, et voila, working 5GHz.
Working hard at more hacks
Click to expand...
Click to collapse
Hey what permissions should be on the files in the /system/etc/firmware/wifi directory?
cuz i only have this:
-rw-r--r-- root root 264070 2011-02-22 18:38 sdio-ag-cdc-full1
1n-minioctl-roml-pno-wme-aoe-pktfilter-keepalive.bin
if it might be connected to my problem once i put in the workign sim, which would be rather unlogical but still ...?
@crnkoj:
I don't think it's the problem, but here are the proper permissions as follows:
Code:
cd /system/etc/firmware/wifi
# ls -l -a
ls -l -a
-rw-r--r-- root root 1747 2011-02-22 09:38 nvram.txt
lrwxrwxrwx root root 2011-02-22 10:12 pds -> /pds/wifi
-rw-r--r-- root root 263942 2011-03-15 23:10 sdio-ag-cdc-full11n-minioctl-roml-pno-wme-aoe-pktfilter-keepalive.b
in
-rw-r--r-- root root 249307 2011-03-15 23:09 sdio-g-cdc-roml-reclaim-wme-apsta-idsup-idauth.bin
-rw-r--r-- root root 262067 2011-02-22 09:38 sdio-ag-cdc-11n-mfgtest-roml-seqcmds.bin
# stat *
File: "nvram.txt"
Size: 1747 Blocks: 4 IO Block: 1024 regular file
Device: b30ch/45836d Inode: 482 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2011-03-15 23:09:49.000000000
Modify: 2011-02-22 09:38:18.000000000
Change: 2011-02-22 10:14:01.000000000
File: "pds -> /pds/wifi"
Size: 9 Blocks: 0 IO Block: 1024 symbolic link
Device: b30ch/45836d Inode: 1010 Links: 1
Access: (0777/lrwxrwxrwx) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2011-02-22 10:12:30.000000000
Modify: 2011-02-22 10:12:30.000000000
Change: 2011-02-22 10:14:01.000000000
File: "sdio-ag-cdc-11n-mfgtest-roml-seqcmds.bin"
Size: 262067 Blocks: 514 IO Block: 1024 regular file
Device: b30ch/45836d Inode: 243 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2011-02-22 09:38:18.000000000
Modify: 2011-02-22 09:38:18.000000000
Change: 2011-02-22 10:14:01.000000000
File: "sdio-ag-cdc-full11n-minioctl-roml-pno-wme-aoe-pktfilter-keepalive.bin"
Size: 263942 Blocks: 518 IO Block: 1024 regular file
Device: b30ch/45836d Inode: 1011 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2011-03-15 23:10:51.000000000
Modify: 2011-03-15 23:10:40.000000000
Change: 2011-03-15 23:10:40.000000000
File: "sdio-g-cdc-roml-reclaim-wme-apsta-idsup-idauth.bin"
Size: 249307 Blocks: 490 IO Block: 1024 regular file
Device: b30ch/45836d Inode: 1251 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2011-02-22 09:38:18.000000000
Modify: 2011-03-15 23:09:18.000000000
Change: 2011-03-15 23:09:18.000000000
aha, thanks, it seems to be the same on mine. hope you got the pds dump on the mail
thk you for share~
I made a thread in the General subforum a few days ago about my phone not being able to detect my 5GHz network. Hopefully this will fix it.
EDIT: I copied the files over, but my phone still doesn't detect my 5GHz n-network.
So how do we know if we updated it to this? and is this the cause on why my phone's connectivity to wifi sometimes disappear even though my router is right next to me? im running adeo v0.1
... I'm confused. I'm on 1.5.2 (after a soft brick, woo!) and I can connect to my 5 GHz network just fine...?
5 GHz, 40MHz band, WPA2/AES/802.1x
Sogarth said:
... I'm confused. I'm on 1.5.2 (after a soft brick, woo!) and I can connect to my 5 GHz network just fine...?
5 GHz, 40MHz band, WPA2/AES/802.1x
Click to expand...
Click to collapse
Is your network n-ONLY, or mixed?
EDIT: nvm stupid question.
Thanks to the OP... copied the two files over with root explorer and now have 5ghz wireless...
Is this also broken on 1.2.6?
5Ghz isn't working on my Atrix with 1.2.6 SBF flash. I haven't tried this fix, but I am surprised that it isn't working on the stock SBF...
Edit: Reflashed SBF and when it said manually power up phone I restarted (twice!) the phone until it said complete (even though the phone booted automatically). Now it is working.
Related
After upgrading CM9 Alpha 0.6 to Alpha 1, the boot animation does not appear anymore. I tried to replaced the bootanimation.zip file with a fullscreen one, but it still does not show up.
I also did a 'fix permission' from ClockWorkMod, but no change.
Everything else works fine. I will upgrade to Alpha 2 this weekend, but I don't think it will make a difference.
I'm assuming you can still enter CM9. If that's the case the boot animation disable function has probably been checked.
Samsung Captivate CM9 - Glitch Kernel | HP TouchPad CM9 - Bricked Kernel
iamsamsamiam said:
I'm assuming you can still enter CM9. If that's the case the boot animation disable function has probably been checked.
Samsung Captivate CM9 - Glitch Kernel | HP TouchPad CM9 - Bricked Kernel
Click to expand...
Click to collapse
Where can I uncheck it?
dtle said:
After upgrading CM9 Alpha 0.6 to Alpha 1, the boot animation does not appear anymore. I tried to replaced the bootanimation.zip file with a fullscreen one, but it still does not show up.
I also did a 'fix permission' from ClockWorkMod, but no change.
Everything else works fine. I will upgrade to Alpha 2 this weekend, but I don't think it will make a difference.
Click to expand...
Click to collapse
two things that can cause this.
1. wrong folder
if the bootanimation.zip is not flashable, then you have to copy it either to /data/local OR /system/media
change the permissions to rw-r--r--. If the system/media is not doing anything try the other.
2. if you did turn bootanimation off in previous built then it's possible it stayed turned off when you switched to newer alpha. there is a fix (this is shamelessly copied from somebody else on Rootzwiki)
maybe you still have the setting on ("persist.sys.nobootanimation"):
[email protected]:/ # ls -la /data/property
ls -la /data/property
-rw------- root root 8 2011-12-01 15:35 persist.cf3d.nightmode
-rw------- root root 0 2012-01-26 09:23 persist.service.adb.enable
-rw------- root root 1 2011-10-28 20:46 persist.sys.alarm-attn
-rw------- root root 2 2012-01-01 11:52 persist.sys.country
-rw------- root root 2 2012-01-01 11:52 persist.sys.language
-rw------- root root 0 2012-01-01 11:52 persist.sys.localevar
-rw------- root root 1 2012-02-18 14:47 persist.sys.nobootanimation <---------- this one
-rw------- root root 1 2011-10-28 20:46 persist.sys.notif-attn
-rw------- root root 1 2012-02-19 15:09 persist.sys.profiler_ms
-rw------- root root 1 2011-10-28 20:46 persist.sys.ring-attn
-rw------- root root 0 2011-11-27 11:47 persist.sys.themeId
-rw------- root root 0 2011-11-27 11:47 persist.sys.themePackageName
-rw------- root root 13 2011-10-26 17:26 persist.sys.timezone
-rw------- root root 5 2012-01-19 14:16 persist.sys.ui.hw
-rw------- root root 7 2012-02-20 18:37 persist.sys.usb.config
-rw------- root root 1 2012-02-12 19:50 persist.sys.use_dithering
-rw------- root root 3 2011-11-05 14:15 persist.sys.vm.heapsize
[email protected]:/ #
Just delete the file and restart
[email protected]:/ # rm /data/property/persist.sys.nobootanimation
rm /data/property/persist.sys.nobootanimation
[email protected]:/ # su
Thanks to derausgewanderte
Works like a charm, got back my boot animation with your trick !
Simsphil
Any other ideas on how you can fix this issue? I am running Alpha 2 and have tried to install this Bios Boot both manually (with ES File Explorer) and flashing it: http://forum.xda-developers.com/showpost.php?p=21560233&postcount=1. The first time I tried to flash it, it failed. I think that may have messed something up.
I still get the black screen where the boot image used to be. I don't see the persist.sys.nobootanimation file when I go to /data/property.
Disregard post.....
Many of XT890s with "Service required Code corrupt" are bricked and mine as well.
I've found out that there's a ancestor model - XT788 in China. And now we've all parts to reflash Medfield: ifwi (UEFI BIOS), osdnx (bootloader), osimage (kernel with fastboot). There's the last part to do, the fwdnx should be changed, but it has checksum and it should be recalculated. How to calculate dnx checksum?
Maybe you know somebody who knows!
He knows but I can't reach him.
http://www.linkedin.com/pub/tapan-shah/10/59a/39
View attachment dnx.zip
The algorithm is unknown still.
Could somebody make a dump of the first 500 Mb of the eMMC, please? (XT890)
Code:
su
busybox dd if=/dev/block/mmcblk0 of=/sdcard/dd.bin bs=500M count=1
After some time (10 minutes in the worst case), You'll find dd.bin file in /sdcard folder.
It operation will copy some specific to only your's device data. I'll not use it and will delete it after my analysis.
Sorry, my I is bricked, or I would.
So, by reading the "--help" message, "xfstk" is capable of flashing more then two files. I assume more then two files have to match/are the same/depend on each other to bootstrap Android. Why aren't more files being flashed? In my bricking experience, I tried flashing the ifwi and dnx files from the 4.0.4 that I was leaving, the 4.1.2 zip didn't have them in it so I tried others from a stock 4.1.2 rom and the original versions packaged with the xfstk. So which ones go with Mattlgroff's cwm Jelly Bean zip? What other files need to be flashed to un-corrupt the code? I don't see names that line up here.
The flashing utility works, we just need the right files to be flashed.
Code:
Z:\brick\unbrick>xfstk-dldr-solo.exe --help
XFSTK Downloader Solo 1.1.0a
Copyright (c) 2011 Intel Corporation
Command Line Options:
-h [ --help ] Print usage message
--fwdnx arg (=BLANK.bin) File path for the FW DNX module
--fwimage arg (=BLANK.bin) File path for the FW Image module
--osdnx arg (=BLANK.bin) File path for the OS DNX module
--osimage arg (=BLANK.bin) File path for the OS image
--miscdnx arg File path for miscellaneous DNX module
--gpflags arg (=0x80000000) Optional argument. 32 Bit Hex Value of the
GPFlags.
--transfer arg (=USB) Optional argument. Determines how the image will
be transferred.
--idrq arg (=0) Optional argument. Indicates whether IDRQ is
used. 1 means idrq is used, 0 means idrq is not
used.
-v [ --verbose ] Optional argument. Display debug information. 1
means show debug information, 0 means hide debug
information.
gilbertiddi0, things aren't so simple.
Motorola doesn't provide osdnx. I'm almost sure that it have never been developed for our model (XT890).
I still have no full dump of the first 500M.
Can you do that on an unrooted machine? If you can describe how to do that I will try. I am familiar with "dd" - just assumed you are needing the help of usb-debugging and busybox.
My phone doesn't have /dev/block/mmcblk0
gilbertiddi0 said:
Can you do that on an unrooted machine? If you can describe how to do that I will try. I am familiar with "dd" - just assumed you are needing the help of usb-debugging and busybox.
Click to expand...
Click to collapse
You could check if you have a read permission by:
Code:
cd /dev/block
ls -l | grep mmc
itsmeinarizona, could you execute those commands and reply, please?
Dark2150 said:
You could check if you have a read permission by:
Code:
cd /dev/block
ls -l | grep mmc
itsmeinarizona, could you execute those commands and reply, please?
Click to expand...
Click to collapse
Code:
[email protected]:/dev/block $ ls -l | grep mmc
lrwxrwxrwx root root 2013-10-03 03:51 boot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-10-03 03:51 bos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-10-03 03:51 bosbackup -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-10-03 03:51 cache -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2013-10-03 03:51 cdrom -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2013-10-03 03:51 cid -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-10-03 03:51 devtree -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2013-10-03 03:51 devtreeBackup -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2013-10-03 03:51 logo -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-10-03 03:51 misc -> /dev/block/mmcblk0p13
brw------- root root 179, 0 2013-10-03 03:51 mmcblk0
brw------- root root 179, 1 2013-10-03 03:51 mmcblk0p1
brw------- root root 179, 10 2013-10-03 03:51 mmcblk0p10
brw------- root root 179, 11 2013-10-03 03:51 mmcblk0p11
brw------- root root 259, 0 2013-10-03 03:51 mmcblk0p12
brw------- root root 259, 1 2013-10-03 03:51 mmcblk0p13
brw------- root root 259, 2 2013-10-03 03:51 mmcblk0p14
brw------- root root 259, 3 2013-10-03 03:51 mmcblk0p15
brw------- root root 259, 4 2013-10-03 03:51 mmcblk0p16
brw------- root root 259, 5 2013-10-03 03:51 mmcblk0p17
brw------- root root 179, 2 2013-10-03 03:51 mmcblk0p2
brw------- root root 179, 3 2013-10-03 03:51 mmcblk0p3
brw------- root root 179, 4 2013-10-03 03:51 mmcblk0p4
brw------- root root 179, 5 2013-10-03 03:51 mmcblk0p5
brw------- root root 179, 6 2013-10-03 03:51 mmcblk0p6
brw-rw---- root mot_tcmd 179, 7 2013-10-03 03:51 mmcblk0p7
brw------- root root 179, 8 2013-10-03 03:51 mmcblk0p8
brw------- root root 179, 9 2013-10-03 03:51 mmcblk0p9
lrwxrwxrwx root root 2013-10-03 03:51 panic -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2013-10-03 03:51 pds -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2013-10-03 03:51 recovery -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2013-10-03 03:51 sp -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-10-03 03:51 system -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2013-10-03 03:51 ulogo -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-10-03 03:51 userdata -> /dev/block/mmcblk0p17
[email protected]:/dev/block $
[\code][COLOR="Silver"]
[SIZE=1]---------- Post added at 04:19 AM ---------- Previous post was at 04:04 AM ----------[/SIZE]
[/COLOR][QUOTE="Dark2150, post: 46131662, member: 421987"]You could check if you have a read permission by:
[CODE]
cd /dev/block
ls -l | grep mmc
itsmeinarizona, could you execute those commands and reply, please?[/QUOTE]
Code:
|[email protected]:/dev/block $ dd if=/dev/block/mmcblk0 of=/sdcard/dd.bin bs=500M count=1 <
/dev/block/mmcblk0: cannot open for read: Permission denied
1|[email protected]:/dev/block $
I went ahead and ran that command. This is a friends 890. As I hardbricked mine by opening the bootloader I am unwilling to unlock theirs
gilbertiddi0, Thank you.
As you see there is a mmcblk0. But only root has rights to read it.
Yours headset bricked with "Service required Code corrupt"? All others cases are debrickable.
Dark2150 said:
Yours headset bricked with "Service required Code corrupt"? All others cases are debrickable.
Click to expand...
Click to collapse
Yes. when I first downgraded, it worked for one boot but the second time it did not.
gilbertiddi0 said:
Yes. when I first downgraded, it worked for one boot but the second time it did not.
Click to expand...
Click to collapse
By the time of the first boot the headset was connected to PC, and by the second reboot it wasn't, right?
Dark2150 said:
By the time of the first boot the headset was connected to PC, and by the second reboot it wasn't, right?
Click to expand...
Click to collapse
Now that you mention it, yes in fact that is what happened. I never thought of it in quite those terms. The second time it got locked on the "bootloader unlocked" warning so I forced it off and turned it back on, I had always equated THAT as the important event: somehow it got stuck, in my haste I corrupted something by making it reload. Since it obviously couldn't get back to the "bootloader unlocked" screen even. I searched for quite awhile for that logo screen thinking that replacing that would allow it to cycle normally. Of course that isn't something you get with a new firmware like you're saying ...
gilbertiddi0 said:
Of course that isn't something you get with a new firmware like you're saying ...
Click to expand...
Click to collapse
The picture of unlocked bootloader it's a part of the firmware, but your phone doesn't boot a firmware.
The dump of mmcblk0 is still needed! Someone?
Dark2150 said:
The dump of mmcblk0 is still needed! Someone?
Click to expand...
Click to collapse
I have the dump. The "pm" link doesn't include a file transfer, how do I get it to you?
I got another 890. It had Jelly Bean on it - it was a pain rooting (I used Matt's method of rooting - unlocked bootloader, flashed insecured boot - reinstalled boot) but I had to do it with "su-bin-3.1-x86" instead of the su file that came with it. Ohh, and replaced the "boot" that came with the unit. I knew you needed this dump and I am still hoping to fix that other unit.
gilbertiddi0 said:
I have the dump. The "pm" link doesn't include a file transfer, how do I get it to you?
I got another 890. It had Jelly Bean on it - it was a pain rooting (I used Matt's method of rooting - unlocked bootloader, flashed insecured boot - reinstalled boot) but I had to do it with "su-bin-3.1-x86" instead of the su file that came with it. Ohh, and replaced the "boot" that came with the unit. I knew you needed this dump and I am still hoping to fix that other unit.
Click to expand...
Click to collapse
And there's a hope to fix it still. Unfortunately Motorola have made it as hard as possible.
The fix process is the same for whole Z2xxx family and it suits to other devices. We're working with XT890 and Lenovo K900 now. But if anybody has a device on Atom SoC platform (Orange SanDiego, Lenovo K800, Lava Xolo X900 e.t.c) and wants to join - welcome.
Dark2150 said:
And there's a hope to fix it still. Unfortunately Motorola have made it as hard as possible.
The fix process is the same for whole Z2xxx family and it suits to other devices. We're working with XT890 and Lenovo K900 now. But if anybody has a device on Atom SoC platform (Orange SanDiego, Lenovo K800, Lava Xolo X900 e.t.c) and wants to join - welcome.
Click to expand...
Click to collapse
HI!
Thanks guys for the help! i have a razr i and it is hard bricked, and there isn't nothing to do (the battery is over and the phone doesn't start) an option is change the motherboard with another and maybe the phone can start ? (sorry for my bad english but i am italian)
peter971215 said:
HI!
Thanks guys for the help! i have a razr i and it is hard bricked, and there isn't nothing to do (the battery is over and the phone doesn't start) an option is change the motherboard with another and maybe the phone can start ? (sorry for my bad english but i am italian)
Click to expand...
Click to collapse
If you have no "Service required code corrupt" message - it have chance to be reflashed with standard tool.
And yes - if you'll change mainboard it will solve the problem, because it's like change the whole phone.
Dark2150 said:
If you have no "Service required code corrupt" message - it have chance to be reflashed with standard tool.
And yes - if you'll change mainboard it will solve the problem, because it's like change the whole phone.
Click to expand...
Click to collapse
i had hard bricked my phone why i downgraded (not from jelly bean to ics , but i had downgraded with a fastboot ics from jelly bean and it was all ok, and when I flash with rsd a firmware ics the phone after 1 reboot gave me the "service required code corrupt" screen with the green led, i tried to revive the phone with the unbrick.zip but nothing outcome from the phone.. sometimes when i change the dnx and ifwi file the phone reboot with a dark screen but nothing..
peter971215 said:
i had hard bricked my phone why i downgraded (not from jelly bean to ics , but i had downgraded with a fastboot ics from jelly bean and it was all ok, and when I flash with rsd a firmware ics the phone after 1 reboot gave me the "service required code corrupt" screen with the green led, i tried to revive the phone with the unbrick.zip but nothing outcome from the phone.. sometimes when i change the dnx and ifwi file the phone reboot with a dark screen but nothing..
Click to expand...
Click to collapse
The same problem there. You definitely could fix it with a new mainboard.
Dark2150 said:
The same problem there. You definitely could fix it with a new mainboard.
Click to expand...
Click to collapse
Yes!! i had just take this option, but i need a razr i used (the mainboard new is 200$)
Hello,
I recently unlocked my bootloader and went to install a custom rom with Clockwork Recovery. It got stuck on the HTC boot screen (using an M7), and it would not move. I hard booted the device, and it corrupted my data.
Now, when going into CWM, the device reboots. I have tried reflashing CWM to no avail, so I then tried flashing TWRP. TWRP cannot mount any partition other than system. Problematically, I cannot get adb to recognize my device when in recovery (on multiple computers) but can get fastboot to detect it.
I cannot get a new image onto my phone via usb to fix it, and I cannot use the following guide (edit, cannot post links yet) to fix my corrupted data as a result. Also, I cannot get the device to show up as mountable storage in windows (I have yet to try Linux) to transfer files to it.
What are my options here?
Update:
I was able to update my "unknown" driver to the HTC diver in windows, and now can see my phone with adb devices.
So, I tried the data corruption fix by loading mkfs.ext4 to it and running :
/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/mmcblk0p37
this completed, but now I still cant mount /data/ for some reason.
this is what I get:
ls -l
drwxr-xr-x 2 root root 0 May 10 20:12 cache
drwxr-xr-x 2 root root 0 Jan 1 1970 data
-rw-r--r-- 1 root root 6586 Jan 1 1970 default.prop
drwxr-xr-x 12 root root 3440 May 10 20:12 dev
drwxr-xr-x 2 root root 0 May 10 20:12 etc
-rwxr-x--- 1 root root 105268 Jan 1 1970 init
-rwxr-x--- 1 root root 1670 Jan 1 1970 init.rc
drwxr-xr-x 3 root root 0 Jan 1 1970 license
dr-xr-xr-x 157 root root 0 Jan 1 1970 proc
drwxr-xr-x 5 root root 0 Jan 1 1970 res
drwx------ 2 root root 0 Aug 15 2013 root
drwxr-x--- 2 root root 0 Jan 1 1970 sbin
drwxr-xr-x 2 root root 0 May 10 20:12 sdcard
drwxr-xr-x 2 root root 0 Jan 1 1970 supersu
dr-xr-xr-x 24 root root 0 May 10 20:12 sys
drwxr-xr-x 3 root root 0 Jan 1 1970 system
drwxrwxr-x 2 root shell 0 May 10 20:17 tmp
-rw-r--r-- 1 root root 272 Jan 1 1970 ueventd.goldfish.rc
-rw-r--r-- 1 root root 5075 Jan 1 1970 ueventd.rc
drwxrwxrwx 2 root root 0 May 10 20:12 usb-otg
~ # ←[6nmount data
mount data
mount: mounting /data on ext4 failed: No such file or directory
~ # ←[6nmount /data
mount /data
mount: mounting /data on ext4 failed: No such file or directory
~ # ←[6nexit
exit
Now what?
Hey Wulf,
Sorry I'm still at work but this happened to me once as well. You wiped the OS completely from the phone and somehow corrupted the recovery.
I resolved it by relocking the bootloader and flashing a stock RUU. After it booted stock I unlocked the bootloader again reflashed the custom rom.
wulfsburg said:
What are my options here?
Click to expand...
Click to collapse
my bad, useless contribution / preaching.
nkk71 said:
re-EDIT: you start by reading (a little or a lot)... by reading you will learn... by learning you will acquire knowledge... and by knowledge you will be hopefully to get a lot farther than where you are now.
Click to expand...
Click to collapse
By posting useless crap like this you become a douche bag, when you become a douche bag people disregard your opinion, when people disregard your opinion you become useless to a forum community, when you become useless to a forum community you get eaten by a bear. Don't get eaten by a bear, stop posting useless crap
nicowagner said:
By posting useless crap like this you become a douche bag, when you become a douche bag people disregard your opinion, when people disregard your opinion you become useless to a forum community, when you become useless to a forum community you get eaten by a bear. Don't get eaten by a bear, stop posting useless crap
Click to expand...
Click to collapse
Have removed my post.
Thanks for pointing it out.
In other ROMs I've edited an XML file in /system/csc to make some changes to the keyboard -- specifically, to display alternate symbols when you press-hold a key. I flashed stock MM tonight and noticed that this folder no longer exists.
I checked the Maximum OvrDriVE MM ROM and it does have this folder with the appropriate file. So what happened to the CSC stuff in stock?
SteveRiley said:
In other ROMs I've edited an XML file in /system/csc to make some changes to the keyboard -- specifically, to display alternate symbols when you press-hold a key. I flashed stock MM tonight and noticed that this folder no longer exists.
I checked the Maximum OvrDriVE MM ROM and it does have this folder with the appropriate file. So what happened to the CSC stuff in stock?
Click to expand...
Click to collapse
which stock firmware you are using?
pvsgh said:
which stock firmware you are using?
Click to expand...
Click to collapse
The one DeeXii posted a couple weeks ago: N910TUVS2EPG2_N910TTMB2EPG2_TMB
http://forum.xda-developers.com/note-4-tmobile/development/stock-n910t-n910tuvu2epe3-6-0-1-t3407018
SteveRiley said:
The one DeeXii posted a couple weeks ago: N910TUVS2EPG2_N910TTMB2EPG2_TMB
http://forum.xda-developers.com/note-4-tmobile/development/stock-n910t-n910tuvu2epe3-6-0-1-t3407018
Click to expand...
Click to collapse
Those are the stock ODIN flashable files. Once you flash it via ODIN you will see CSC folder on your phone under /system directory.
pvsgh said:
Those are the stock ODIN flashable files. Once you flash it via ODIN you will see CSC folder on your phone under /system directory.
Click to expand...
Click to collapse
No CSC folder here.
Code:
[email protected]:/ # [B]ls -al /system[/B]
drwxr-xr-x root root 2016-08-11 23:53 app
drwxr-xr-x root shell 2008-12-31 07:00 bin
-rw-r--r-- root root 8080 2008-12-31 07:00 build.prop
drwxr-xr-x root root 2008-12-31 07:00 cameradata
drwxr-xr-x root root 2016-07-07 07:17 container
drwxr-xr-x root root 2016-08-12 01:00 etc
drwxr-xr-x root root 2008-12-31 07:00 fonts
drwxr-xr-x root root 2016-07-07 07:17 framework
-rw-r--r-- root root 10800 2008-12-31 07:00 kern_sec_info
drwxr-xr-x root root 2016-08-11 23:36 lib
drwx------ root root 1969-12-31 16:00 lost+found
drwxr-xr-x root root 2008-12-31 07:00 media
drwxr-xr-x root root 2016-07-07 07:16 preloadedmdm
drwxr-xr-x root root 2016-08-11 23:52 priv-app
-rw-r--r-- root root 4876860 2008-12-31 07:00 recovery-from-boot.bak
drwxr-xr-x root root 2008-12-31 07:00 saiv
-rw-r--r-- root root 417 2016-07-07 07:36 tima_measurement_info
drwxr-xr-x root root 2008-12-31 07:00 tts
drwxr-xr-x root root 2008-12-31 07:00 usr
drwxr-xr-x root shell 2008-12-31 07:00 vendor
drwxr-xr-x root root 2008-12-31 07:00 voicebargeindata
drwxr-xr-x root root 2008-12-31 07:00 wakeupdata
drwxr-xr-x root shell 2008-12-31 07:00 xbin
And a little bit of searching on /system and /data doesn't reveal anything much:
Code:
[email protected]:/ # [B]find /system -iname '*csc*'[/B]
/system/fonts/CarroisGothicSC-Regular.ttf
/system/lib/libcontrolcsc.so
/system/lib/libsccore_csc.so
/system/priv-app/CSC
/system/priv-app/CSC/CSC.apk
/system/priv-app/CSC/oat/arm/CSC.odex.xz
[email protected]:/ # f[B]ind /data -iname '*csc*'[/B]
/data/data/com.samsung.sec.android.application.csc
/data/data/com.google.android.gms/files/AppDataSearch/main/cur/ds.cscoring
/data/system/cscversion.txt
/data/dalvik-cache/profiles/com.samsung.sec.android.application.csc
/data/dalvik-cache/arm/[email protected]@[email protected]@classes.dex
And this zero-byte file seems odd:
Code:
[email protected]:/ # [B]ls -al /data/system/cscversion.txt[/B]
-rw------- system system 0 2016-08-12 20:03 cscversion.txt
I've flashed the build a couple times now, same results. My procedure:
1. Ensure SuperSU zip is on external SD card
2. Boot TWRP recovery (currently 3.0.2 installed)
3. Wipe every partition except external SD
4. Boot the phone into download mode
5. Odin (3.0.9) the ROM to the phone
6. Odin TWRP back to the phone
7. Boot TWRP recovery
8. Flash SuperSU zip
9. Reboot and let settle for 15 minutes
SteveRiley said:
No CSC folder here.
Code:
[email protected]:/ # [B]ls -al /system[/B]
drwxr-xr-x root root 2016-08-11 23:53 app
drwxr-xr-x root shell 2008-12-31 07:00 bin
-rw-r--r-- root root 8080 2008-12-31 07:00 build.prop
drwxr-xr-x root root 2008-12-31 07:00 cameradata
drwxr-xr-x root root 2016-07-07 07:17 container
drwxr-xr-x root root 2016-08-12 01:00 etc
drwxr-xr-x root root 2008-12-31 07:00 fonts
drwxr-xr-x root root 2016-07-07 07:17 framework
-rw-r--r-- root root 10800 2008-12-31 07:00 kern_sec_info
drwxr-xr-x root root 2016-08-11 23:36 lib
drwx------ root root 1969-12-31 16:00 lost+found
drwxr-xr-x root root 2008-12-31 07:00 media
drwxr-xr-x root root 2016-07-07 07:16 preloadedmdm
drwxr-xr-x root root 2016-08-11 23:52 priv-app
-rw-r--r-- root root 4876860 2008-12-31 07:00 recovery-from-boot.bak
drwxr-xr-x root root 2008-12-31 07:00 saiv
-rw-r--r-- root root 417 2016-07-07 07:36 tima_measurement_info
drwxr-xr-x root root 2008-12-31 07:00 tts
drwxr-xr-x root root 2008-12-31 07:00 usr
drwxr-xr-x root shell 2008-12-31 07:00 vendor
drwxr-xr-x root root 2008-12-31 07:00 voicebargeindata
drwxr-xr-x root root 2008-12-31 07:00 wakeupdata
drwxr-xr-x root shell 2008-12-31 07:00 xbin
And a little bit of searching on /system and /data doesn't reveal anything much:
Code:
[email protected]:/ # [B]find /system -iname '*csc*'[/B]
/system/fonts/CarroisGothicSC-Regular.ttf
/system/lib/libcontrolcsc.so
/system/lib/libsccore_csc.so
/system/priv-app/CSC
/system/priv-app/CSC/CSC.apk
/system/priv-app/CSC/oat/arm/CSC.odex.xz
[email protected]:/ # f[B]ind /data -iname '*csc*'[/B]
/data/data/com.samsung.sec.android.application.csc
/data/data/com.google.android.gms/files/AppDataSearch/main/cur/ds.cscoring
/data/system/cscversion.txt
/data/dalvik-cache/profiles/com.samsung.sec.android.application.csc
/data/dalvik-cache/arm/[email protected]@[email protected]@classes.dex
And this zero-byte file seems odd:
Code:
[email protected]:/ # [B]ls -al /data/system/cscversion.txt[/B]
-rw------- system system 0 2016-08-12 20:03 cscversion.txt
I've flashed the build a couple times now, same results. My procedure:
1. Ensure SuperSU zip is on external SD card
2. Boot TWRP recovery (currently 3.0.2 installed)
3. Wipe every partition except external SD
4. Boot the phone into download mode
5. Odin (3.0.9) the ROM to the phone
6. Odin TWRP back to the phone
7. Boot TWRP recovery
8. Flash SuperSU zip
9. Reboot and let settle for 15 minutes
Click to expand...
Click to collapse
Don't know if it would make any difference but you should be using Odin 3.11.1 with this latest EPG2 firmware. CSC related files reside in cache.img.ext4 , so it is possible that that particular file is not being flashed in your case.
pvsgh said:
Don't know if it would make any difference but you should be using Odin 3.11.1 with this latest EPG2 firmware. CSC related files reside in cache.img.ext4 , so it is possible that that particular file is not being flashed in your case.
Click to expand...
Click to collapse
Hm, you might very well have discovered the cause.
Examining the cache.img.ext4 file on my PC:
Code:
[email protected] ~/junk $ [B]simg2img cache.img.ext4 cache.raw[/B]
[email protected] ~/junk $ [B]sudo mount -t ext4 -o loop cache.raw /mnt[/B]
[email protected] ~/junk $ [B]ls -al /mnt[/B]
total 28
drwxr-xr-x 4 root root 4096 Dec 31 1969 .
drwxr-xr-x 1 root root 122 Dec 24 2015 ..
drwx------ 2 root root 4096 Dec 31 1969 lost+found
drwxrwx--- 2 steve 2001 4096 Jul 7 07:36 recovery
[email protected] ~/junk $ [B]ls -al /mnt/recovery/[/B]
total 82720
drwxrwx--- 2 steve 2001 4096 Jul 7 07:36 .
drwxr-xr-x 4 root root 4096 Dec 31 1969 ..
-rw-r--r-- 1 root root 78 Jul 7 07:36 command
-rw-r--r-- 1 root root 84691365 Jul 7 07:36 sec_csc.zip
[email protected] ~/junk $ [B]unzip -l /mnt/recovery/sec_csc.zip[/B]
Archive: /mnt/recovery/sec_csc.zip
signed by SignApk
Length Date Time Name
--------- ---------- ----- ----
{... many files, including several for system/csc ...}
--------- -------
104784820 113 files
I'm surprised the phone even works!
Hm, experiencing flash write failures. First time was about 15% finished. Second time seems about 95% finished.
Third flash completed. Before rebooting, I flashed TWRP. Then I booted TWRP and installed SuperSU. Booted normally and received the dreaded ddi: mmc_read failed message. Crap. Tried another flashing round, which also completed, and let it boot immediately. The Samsung recovery started (which I have never actually seen before) and ran through an installation cycle of something. After that, the phone booted and once again shows ddi:mmc_read failed. Is this thing kaput now?
----------
EDIT: I power cycled the phone and now it appears to be doing a normal first boot -- I'm staring at the T-Mobile splash and the status light is flickering blue/cyan. Wow!
SteveRiley said:
Third flash completed. Before rebooting, I flashed TWRP. Then I booted TWRP and installed SuperSU. Booted normally and received the dreaded ddi: mmc_read failed message. Crap. Tried another flashing round, which also completed, and let it boot immediately. The Samsung recovery started (which I have never actually seen before) and ran through an installation cycle of something. After that, the phone booted and once again shows ddi:mmc_read failed. Is this thing kaput now?
----------
EDIT: I power cycled the phone and now it appears to be doing a normal first boot -- I'm staring at the T-Mobile splash and the status light is flickering blue/cyan. Wow!
Click to expand...
Click to collapse
Did you use the latest version of ODIN now? Also if the phone looks stuck on T-Mobile logo for longer than 30 mins, then remove the battery from the phone and try to boot again.
pvsgh said:
Did you use the latest version of ODIN now? Also if the phone looks stuck on T-Mobile logo for longer than 30 mins, then remove the battery from the phone and try to boot again.
Click to expand...
Click to collapse
Yep, Odin 3.11.1 worked, but like I wrote before, it took three attempts. Weird.
BTW, not everyone agrees that the version of Odin was the actual problem:
http://forum.xda-developers.com/not...ow-updates-issues-t3415914/page2#post68173468
pvsgh said:
Don't know if it would make any difference but you should be using Odin 3.11.1 with this latest EPG2 firmware. CSC related files reside in cache.img.ext4 , so it is possible that that particular file is not being flashed in your case.
Click to expand...
Click to collapse
Worked like a charm. Now I have wifi calling and secondary characters on my keyboard again!
You'll also notice that Bluetooth tethering is gone. T-Mobile likes to disable that for some reason. I imagine that buried in one of the CSC files is a line you could delete to restore Bluetooth tethering.
Upstream Repository
Official Kernel Documentation (zRAM)
Swap Performance (ArchWIki)
This project targets mainly gamers, heavy multitaskers and those with low RAM systems.
VR25 said:
Upstream Repository
Official Kernel Documentation (zRAM)
Swap Performance (ArchWIki)
This project targets mainly gamers, heavy multitaskers and those with low RAM systems.
Click to expand...
Click to collapse
i dont understand what memory limit does
VR25 said:
Upstream Repository
Official Kernel Documentation (zRAM)
Swap Performance (ArchWIki)
This project targets mainly gamers, heavy multitaskers and those with low RAM systems.
Click to expand...
Click to collapse
and how do i change setting , i typed zsm but i dont understand
Guan Yu said:
i dont understand what memory limit does
Click to expand...
Click to collapse
Memory limit caps the amount of memory zRAM can use. This is not something users must deeply understand to use this software. There's a config file: /data/adb/vr25/zram-swap-manager/config.txt (Android) or /etc/zram-swap-manager.conf (GNU/Linux). While the config can be edited with one of many programs, the usual way is with zsm -c [editor], editor being optional (falling back to vim | vi | nano).
sm -v
v2022.1.9 (202201090)
sm -e
Memory Estimates
Without zRAM: 2734 MB
With zRAM: 3727 MB
Net Gain: 993 MB (36%)
sm -f
sm -n
Loops into this.....
cat: can't open '/sys/block/zram0/comp_algorithm': No such file or directory
mkswap: /dev/block/zram0: No such file or directory
(i) Trying alternative: /system/bin/mkswap...
mkswap: can't open '/dev/block/zram0': No such file or directory
(i) Trying alternative: /system/xbin/mkswap...
mkswap: /dev/block/zram0: No such file or directory
(i) Trying alternative: /vendor/bin/mkswap...
mkswap: /dev/block/zram0: No such file or directory
(i) Trying alternative: /system/bin/mkswap...
mkswap: can't open '/dev/block/zram0': No such file or directory
sieger007 said:
sm -v
v2022.1.9 (202201090)
sm -e
Memory Estimates
Without zRAM: 2734 MB
With zRAM: 3727 MB
Net Gain: 993 MB (36%)
sm -f
sm -n
Loops into this.....
cat: can't open '/sys/block/zram0/comp_algorithm': No such file or directory
mkswap: /dev/block/zram0: No such file or directory
(i) Trying alternative: /system/bin/mkswap...
mkswap: can't open '/dev/block/zram0': No such file or directory
(i) Trying alternative: /system/xbin/mkswap...
mkswap: /dev/block/zram0: No such file or directory
(i) Trying alternative: /vendor/bin/mkswap...
mkswap: /dev/block/zram0: No such file or directory
(i) Trying alternative: /system/bin/mkswap...
mkswap: can't open '/dev/block/zram0': No such file or directory
Click to expand...
Click to collapse
What's the output of ls /dev/zram*?
Bash:
ls /dev/zram*
ls: /dev/zram*: No such file or directory
and here is the mod
Bash:
ls -al /data/adb/modules/zram-swap-manager
total 19
drwxr-xr-x 3 root root 3488 2022-03-28 06:04 .
drwxr-xr-x 14 root root 3488 2022-04-01 18:39 ..
-rwxr-xr-x 1 root root 767 2022-03-28 06:04 busybox.sh
-rw-r--r-- 1 root root 103 2022-03-28 06:04 module.prop
-rwxr-xr-x 1 root root 161 2022-03-28 06:04 service.sh
drwxr-xr-x 3 root root 3488 2022-03-28 06:04 system
-rwxrwxrwx 1 root root 697 2022-03-28 06:04 uninstall.sh
-rwxrwxrwx 1 root root 5803 2022-03-28 06:04 zram-swap-manager.sh
Also while you are at it - if its ok with you wanted to ask you about fbind - is there anyway you figured out to modify selinux policy so it can run successfully on enforced mobs. I asked that in relevant thread. wondered if it updated. thx!
sieger007 said:
Bash:
ls /dev/zram*
ls: /dev/zram*: No such file or directory
and here is the mod
Bash:
ls -al /data/adb/modules/zram-swap-manager
total 19
drwxr-xr-x 3 root root 3488 2022-03-28 06:04 .
drwxr-xr-x 14 root root 3488 2022-04-01 18:39 ..
-rwxr-xr-x 1 root root 767 2022-03-28 06:04 busybox.sh
-rw-r--r-- 1 root root 103 2022-03-28 06:04 module.prop
-rwxr-xr-x 1 root root 161 2022-03-28 06:04 service.sh
drwxr-xr-x 3 root root 3488 2022-03-28 06:04 system
-rwxrwxrwx 1 root root 697 2022-03-28 06:04 uninstall.sh
-rwxrwxrwx 1 root root 5803 2022-03-28 06:04 zram-swap-manager.sh
Click to expand...
Click to collapse
It almost seems like your kernel lacks [proper] zRAM support.
Share /dev/.vr25/zram-swap-manager/service.log (recreated on reboot).
Also while you are at it - if its ok with you wanted to ask you about fbind - is there anyway you figured out to modify selinux policy so it can run successfully on enforced mobs. I asked that in relevant thread. wondered if it updated. thx!
Answered in the dedicated thread.
VR25 said:
It almost seems like your kernel lacks [proper] zRAM support.
Share /dev/.vr25/zram-swap-manager/service.log (recreated on reboot).
Also while you are at it - if its ok with you wanted to ask you about fbind - is there anyway you figured out to modify selinux policy so it can run successfully on enforced mobs. I asked that in relevant thread. wondered if it updated. thx!
Answered in the dedicated thread.
Click to expand...
Click to collapse
@sieger007, your kernel does not seem to support zRAM.
Which device is this?
Does /sys/class/zram-control/ exist?
Hi, can you please release a guide for how to do this? My goal is to keep (certain) apps running in the background. If I can't choose specific apps, I'd like to keep ALL apps running in the background unless I actively close them. It's pretty ridiculous not being able to use more than 1-2 apps at a time. I run adguard, accubattery, JamesDSP constantly. I also listen to music sometimes while also browsing or playing a light game. Browsing even requires the keyboard open sometimes to type. And don't even think about summoning the Google assistant or any voice typing because instead of opening as an overlay, it closes the background app and switches to GA as an active foreground app.
I'm using a Pixel 3 with PixelDust12 and sure, it only has 4 gigs of ram. But even stock behavior isn't this bad. And I have the highest amount of zram I can set through EX kernel manager. (yes my kernel supports it. I have the directory mentioned above with two files inside it)
But the more I mess with zram settings the worse it seems to get. At one point yesterday it got so bad I wasn't able to use even 1 foreground app without it crashing on me. Sometimes even pulling up multi-tasking is enough to make it all crash. I even switched to Pure browser because it has far lower foreground ram usage than Brave (more than half) and it was still not enough. I'm now in Via browser and it seems to be ok. But without anything running in the background. Even system keeps crashing on me. Dev ops shows 0 background processes and around 10% average ram usage. It's crazy. EX shows that zram keeps getting disabled.
Hasn't been updated in a year... Does this still work ?