No Systemless root on g900f 6.0.1 - SuperSU

Seems there is a problem with rooting the leaked mm firmware for the g900f (Galaxy S5)
Systemless root does not work. Patching boot image and creating su.img works fine as far as i can see, but somehow mounting su.img seems to fail at boot.
strangely enough /su seems not even to be created.
according to my adblog losetup seems to fail somehow too.
Logs are attached.

Ok, installed su in system to see if i cand find the problem.
Apparently i can't execute losetup right, as i get a permission denied error.
Code:
[email protected]:/ # ls -l /dev/block/loop*
brw------- root root 7, 0 2014-09-04 01:14 loop0
brw------- root root 7, 1 2014-09-04 01:14 loop1
brw------- root root 7, 2 2014-09-04 01:14 loop2
brw------- root root 7, 3 2014-09-04 01:14 loop3
brw------- root root 7, 4 2014-09-04 01:14 loop4
brw------- root root 7, 5 2014-09-04 01:14 loop5
brw------- root root 7, 6 2014-09-04 01:14 loop6
brw------- root root 7, 7 2014-09-04 01:14 loop7
[email protected]:/ # losetup -f
losetup: -f: Permission denied
1|[email protected]:/ # losetup /dev/block/loop0 /data/su.img
losetup: /dev/block/loop0: Permission denied
That shouldn't be the case right?
Anyone with an idea to deal with this?
Creating a new loop device doesn't work either.

Force SElinux into permissive or just disable it

I have also installed the leaked Marshmellow (Android 6.0.1) firmware on my Samsung Galaxy S5 (G900F).
Root rights would be great! Do we have to wait for the latest android 6.0 root files from Chainfire?
Is there another way to get root rights? A description of this would be great.

I have this problem.
i don`t have root access
BETA-SuperSU-v2.68-20160228150503 doesnt work

So i guess still no change? No solution guys?:crying:

And with CF-Auto-Root-klte-kltexx-smg900f.tar.md5 + Odin ?

po1725 said:
And with CF-Auto-Root-klte-kltexx-smg900f.tar.md5 + Odin ?
Click to expand...
Click to collapse
Everything solved since supersu beta 2.69 i think, which was released about 2 months ago.

eeausli said:
Ok, installed su in system to see if i cand find the problem.
Apparently i can't execute losetup right, as i get a permission denied error.
Code:
[email protected]:/ # ls -l /dev/block/loop*
brw------- root root 7, 0 2014-09-04 01:14 loop0
brw------- root root 7, 1 2014-09-04 01:14 loop1
brw------- root root 7, 2 2014-09-04 01:14 loop2
brw------- root root 7, 3 2014-09-04 01:14 loop3
brw------- root root 7, 4 2014-09-04 01:14 loop4
brw------- root root 7, 5 2014-09-04 01:14 loop5
brw------- root root 7, 6 2014-09-04 01:14 loop6
brw------- root root 7, 7 2014-09-04 01:14 loop7
[email protected]:/ # losetup -f
losetup: -f: Permission denied
1|[email protected]:/ # losetup /dev/block/loop0 /data/su.img
losetup: /dev/block/loop0: Permission denied
That shouldn't be the case right?
Anyone with an idea to deal with this?
Creating a new loop device doesn't work either.
Click to expand...
Click to collapse
1|[email protected]:/ # losetup /dev/block/loop0 /data/su.img
losetup: /dev/block/loop0: Permission denied[/code]
instructions su.img Permission denied
you must be rooted your phone and try again!

Hay。 said:
you must be rooted your phone and try again!
Click to expand...
Click to collapse
You're a real genius. Look at the topic, read the post and think about what you've written.

I confirm works like a charm with superSu 2.74

Related

[Q] Captivate internal memory corruption, help?

i bought a captivate yesterday solely to sell, it works and is not hard bricked. it would not start when i got it, it always got stuck at the at&t world phone screen and then would shut off but it does get into download and recovery mode. i have tried odin for eclair and gingerbread, neither of them worked. i tried to repartition and odin stopped and failed. when i try to mount the internal sd it says it is not found. i really need to fix it and would love any help i can get. anyone know how to save this phone?
This is what happens when I restore from odin
{
"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"
}
Sent from my Cappy of Power
What Odin are you using? What package? Btw that image is broken.
I used odin3 1.3. Ill reupload that pic in a bit, I'm not around the phone at the moment. Every time I've tried to repartition from Odin it says it has a write error about halfway though the filesystem part of the restore.
Sent from my Cappy of Power
Why don't you use a newer version of ODIN? (doubt its that but worth mentioning) What PIT file? and package are you using?
What is the newest version? I used the 512 pit and the jh2 package
Sent from my Cappy of Power
Well then I don't know. Apart from asking if you are running ODIN in admin when you repartition I have no clue. Hope someone else can help.
edit: Well I have Odin 1.83. I doubt its that but worth a try.
Did you click repartition???
Sent from my SGH-I897 using xda premium
Yeah usually I have no problems handling this kind of thing myself but this one is giving me a lot of trouble :/ and yes, I clicked repartition but I'm gonna try it again with a newer version of Odin and see if it helps at all
Sent from my Cappy of Power
Still didn't work :/
Sent from my Cappy of Power
shopealope said:
Still didn't work :/
Sent from my Cappy of Power
Click to expand...
Click to collapse
Which specific firmware versions have u tried (kk4, kb1, etc.) ?? And were they one click odins or just regular odin ??
Edit: Here is the latest Odin that I have and the .pit file for the Gingerbread i897 Firmwares. It is not the 512 that was used in Froyo days. It is Kepler_odin_new_part_JE3_S1JE4.pit
I zipped both up together to upload... View attachment 806756
4-2ndtwin said:
Which specific firmware versions have u tried (kk4, kb1, etc.) ?? And were they one click odins or just regular odin ??
Edit: Here is the latest Odin that I have and the .pit file for the Gingerbread i897 Firmwares. It is not the 512 that was used in Froyo days. It is Kepler_odin_new_part_JE3_S1JE4.pit
I zipped both up together to upload... View attachment 806756
Click to expand...
Click to collapse
Awesome ill give it a shot in just a bit. I've been trying to flash jh2 and also tried stock kf1 with one click. Ill try this out though and hopefully it'll work. It just refuses to mount internal storage.
Sent from my Cappy of Power
Have you tried heimdall?
Sent from my SGH-I897 using XDA App
I haven't tried heimdall, would you recommend it?
Sent from my Cappy of Power
Still nothing working. I tried to reformat the /dev/block/mmcblk0p2 partition with adb but it says it doesn't exist. Yet that's what the problem is when I restore, it can't mount that partition.
Sent from my Cappy of Power
In adb shell, if you navigate to /dev/block and do the ls -l command, what does it spit out? (Warning: results may be a long list)
jmtheiss said:
In adb shell, if you navigate to /dev/block and do the ls -l command, what does it spit out? (Warning: results may be a long list)
Click to expand...
Click to collapse
I'm at work at the moment but as soon as I'm home ill check it out and get back to you
Sent from my Cappy of Power
Maybe JH2 package that you used to flash doesn't contain the "dbdata.rfs"? Try downloading this one http://forum.xda-developers.com/showthread.php?t=1266172, it's a KB2 Package. Check Re-partition, use the pit file and let it flash.
Nick0703 said:
Maybe JH2 package that you used to flash doesn't contain the "dbdata.rfs"? Try downloading this one http://forum.xda-developers.com/showthread.php?t=1266172, it's a KB2 Package. Check Re-partition, use the pit file and let it flash.
Click to expand...
Click to collapse
I'm pretty sure it did have dbdata.rfs, ill double check that though. This is the most difficulty I've ever had with a phone and I work on phones for people all the time.
Sent from my Cappy of Power
jmtheiss said:
In adb shell, if you navigate to /dev/block and do the ls -l command, what does it spit out? (Warning: results may be a long list)
Click to expand...
Click to collapse
alright here is what i got from adb when i ran that command:
C:\Program Files (x86)\Android\android-sdk\tools>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
/ # cd /dev/block
cd /dev/block
/dev/block # ls -l
ls -l
brw------- 1 root root 137, 0 Dec 7 05:12 bml0!c
brw------- 1 root root 137, 1 Dec 7 05:12 bml1
brw------- 1 root root 137, 10 Dec 7 05:12 bml10
brw------- 1 root root 137, 11 Dec 7 05:12 bml11
brw------- 1 root root 137, 12 Dec 7 05:12 bml12
brw------- 1 root root 137, 2 Dec 7 05:12 bml2
brw------- 1 root root 137, 3 Dec 7 05:12 bml3
brw------- 1 root root 137, 4 Dec 7 05:12 bml4
brw------- 1 root root 137, 5 Dec 7 05:12 bml5
brw------- 1 root root 137, 6 Dec 7 05:12 bml6
brw------- 1 root root 137, 7 Dec 7 05:12 bml7
brw------- 1 root root 137, 8 Dec 7 05:12 bml8
brw------- 1 root root 137, 9 Dec 7 05:12 bml9
brw------- 1 root root 7, 0 Dec 7 05:12 loop0
brw------- 1 root root 7, 1 Dec 7 05:12 loop1
brw------- 1 root root 7, 2 Dec 7 05:12 loop2
brw------- 1 root root 7, 3 Dec 7 05:12 loop3
brw------- 1 root root 7, 4 Dec 7 05:12 loop4
brw------- 1 root root 7, 5 Dec 7 05:12 loop5
brw------- 1 root root 7, 6 Dec 7 05:12 loop6
brw------- 1 root root 7, 7 Dec 7 05:12 loop7
brw------- 1 root root 1, 0 Dec 7 05:12 ram0
brw------- 1 root root 1, 1 Dec 7 05:12 ram1
brw------- 1 root root 1, 10 Dec 7 05:12 ram10
brw------- 1 root root 1, 11 Dec 7 05:12 ram11
brw------- 1 root root 1, 12 Dec 7 05:12 ram12
brw------- 1 root root 1, 13 Dec 7 05:12 ram13
brw------- 1 root root 1, 14 Dec 7 05:12 ram14
brw------- 1 root root 1, 15 Dec 7 05:12 ram15
brw------- 1 root root 1, 2 Dec 7 05:12 ram2
brw------- 1 root root 1, 3 Dec 7 05:12 ram3
brw------- 1 root root 1, 4 Dec 7 05:12 ram4
brw------- 1 root root 1, 5 Dec 7 05:12 ram5
brw------- 1 root root 1, 6 Dec 7 05:12 ram6
brw------- 1 root root 1, 7 Dec 7 05:12 ram7
brw------- 1 root root 1, 8 Dec 7 05:12 ram8
brw------- 1 root root 1, 9 Dec 7 05:12 ram9
brw------- 1 root root 138, 1 Dec 7 05:12 stl1
brw------- 1 root root 138, 10 Dec 7 05:12 stl10
brw------- 1 root root 138, 11 Dec 7 05:12 stl11
brw------- 1 root root 138, 12 Dec 7 05:12 stl12
brw------- 1 root root 138, 2 Dec 7 05:12 stl2
brw------- 1 root root 138, 3 Dec 7 05:12 stl3
brw------- 1 root root 138, 4 Dec 7 05:12 stl4
brw------- 1 root root 138, 5 Dec 7 05:12 stl5
brw------- 1 root root 138, 6 Dec 7 05:12 stl6
brw------- 1 root root 138, 7 Dec 7 05:12 stl7
brw------- 1 root root 138, 8 Dec 7 05:12 stl8
brw------- 1 root root 138, 9 Dec 7 05:12 stl9
brw------- 1 root root 139, 0 Dec 7 05:12 tfsr0!c
brw------- 1 root root 139, 1 Dec 7 05:12 tfsr1
brw------- 1 root root 139, 10 Dec 7 05:12 tfsr10
brw------- 1 root root 139, 11 Dec 7 05:12 tfsr11
brw------- 1 root root 139, 12 Dec 7 05:12 tfsr12
brw------- 1 root root 139, 2 Dec 7 05:12 tfsr2
brw------- 1 root root 139, 3 Dec 7 05:12 tfsr3
brw------- 1 root root 139, 4 Dec 7 05:12 tfsr4
brw------- 1 root root 139, 5 Dec 7 05:12 tfsr5
brw------- 1 root root 139, 6 Dec 7 05:12 tfsr6
brw------- 1 root root 139, 7 Dec 7 05:12 tfsr7
brw------- 1 root root 139, 8 Dec 7 05:12 tfsr8
brw------- 1 root root 139, 9 Dec 7 05:12 tfsr9
/dev/block #

[Q] Invalid Magic (TouchPadBuntu)

Hi,
I have upgraded my moboot to 3.0.5 and upgraded the Cyanogenmod to CM9. Also, i have decided to install TouchPadBuntu to test it. Followed the instructions with some modifications, and everything went fine, but when i try to boot on it via moboot, it gives the error:
Loading '/boot/uImage.TouchPadBuntu'... OK
Checking uImage... Invalid Magic
BOOT FAILED!
Also, ClockRecovery doesn't works too, it returns some numbers (hex codes) on the boot screen.
Someone can give some light?
I'm dealing with same problem, but with Arch Linux.
I think the problem is in /boot free space...
Can you list your files in /boot and your free space in there?
ls -l /boot
df -h /boot
Hi, i have attached the errors... one is TouchPadBuntu error, and the other is Cyanogenmod error that is appearing sometimes yes, sometimes no...
http://img19.imageshack.us/img19/5138/imagem0000m.jpg
http://img828.imageshack.us/img828/4153/imagem0001.jpg
Also, here is my /boot
Code:
[email protected]:/# ls -l /boot
-rw-r--r-- 1 root root 1430215 Jul 30 2011 System.map-2.6.35-palm-tenderloin
drwxr-xr-x 2 root root 4096 Oct 14 02:59 bin
-rw-r--r-- 1 root root 490764 Jul 30 2011 boot-genesis.tar.gz
-rw-r--r-- 1 root root 119371 Jul 30 2011 boot-images.tar.gz
-rw-r--r-- 1 root root 115392 Jul 30 2011 boot.bin
-rw-r--r-- 1 root root 75277 Jul 30 2011 config-2.6.35-palm-tenderloin
drwxr-xr-x 2 root root 4096 Oct 14 02:59 dev
drwxr-xr-x 3 root root 4096 Oct 14 02:59 etc
-rwxr-xr-x 1 root root 1131 Jul 30 2011 genesis-update.xml
-rwxr-xr-x 1 root root 2224 Jul 30 2011 image-update.xml
drwxr-xr-x 2 root root 4096 Oct 14 02:59 lib
drwx------ 2 root root 16384 Oct 14 02:56 lost+found
-rw-r--r-- 1 root root 11 Oct 14 03:51 moboot.default
-rw-r--r-- 1 luna luna 0 Feb 9 01:57 moboot.next
-rw-rw-rw- 1 root root 30313 Feb 8 00:58 moboot.splash.CyanogenMod.tga
-rw-r--r-- 1 luna 10000 14046 Sep 8 2001 moboot.splash.webOS.tga
-rw-r--r-- 1 root root 4 Feb 8 01:51 moboot.verbose.TouchPadBuntu
drwxr-xr-x 2 root root 4096 Oct 14 02:59 proc
drwxr-xr-x 2 root root 4096 Oct 14 02:59 realroot
drwxr-xr-x 2 root root 4096 Oct 14 02:59 sbin
drwxr-xr-x 2 root root 4096 Oct 14 02:59 sys
lrwxrwxrwx 1 root root 13 Feb 8 01:51 uImage -> uImage.moboot
-rw-r--r-- 1 root root 3333228 Jul 30 2011 uImage-2.6.35-palm-tenderloin
-rw-r--r-- 1 root root 5006686 Feb 8 00:57 uImage.ClockworkMod
-rw-r--r-- 1 root root 4136681 Feb 8 00:58 uImage.CyanogenMod
-rw-r--r-- 1 root root 1106 Feb 8 02:53 uImage.TouchPadBuntu
-rw-r--r-- 1 root root 64508 Feb 8 01:50 uImage.moboot
lrwxrwxrwx 1 root root 29 Oct 14 02:58 uImage.webOS -> uImage-2.6.35-palm-tenderloin
-rw-r--r-- 1 root root 84 Jul 30 2011 updatefs-info
drwxr-xr-x 5 root root 4096 Oct 14 02:59 usr
[email protected]:/# df -h /boot
Filesystem Size Used Available Use% Mounted on
/dev/root 31.0M 22.1M 8.9M 71% /boot
Hi folks,
I have corrected my problem downloading uImage.TouchPadUbuntu again via CURL direclty to /boot. To do this i have to use mount -O rw,remount /boot and execute the curl command here.
After this, i rebooted the touchpad and now have ubuntu on it. But using touchscreen as mouse is sucking a lot, and response of my touch on virtual keyboard too... but fine to test!
I also solved my problem, I think the problem was pretty like yours!
My solution post.

XT890 unbrick (new firmware)

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$)

No CSC folder in stock MM?

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.

No logcat output

I'm porting Ubuntu Touch on an y991 (Elephone Vowney Lite).
I managed to boot the system and run its apps. Now I need to debug RIL, wireles, camera etc., but I cannot get any logcat output.
I tried both /system/bin/logcat both /android/system/bin/logcat from an adb root shell. It just returns to prompt. No error, no log. Logs exist:
Code:
ls -l /dev/log*
srw-rw-rw- 1 root root 0 Jan 1 01:00 /dev/log
crw-rw-rw- 1 root root 10, 59 Jan 1 01:00 /dev/log_events
crw-rw-rw- 1 root root 10, 60 Jan 1 01:00 /dev/log_main
crw-rw-rw- 1 root root 10, 58 Jan 1 01:00 /dev/log_radio
crw-rw-rw- 1 root root 10, 57 Jan 1 01:00 /dev/log_system
I was about to suggest that you ask the ubport's guys ..... but mayyybe you know them already https://forums.ubports.com/user/4javier

Categories

Resources