Related
The link below is a dump of the /dev/block/mmcblk0p13 partition.
It is the entire ubuntu "distribution". However, it is not an OS per say. It is just an environment compiled and setup to run on the "android linux". Everything just runs from a second X session started on top of the native Android Arm linux redirected to the HDMI display port.
The partition has about 800MB in size and is mounted under /osh once the system boots.
Something worth to note, is that the webtop X session does not consume any RAM or system resource at all till when the phone enters RM_SM_DOCKED mode. While the phone is on RM_SM_MOBILE mode, that X session is complete shutdown.
http://www.usk.bz/android/ubuntu.img.bz2
If you use a linux or MacOS, just uncompress the file with bzip2 -d , then mount like this:
mount -t ext3 -o loop,ro ubuntu.img /mnt/loop
Of course, make sure the directory /mnt/loop exists.
Also, some directories, like /etc will not be available or will look like bugged/corrupted, it's because they are actually just a "link" to the /etc from the root partition. I can provide a dump for that partition as well, if that will help with any development. Let me know.
Have fun and post us if you find anything special.
A bit further: There's a chroot involved! And the adas account password is randomly set!
... Buuuuuuuuut, Motorola was smart and got rid of telnetd, etc in this production script...
See /usr/local/sbin/webtop-product.sh.
It's the script that makes the "production" webtop - and removes the fun stuff via dpkg in the process.
But here's a hint - if you can run an app within Webtop, get it to run /usr/bin/.lxterminal - they HID the terminal app.
EDIT: Hm. /usr/local/share/motorola/fireboxmake/ has some interesting readmes... on what .sh does what in /usr/local/sbin.
EDIT2: Check out what's in the OSH_tools.tgz. Motorola left a bootloader BIN in there along with some interesting flashing scripts for both Webtop and the Android side... and some interesting config files in nvflash...
Also, can I get the root filesystem for /etc/?
I have not downloaded the archive yet but did a search for RM_SM_DOCKED on google and came up with a hit elsewhere.
I can't post the link to this directly due to it being one of my first posts. It's only one of 3/4 hits on google.
I am guessing it is in the archive you posted.
Code:
#
#
on property:dev.bootcomplete=1
#
setprop ro.webtop.boot 1
#
start loadpreinstalls
#
#
on property:ro.webtop.boot=1
#
exec /system/bin/logwrapper /ubuntu.sh
#
#
on property:sys.SystemMode=RM_SM_DOCKED
#
exec /osh/etc/init.d/startX.sh
#
uskr said:
The link below is a dump of the /dev/block/mmcblk0p13 partition.
It is the entire ubuntu "distribution". However, it is not an OS per say. It is just an environment compiled and setup to run on the "android linux". Everything just runs from a second X session started on top of the native Android Arm linux redirected to the HDMI display port.
The partition has about 800MB in size and is mounted under /osh once the system boots.
Something worth to note, is that the webtop X session does not consume any RAM or system resource at all till when the phone enters RM_SM_DOCKED mode. While the phone is on RM_SM_MOBILE mode, that X session is complete shutdown.
http://www.usk.bz/android/ubuntu.img.bz2
If you use a linux or MacOS, just uncompress the file with bzip2 -d , then mount like this:
mount -t ext3 -o loop,ro ubuntu.img /mnt/loop
Of course, make sure the directory /mnt/loop exists.
Also, some directories, like /etc will not be available or will look like bugged/corrupted, it's because they are actually just a "link" to the /etc from the root partition. I can provide a dump for that partition as well, if that will help with any development. Let me know.
Have fun and post us if you find anything special.
Click to expand...
Click to collapse
uskr,
Excellent work & post, have a Thanks.
It's a shame that the webtop will probably flop (and I sure as heck won't buy one for the price they're asking). Here's to hoping a dockless hack comes up.
uskr,
Great post, Thanks
labsONE said:
Also, can I get the root filesystem for /etc/?
Click to expand...
Click to collapse
http://www.usk.bz/android/etc.tar.bz2
You will notice some files are just links to /system/etc. You can find the /system dump on another thread on this forum. If you cant, let me know and I will get a link here.
Can someone take a good look at the contents of:
/usr/local/share/motorola/fireboxmake/OSH_tools.tgz
There's lots of interesting stuff in there & I am completely unfamiliar with tegra and Motorola cruft.
uskr said:
The link below is a dump of the /dev/block/mmcblk0p13 partition.
It is the entire ubuntu "distribution". However, it is not an OS per say. It is just an environment compiled and setup to run on the "android linux". Everything just runs from a second X session started on top of the native Android Arm linux redirected to the HDMI display port.
The partition has about 800MB in size and is mounted under /osh once the system boots.
Something worth to note, is that the webtop X session does not consume any RAM or system resource at all till when the phone enters RM_SM_DOCKED mode. While the phone is on RM_SM_MOBILE mode, that X session is complete shutdown.
If you use a linux or MacOS, just uncompress the file with bzip2 -d , then mount like this:
mount -t ext3 -o loop,ro ubuntu.img /mnt/loop
Of course, make sure the directory /mnt/loop exists.
Also, some directories, like /etc will not be available or will look like bugged/corrupted, it's because they are actually just a "link" to the /etc from the root partition. I can provide a dump for that partition as well, if that will help with any development. Let me know.
Have fun and post us if you find anything special.
Click to expand...
Click to collapse
uskr, appreciate if you could also get us the root partition dump
Actually, sorry for not posting this before. But right after I posted the first dump I noticed that pretty much everything on the root partition is just a link to /osh, like you can see here:
Code:
lrwxrwxrwx root root 2011-02-22 23:54 lib -> /osh/lib
lrwxrwxrwx root root 2011-02-22 23:54 etc -> /osh/etc
lrwxrwxrwx root root 2011-02-22 23:54 thumb2 -> /osh/thumb2
lrwxrwxrwx root root 2011-02-22 23:54 srv -> /osh/srv
lrwxrwxrwx root root 2011-02-22 23:54 usr -> /osh/usr
lrwxrwxrwx root root 2011-02-22 23:54 media -> /osh/media
lrwxrwxrwx root root 2011-02-22 23:54 upath.sh -> /osh/upath.sh
lrwxrwxrwx root root 2011-02-22 23:54 boot -> /osh/boot
lrwxrwxrwx root root 2011-02-22 23:54 sbin -> /osh/sbin
lrwxrwxrwx root root 2011-02-22 23:54 var -> /osh/var
lrwxrwxrwx root root 2011-02-22 23:54 root -> /osh/root
lrwxrwxrwx root root 2011-02-22 23:54 apath.sh -> /osh/apath.sh
lrwxrwxrwx root root 2011-02-22 23:54 bin -> /osh/bin
lrwxrwxrwx root root 2011-02-22 23:54 opt -> /osh/opt
lrwxrwxrwx root root 2011-02-22 23:54 selinux -> /osh/selinux
lrwxrwxrwx root root 2011-02-22 23:54 ubuntu.sh -> /osh/ubuntu.sh
lrwxrwxrwx root root 2011-02-22 23:54 lost+found -> /osh/lost+found
lrwxrwxrwx root root 2011-02-22 23:54 home -> /data/home
dr-x------ root root 2011-02-22 23:54 config
drwxrwx--- system misc 2011-02-22 23:54 misc
drwxrwx--- system cache 2011-02-23 00:58 cache
drwxr-xr-x root root 2011-01-30 05:54 pds
lrwxrwxrwx root root 2011-02-22 23:54 sdcard-ext -> /mnt/sdcard-ext
lrwxrwxrwx root root 2011-02-22 23:54 sdcard -> /mnt/sdcard
drwxr-xr-x root root 2011-02-22 23:54 acct
lrwxrwxrwx root root 2011-02-22 23:54 tmp -> /data/tmp
drwxr-xr-x root root 2010-12-22 17:39 preinstall
drwxr-xr-x root root 2011-01-20 21:49 osh
drwxrwxr-x root system 2011-02-22 23:54 mnt
lrwxrwxrwx root root 2011-02-22 23:54 d -> /sys/kernel/debug
drwxr-xr-x root root 2011-02-05 05:07 system
drwxr-xr-x root root 1969-12-31 19:00 sys
dr-xr-xr-x root root 1969-12-31 19:00 proc
-rwxr-x--- root root 32498 1969-12-31 19:00 init.rc
-rwxr-x--- root root 1954 1969-12-31 19:00 init.goldfish.rc
-rwxr-x--- root root 118156 1969-12-31 19:00 init
-rw-r--r-- root root 153 1969-12-31 19:00 default.prop
drwxrwx--x system system 2011-02-22 23:54 data
drwxr-xr-x root root 2011-02-22 23:54 dev
But for some reason when I dump the /osh partition, a couple of those folders come corrupted. Let me know if any of the folders you are interested are damaged on the dump and I will post a tar.bz2 like I did with /etc
In debugging a problem with a cross-compiled binary crashing on someone elses Droid Bionic, I noticed that a bunch of dirs in / are sym-linked into /osh:
Code:
/# [B]ls -l /[/B]
...
lrwxrwxrwx root root 2011-11-06 09:38 etc -> /osh/etc
lrwxrwxrwx root root 2011-11-06 09:38 lib -> /osh/lib
lrwxrwxrwx root root 2011-11-06 09:38 sbin -> /osh/sbin
lrwxrwxrwx root root 2011-11-06 09:38 usr -> /osh/usr
...
Is it 'normal' for stock Droid Bionic Androids to sym-link this stuff in the root dir to /osh, or is it the result of some customisation (Havent seen this on other devices, and dont have hands-on a Bionic to check further ... ) ?
- jc
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$)
Dear Moderators!
Since I had top stop being active in the development the threads that I started with having a master directory and thus that are left here has become totally stale since they have not been updated in a long time nor do I have current plans to continue.
I don't track this forum and the wonders done with this phone but this post has some real potential danger.
The post is outdated and the information in it could therefore be wrong, faulty or even harmful. And I see it mostly harmful in my point of view, since this was the baby steps taken a long time ago.
Looking at the contents it compares several parts of partition tables and even brave (and foolish) tries of me testing philz recoveries. Now Philz has put some safety code since the Note II/S3 melds but for a less experienced user that look at the names.
"hlte and jflte", sound pretty close that we know is not the case but they reeeely want so badly into the "world" of S4 they could try to alter the partition tables, that we serve them on a platter and that there are easy utils for, to TRY make it look like the "real" S4 and really hard brick the phone, or even worse try TWRP of the hlfe "since it was so long time ago" and look at their screen melting away.
Proper scientific rules dictates that if any information is unknown and therefore in a volatile state it should fall under the principle of caution until verified of its validity and safety. I have no insight into that validly and the current development but I highly doubt this post is needed any longer and since this is accessible to the public the "not doing any harm" comes into place and thus this thread should be deleted since if anything useful came out of it it has already been taken into current development and it can cause harm. A lock will not suffice.
Since I know that many posts are not considered being "device specific enough" (like a discussion about lowering the voltage of the kernel) or "cluttering" (explaining the booting process of a kernel works) this post should absolutely fall under some of those rules (or some other that I've yet not encountered) and I strongly think a deletion of this would be more proper then just moving it to the trashcan "General"?
So at least I try to make you see that this post should not be in the trashcan but deleted for the safety of less experienced users.
You can say that they are then stupid. I call them inexperienced. I tried to so many times to post and raise the level of knowledge and we all know where those writing for 8 hours posts went, right?
But this is not about being ignored from "higher devs" about my finding of a side channel attack in the bootloader in 4.3.
This post is just not a safe for those unlucky who got this ****ty phone on their warranty (I got one too). They feel cheated and I understand them.
It's useless, can't use the S4 and not the N9005 stuff. The guys here did an amazing job with it but I had leave. But someone can really do something stupid and and this post gives false "hope". I got some "Pit"-file. Lets try that one...
Since this is also a stub for a "collection" that I also could not finish and I don't recall if I did something more of those but I know you are pros of finding nonsense like this and could you please remove that "clutter" as well?
All the best,
Absie
Abstract
This thread is about testing and finding similarities and differences between the currently two Snapdragon 800 Samsung smartphones, namely the I9506 and Galaxy Note 3 (SM-N9005, hltexx). What we know so far is that they use the same hardware and production line and are separated quite late where they diverge. The theory is therefore that the Samsung Note 3 LTE binaries should work since the development here is non-existent and the similarities are larger between those two then with the previous S4, I9505. The work seem not as straight forward and so far binaries from Note 3 have been incompatible and this thread is about finding our just WHY this is so and how we can try to overcome those problems and have some porting of available ROMs from the major project branches. Similarities with the previous S4 (I9505) will be investigated along the progress of this thread. Since this device is shipped with Android v4.2.2 and without KNOX activated we also need to investigate what activates KNOX and how to avoid that.
Collection of findings
This is a stub of the different pages that will be updated as the progress is ongoing and will be updates as we move along and collect the findings.
General Findings
Stub
Custom Recoveries
Stub
Kernels
Stub
Roms
Stub
Other (KNOX, modems, bootloaders etc)
Stub
.
General Findings
Things we know
The I9506 and Note 3 (int) are based on the same board and therefore they should be interchangeable.
The Pit-files (Partition information) are identical for the both devices except for the obvious, larger screen, more mem and bigger internal data partition. All other partitions are exactly the same and lies on the same place in the Flash which should porting much easier since the core partition layout is the same and makes it much easier and safer to try different versions.
The initial tests done with trying different Custom recoveries has not worked.
Things we don't know
Are the kernel interchangable? Here we have note yet had a 4.3 for I9506 to compare but Samsung has started to roll out that. Knox is then activated.
Differences between other partitions and their content
Questions that need answers (volunteers are needed!)
Now that we have at least 2 versions of the 4.3, we need to hunt for the same releases made on Note 3 and compare them.
Why is not Custom recovery working? Is it something simple?
Does anything from the I9505 work? Are there any similarities there?
.
Custom Recovery
So far we hare 2 custom recoveries (links will be provied).
No custom recoveries from Note 3 has yet been working.
The following recoveries from Note 3 have been tested and found not been working my normal replacement in Odin
Philz_touch_6.04.1 - (Give the first BSOD! Blue! Blue!)
Philz_touch_6.08.9 - (Seems like the screen is melting)
Openrecovery-twrp-2.6.3.0 - (Black screen. Nothing happens)
You can all try, those who has 4.3 and Knox 0x01 could test those. It seems a bit scary, but at least for the the "pull the battery and reinstall a normal one with Odin" worked,
but as usual, this is work that need to be done and nobody here can promise anything. Brick/unbrick, but you might be the hero if you get stuff to work from over Note (like a kernel).
So I have something to fill the next post with?
Who initially provided the working custom recoveries and what was done to make them work?
Please PM me if you don't want to write it here.
.
Kernels
Roms
Other (KNOX, modems, bootloaders etc)
Reserved
Absolon said:
Custom Recovery
So far we hare 2 custom recoveries (links will be provied)
No custom recoveries from Note 3 has yet been working.
The following recoveries from Note 3 have been tested and found not been working my normal replacement in Odin
Philz_touch_6.04.1
Philz_touch_6.08.9
Openrecovery-twrp-2.6.3.0
.
Click to expand...
Click to collapse
Hi Absolon.
Probably because a different portion table. Our is even different from the GT-I9505.
I'll post our full partion table, as it looks on our phone. Just need to get home and fire up my Ubuntu/Linux.
See ya'
Sent from my GT-I9305 using XDA Premium 4 mobile app
I made the Pit files yesterday from the two devices and the are the same.
Same size, same memory adresses.
DeHAWK said:
Hi Absolon.
Probably because a different portion table. Our is even different from the GT-I9505.
I'll post our full partion table, as it looks on our phone. Just need to get home and fire up my Ubuntu/Linux.
See ya'
Sent from my GT-I9305 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Did you see the PIT-files I sent you yesterday?
Those where the same. Exactly the same. So how can it differ?
I posted them above this reply
Absolon said:
Did you see the PIT-files I sent you yesterday?
Those where the same. Exactly the same. So how can it differ?
I posted them above this reply
Click to expand...
Click to collapse
Just received them. I put the files up in a moment.
Sent from my GT-I9506 using XDA Premium 4 mobile app
Ok, now back on my PC, look at this..
[email protected]:/ $ ls -al /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 2013-06-28 18:24 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2013-06-28 18:24 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-06-28 18:24 backup -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2013-06-28 18:24 boot -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2013-06-28 18:24 cache > /dev/block/mmcblk0p24
lrwxrwxrwx root root 2013-06-28 18:24 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-06-28 18:24 ddr -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-06-28 18:24 efs -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2013-06-28 18:24 fota -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2013-06-28 18:24 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2013-06-28 18:24 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2013-06-28 18:24 hidden -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2013-06-28 18:24 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-06-28 18:24 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2013-06-28 18:24 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2013-06-28 18:24 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2013-06-28 18:24 param -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2013-06-28 18:24 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2013-06-28 18:24 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2013-06-28 18:24 recovery -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2013-06-28 18:24 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-06-28 18:24 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-06-28 18:24 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2013-06-28 18:24 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2013-06-28 18:24 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-06-28 18:24 userdata -> /dev/block/mmcblk0p26
Mount Point Number Filesystem name
/dev/block/mmcblk0p1 anphlos
/dev/block/mmcblk0p2 modem
/dev/block/mmcblk0p3 sbl1
/dev/block/mmcblk0p4 dbi
/dev/block/mmcblk0p5 ddr
/dev/block/mmcblk0p6 aboot
/dev/block/mmcblk0p7 rpm
/dev/block/mmcblk0p8 tz
/dev/block/mmcblk0p9 pad
/dev/block/mmcblk0p10 param
/dev/block/mmcblk0p11 ext4 efs
/dev/block/mmcblk0p12 modemst1
/dev/block/mmcblk0p13 modemst2
/dev/block/mmcblk0p14 boot
/dev/block/mmcblk0p15 recovery
/dev/block/mmcblk0p16 fota
/dev/block/mmcblk0p17 backup
/dev/block/mmcblk0p18 fsg
/dev/block/mmcblk0p19 fsc
/dev/block/mmcblk0p20 ssd
/dev/block/mmcblk0p21 persist
/dev/block/mmcblk0p22 ext4 persdata
/dev/block/mmcblk0p23 ext4 system
/dev/block/mmcblk0p24 ext4 cache
/dev/block/mmcblk0p25 ext4 hidden
/dev/block/mmcblk0p26 ext4 userdata
Number Start End Size File system Name Flags
1 4194kB 17.3MB 13.1MB apnhlos
2 17.3MB 71.3MB 54.0MB mdm
3 71.3MB 71.4MB 131kB sbl1
4 71.4MB 71.7MB 262kB sbl2
5 71.7MB 72.2MB 524kB sbl3
6 72.2MB 74.3MB 2097kB aboot
7 74.3MB 74.8MB 524kB rpm
8 74.8MB 75.4MB 524kB tz
9 75.4MB 92.7MB 17.3MB pad
10 92.7MB 107MB 14.3MB ext4 efs
11 107MB 110MB 3146kB modemst1
12 110MB 113MB 3146kB modemst2
13 113MB 114MB 799kB m9kefs1
14 114MB 115MB 799kB m9kefs2
15 115MB 116MB 799kB m9kefs3
16 116MB 3010MB 2894MB ext4 system
17 3010MB 3018MB 8389kB persist
18 3018MB 5189MB 2171MB ext4 cache
19 5189MB 5195MB 6291kB param
20 5195MB 5205MB 10.5MB boot
21 5205MB 5216MB 10.5MB recovery
22 5216MB 5226MB 10.5MB fota
23 5226MB 5233MB 6291kB backup
24 5233MB 5236MB 3146kB fsg
25 5236MB 5236MB 8192B ssd
26 5236MB 5245MB 9437kB ext4 persdata
27 5245MB 5770MB 524MB ext4 hidden
28 5770MB 5791MB 21.0MB carrier
29 5791MB 15.8GB 9961MB ext4 userdata
I had to find some info in XDA, but it should look like this. One thing is sure, and thats the first part, the last 2 parts I made myself...
Try to run the command: ls -al /dev/block/platform/msm_sdcc.1/by-name
Do it in a terminal.
Btw. Does anybody know why I can't upload screenshots and other stuff???
I just compared the 2 .txt files in excel
The result are in attachement >
Cell B is BASE
Cell A is compared with Cell B
- Everthing green in Cell A is identical with Cell B
- Everthing white in Cell A is different to Cell B
You can also compare to this ref thread [DEV][REF][INFO] Partitions GT-I9506
Cheers
Absolon said:
I made the Pit files yesterday from the two devices and the are the same.
Same size, same memory adresses.
Click to expand...
Click to collapse
Got your mail, looking at them right now and comparing with my own files.
See ya'
---------- Post added at 08:09 PM ---------- Previous post was at 08:01 PM ----------
DeHAWK said:
Got your mail, looking at them right now and comparing with my own files.
See ya'
Click to expand...
Click to collapse
Ok, this looks nice. Have to look more into them.
---------- Post added at 08:21 PM ---------- Previous post was at 08:09 PM ----------
xenix96 said:
I just compared the 2 .txt files in excel
The result are in attachement >
Cell B is BASE
Cell A is compared with Cell B
- Everthing green in Cell A is identical with Cell B
- Everthing white in Cell A is different to Cell B
You can also compare to this ref thread [DEV][REF][INFO] Partitions GT-I9506
Cheers
Click to expand...
Click to collapse
My dear friend, please zip your files, I don't use rar in Ubuntu.
Have to switch to Windows and back...lol
Somethings wrong with my account here, it log out out after a few minutes, can't add pics etc...
But at least I can get in now on my laptop. Might have to cantact the Mod.
See ya'
DeHAWK said:
Got your mail, looking at them right now and comparing with my own files.
See ya'
---------- Post added at 08:09 PM ---------- Previous post was at 08:01 PM ----------
Ok, this looks nice. Have to look more into them.
---------- Post added at 08:21 PM ---------- Previous post was at 08:09 PM ----------
My dear friend, please zip your files, I don't use rar in Ubuntu.
Have to switch to Windows and back...lol
Somethings wrong with my account here, it log out out after a few minutes, can't add pics etc...
But at least I can get in now on my laptop. Might have to cantact the Mod.
See ya'
Click to expand...
Click to collapse
Added Mappe1.zip to http://forum.xda-developers.com/showpost.php?p=49182714&postcount=12
Cheers
Nice thread, i already have the i9506, and i will get my Note 3 as a company phone on wednesday. I'd ble glad to help!
I created my I9506 files from my phone.
All XDA related content will be placed here for reference and PM me your gmails and I give you r/w there.
(changed the link since someone tried to read INSIDE a rar file in gdocs. There is a zip there now as well)
So, as you see, I got the same values, just that you didn't give you any?
We do have exactly the same layout
We know it's the same board
We have recovery that is working
N9005 recoveries are NOT?
Any idea?
Who had the "mended" Philz from start? What was changed so it would work?
Because if we can figure this out it looks promising. If we can't then we need to start trying (need that anyway) compiling stuff and go from there.
But I thought it would be interesting just to check if it would work or not. Damn it...
/Abs
Edit: OMG, I outed myself
xenix96 said:
I just compared the 2 .txt files in excel
The result are in attachement >
Cell B is BASE
Cell A is compared with Cell B
- Everthing green in Cell A is identical with Cell B
- Everthing white in Cell A is different to Cell B
You can also compare to this ref thread [DEV][REF][INFO] Partitions GT-I9506
Cheers
Click to expand...
Click to collapse
I created the PIT-file from my phone.
Will place all further things
xenix96 said:
Added Mappe1.zip to http://forum.xda-developers.com/showpost.php?p=49182714&postcount=12
Cheers
Click to expand...
Click to collapse
Yes, I will use the algorithm that was invented in 1978 (ok 1989 and I have NO IDEA why Google chose that when there are so many more effective alg that are OS)...
I can use LHA, or even a C64 cruncher just to get you start working dammit
And btw, unrar if freeware
/Absie
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.