Database Develop

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

[Q] au SCL22

I currently having a au (Japan) SCL22 which is a au kddi branded Galaxy Note 3. I'm wondering if anyone knows how to root it?

ken0ryu said:
I currently having a au (Japan) SCL22 which is a au kddi branded Galaxy Note 3. I'm wondering if anyone knows how to root it?
Click to expand...
Click to collapse
I suppose unless somebody gets the official firmware to people who know how to root devices here, we won't see one. =) Someone is on the Docomo version already. I am sure it will be rooted, just a bit later. Until then, I will keep wondering why I will have to void my warranty in order to have access to what Note 3 can already do - unrestricted multi-tasking with multi windows and s pen window...

Snakiest said:
I suppose unless somebody gets the official firmware to people who know how to root devices here, we won't see one. =) Someone is on the Docomo version already. I am sure it will be rooted, just a bit later. Until then, I will keep wondering why I will have to void my warranty in order to have access to what Note 3 can already do - unrestricted multi-tasking with multi windows and s pen window...
Click to expand...
Click to collapse
This phone can't root now.

doantri said:
This phone can't root now.
Click to expand...
Click to collapse
Well, that is what I said. I remember it took about 6 months for the AU version of the Galazy S2 to get rooted, so I expect something like this with Note 3.

This is ridiculousness! I had a desire HD on Softbank and could run any desire HD rom on it I wanted. Now I switch to au to find this is not the case huh? Why can't we use sprint or Verizon roms/recoveries?

You ever figure anything out? This is killing me. Custom rom seems like is never going to happen
ken0ryu said:
I currently having a au (Japan) SCL22 which is a au kddi branded Galaxy Note 3. I'm wondering if anyone knows how to root it?
Click to expand...
Click to collapse

rooted note scl22
dan.kels.r said:
You ever figure anything out? This is killing me. Custom rom seems like is never going to happen
Click to expand...
Click to collapse
thanks for replay but some one rooted done

how to root Galaxy note 3 SCL22
hi
i also want to know same thing, how to root Galaxy note 3 SCL22
anyone know pls help us

need help
Hi everybody. I successfully rooted my scl22 using the instructions in a chinese site : " SCL22 root & sim unlock
Galaxy Note3 SCL22のRoot化(SC-01Fも対応)
SM-N9005用CWMをOdinから焼き込み、SuperSUをインストールすればRoot化完了。
・SM-N9005用CWMのダウンロード先
n9005-cwm-recovery-6.0.4.5(1116).tar
・SuperSUのダウンロード先
UPDATE-SuperSU-v1.65.zip
・sgs3_rooting_supersu_v3.zipも必要です。ググってください。
○順番
1.CWMをOdinで焼きこみ。
2.CWMを起動し、sgs3_rooting_supersu_v3.zipをインストール。
3.続けてUPDATE-SuperSU-v1.65.zipをインストール。
4.再起動すればsuが効くようになります。
○カウントアップはCWMを焼くとKNOX WARRANTYが変化します。
他は初期ROM焼いて初期化すれば元に戻ります。
※カウントアップするとオサイフがNGになります。
※Root化されたsystem.imgのみ焼けば大丈夫かも？
KNOX WARRANTY VOID : 0x0
↓
KNOX WARRANTY VOID : 0x1
Galaxy Note 3 SCL22の内部パーティション
[email protected]:/ # ls -l /dev/block/platform/msm_sdcc.1/by-name/
ls -l /dev/block/platform/msm_sdcc.1/by-name/
lrwxrwxrwx root root 1970-01-02 04:36 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-02 04:36 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-02 04:36 backup -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-02 04:36 boot -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-02 04:36 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-02 04:36 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-02 04:36 ddr -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-02 04:36 efs -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-02 04:36 fota -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-02 04:36 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-02 04:36 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-02 04:36 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-02 04:36 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-02 04:36 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-02 04:36 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-02 04:36 param -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-02 04:36 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-02 04:36 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-02 04:36 recovery -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-02 04:36 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-02 04:36 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-02 04:36 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-02 04:36 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-02 04:36 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-02 04:36 userdata -> /dev/block/mmcblk0p25
zhongkai cheng*时间：*下午7:20
,but not beeing experienced in programming , i wasn't able to aply the second set of instructions. There is a script that should be run and i do not know how to do that. Maybe someone with experience can help us.

mvmaos said:
Hi everybody. I successfully rooted my scl22 using the instructions in a chinese site : " SCL22 root & sim unlock
Galaxy Note3 SCL22のRoot化(SC-01Fも対応)
SM-N9005用CWMをOdinから焼き込み、SuperSUをインストールすればRoot化完了。
・SM-N9005用CWMのダウンロード先
n9005-cwm-recovery-6.0.4.5(1116).tar
・SuperSUのダウンロード先
UPDATE-SuperSU-v1.65.zip
・sgs3_rooting_supersu_v3.zipも必要です。ググってください。
○順番
1.CWMをOdinで焼きこみ。
2.CWMを起動し、sgs3_rooting_supersu_v3.zipをインストール。
3.続けてUPDATE-SuperSU-v1.65.zipをインストール。
4.再起動すればsuが効くようになります。
○カウントアップはCWMを焼くとKNOX WARRANTYが変化します。
他は初期ROM焼いて初期化すれば元に戻ります。
※カウントアップするとオサイフがNGになります。
※Root化されたsystem.imgのみ焼けば大丈夫かも？
KNOX WARRANTY VOID : 0x0
↓
KNOX WARRANTY VOID : 0x1
Galaxy Note 3 SCL22の内部パーティション
[email protected]:/ # ls -l /dev/block/platform/msm_sdcc.1/by-name/
ls -l /dev/block/platform/msm_sdcc.1/by-name/
lrwxrwxrwx root root 1970-01-02 04:36 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-02 04:36 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-02 04:36 backup -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-02 04:36 boot -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-02 04:36 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-02 04:36 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-02 04:36 ddr -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-02 04:36 efs -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-02 04:36 fota -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-02 04:36 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-02 04:36 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-02 04:36 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-02 04:36 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-02 04:36 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-02 04:36 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-02 04:36 param -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-02 04:36 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-02 04:36 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-02 04:36 recovery -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-02 04:36 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-02 04:36 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-02 04:36 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-02 04:36 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-02 04:36 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-02 04:36 userdata -> /dev/block/mmcblk0p25
zhongkai cheng*时间：*下午7:20
,but not beeing experienced in programming , i wasn't able to aply the second set of instructions. There is a script that should be run and i do not know how to do that. Maybe someone with experience can help us.
Click to expand...
Click to collapse
You may have rooted, but you also blew your KNOX fuse and now your warranty is voided. KNOX WARRANTY VOID : 0x1 this line tells you that the KNOX has been tripped. This is impossible to reset so if you ever have to send your phone in for repairs now you will not be able to make a warranty claim. This is what haapens when you get impatient and try things that have not been proven like KINGOROOT.

need help
Solarenemy68 said:
You may have rooted, but you also blew your KNOX fuse and now your warranty is voided. KNOX WARRANTY VOID : 0x1 this line tells you that the KNOX has been tripped. This is impossible to reset so if you ever have to send your phone in for repairs now you will not be able to make a warranty claim. This is what haapens when you get impatient and try things that have not been proven like KINGOROOT.
Click to expand...
Click to collapse
i do not care about the knox.
mi problem is that i can not use a european sim for gsm , hence the need to unlock the phone. so if you can help with that script, please do.
i saw on youtube someone in vietnam, that unlocked a japanesse version of note 3, and offers his service for money, but only if you can go with the phone to him..., so... it can be done.

mvmaos said:
i do not care about the knox.
mi problem is that i can not use a european sim for gsm , hence the need to unlock the phone. so if you can help with that script, please do.
i saw on youtube someone in vietnam, that unlocked a japanesse version of note 3, and offers his service for money, but only if you can go with the phone to him..., so... it can be done.
Click to expand...
Click to collapse
can you provide me that vietnam video link pls. If you have any additional details about unlocking SCL22 pls share with us. I will do
the same. Because i want to unlock my Note 3 SCL22 immediately.

need help
niranjan.anu said:
can you provide me that vietnam video link pls. If you have any additional details about unlocking SCL22 pls share with us. I will do
the same. Because i want to unlock my Note 3 SCL22 immediately. [/QUOTE
watch?v=7E12QTQv3Io just check that id on youtube or search for "unlock scl22"
Click to expand...
Click to collapse

mvmaos said:
niranjan.anu said:
can you provide me that vietnam video link pls. If you have any additional details about unlocking SCL22 pls share with us. I will do
the same. Because i want to unlock my Note 3 SCL22 immediately. [/QUOTE
watch?v=7E12QTQv3Io just check that id on youtube or search for "unlock scl22"
Click to expand...
Click to collapse
I send a message to this person. He replied as
"I can unlock SCL22 but i cant to do it by network. sorry"
Click to expand...
Click to collapse

scl 22 unlock
niranjan.anu said:
mvmaos said:
I send a message to this person. He replied as
"I can unlock SCL22 but i cant to do it by network. sorry"
Click to expand...
Click to collapse
did you try to ask him, at least how it can be done,or, like , what tool or software he's using ?
Click to expand...
Click to collapse

Hm, that root should be fine in a year when the warranty ends unless some smart fellow comes up with a better way to do it. As for the SIM-unlock, I hear it is possible to ask either the carrier or the phone maker for the unlock key (or whatever it is). I believe some companies even do that officially for a fee. You guys should contact AU and then Samsung support for that, really, especially if you are Japanese - should be a lot easier than for some of us here. And then report here to let everybody know.

I have another AU phone, Xperia Acro. Long time ago, I also was looking for a way to unlock it, to use with European SiM. That was hard to find. After long search, I found a company which did it for about 50 bucks. But, at the end, I could only use my phone to do phone calls, but no SMS. Tried different ways - but SMS didn't work. Fund similar complaints about SMS on my AU model online, so its a real issue. And using phone without SMS in Europe sucks.
Got another phone for Europe, after all.
AU have something weird about their frequency so that might be that SCL22 will not be able to handle SMS either, even unlocked. Think if you really need to unock it

How To Root Samsung Galaxy Note 3
How To Root Samsung Galaxy Note 3 SCL22 au by KDDI (JAPAN phone) 100% working.
Quote:
My phone details (Tested devise)
Samsung Galaxy Note 3 SCL22 AU by KDDI (JAPAN phone) SM-N900J
Android Version - 4.4.2
Baseband Version - SCL22KDU2FNF7
Kernel Version - 3.4.0-1990145
This is all the stuff you need to Root your phone -
01. Kies3Setup.exe
02. ODIN 3.07 (Do Not Use 3.09)
03. UPDATE-SuperSU-v2.35.zip
04. hltedcm-KK-KBC-CWM-v6.0.5.0_r0-recovery.tar
05. CWMrecovery-scl22kk.tar
06. Stock firmware - (for that you need to register and download the stock kernel from sammobile. you better download it just in case )
DOWNLOAD LINKS -
01.hltedcm-KK-KBC-CWM-v6.0.5.0_r0-recovery.tar - https://mega.co.nz/#!1FI3xICS!7Un6z5...8GUZMkxkAwa7n4
02.02.CWMrecovery-scl22kk.tar - https://mega.co.nz/#!FZoEAbxC!j_l24G...3Vl63DHMSThuwE
03.twrp.tar - https://mega.co.nz/#!wd5Ama5b!33WccV...a6F0uHlBf_CVRE
04.SuperSU.rar - https://mega.co.nz/#!xY5CBJ4Y!NCN_DL...7l0b5P7UmaesyA
Quote:
(This file comes with a RAR format so extract it and inside that folder you can see UPDATE-SuperSU-v2.35.zip file )
05.Odin307.zip - https://mega.co.nz/#!Bd5x0CzC!UavXZ3...nWex3ECZ_mH8LI
01.Connect your phone to PC and copy and paste UPDATE-SuperSU-v2.35.zip to phone SD card
02.Start Odin 3.07
03.Put your phone to Download mode
04.Flash the hltedcm-KK-KBC-CWM-v6.0.5.0_r0-recovery.tar
05.Flash the CWMrecovery-scl22kk.tar
06.Start your phone then put it to Recovery mode and install UPDATE-SuperSU-v2.35.zip
07.Start your phone in normal mode. And now you all set and ROOT.
FINISH.!
Enjoy your rooted phone.!

ken0ryu said:
I currently having a au (Japan) SCL22 which is a au kddi branded Galaxy Note 3. I'm wondering if anyone knows how to root it?
Click to expand...
Click to collapse
Read this - http://forum.xda-developers.com/galaxy-note-3/general/samsung-galaxy-note-3-scl22-au-kddi-t2964801

Tmobile d959 4.4.2 partition table

This is the partition table for the TMOBILE LG-D959 4.4.2 FLEX ONLY
DDR -> /dev/block/mmcblk0p4
aboot -> /dev/block/mmcblk0p5
blus -> /dev/block/mmcblk0p29
boot -> /dev/block/mmcblk0p7
cache -> /dev/block/mmcblk0p35
carrier -> /dev/block/mmcblk0p27
dbi -> /dev/block/mmcblk0p3
dbibak -> /dev/block/mmcblk0p30
drm -> /dev/block/mmcblk0p21
encrypt -> /dev/block/mmcblk0p20
eri -> /dev/block/mmcblk0p28
fota -> /dev/block/mmcblk0p25
fsc -> /dev/block/mmcblk0p17
fsg -> /dev/block/mmcblk0p16
grow -> /dev/block/mmcblk0p39
laf -> /dev/block/mmcblk0p24
misc -> /dev/block/mmcblk0p13
modem -> /dev/block/mmcblk0p1
modemst1 -> /dev/block/mmcblk0p10
modemst2 -> /dev/block/mmcblk0p11
mpt -> /dev/block/mmcblk0p26
pad -> /dev/block/mmcblk0p9
pad1 -> /dev/block/mmcblk0p12
pad2 -> /dev/block/mmcblk0p19
persist -> /dev/block/mmcblk0p14
rct -> /dev/block/mmcblk0p33
recovery -> /dev/block/mmcblk0p15
rpm -> /dev/block/mmcblk0p6
rpmbak -> /dev/block/mmcblk0p31
sbl1 -> /dev/block/mmcblk0p2
sns -> /dev/block/mmcblk0p22
spare -> /dev/block/mmcblk0p37
ssd -> /dev/block/mmcblk0p18
system -> /dev/block/mmcblk0p34
tombstones -> /dev/block/mmcblk0p36
tz -> /dev/block/mmcblk0p8
tzbak -> /dev/block/mmcblk0p32
userdata -> /dev/block/mmcblk0p38
ve -> /dev/block/mmcblk0p23

why not just use
Code:
ls -l /dev/block/platform/msm_sdcc.1/by-name
????

Why go that route when its right in /system
And it will help people know the correct partition for their zips
And side note sorry for taking so long on the kernel been busy working nonstop

allenjthomsen said:
Why go that route when its right in /system
And it will help people know the correct partition for their zips
And side note sorry for taking so long on the kernel been busy working nonstop
Click to expand...
Click to collapse
because we all use /dev/block/platform/msm_sdcc.1/by-name/boot, recovery etc nowa days. Look at the fstabs for most devices done in the last year.
Which also works in the updater-script.
New way of doing things, need to keep up. lol
Makes it easy to remember too.

Fixed

I didnt forget sorry was being lazy next time i wont be

allenjthomsen said:
And side note sorry for taking so long on the kernel been busy working nonstop
Click to expand...
Click to collapse
What kernel? Did I miss something ? Benn away for a bit helping out some noobs that got flash happy and went to far with it. Lmao.

I was going to build a kernel that would allow us to flash a recovery but i havent had a chance yet

Also check outthis thread i posted some stuff
http://forum.xda-developers.com/showthread.php?t=2834433

@mattwheat i am in talks with @ cloudyfa about making a cloudyg3 flex rom that is flashable via kdz waiting to hear back

allenjthomsen said:
I was going to build a kernel that would allow us to flash a recovery but i havent had a chance yet
Click to expand...
Click to collapse
and just what is a kernel going to do about a locked bootloader??
Like I have said numerous times, the jb aboot and currently recovery works fine. Need to find the rebooting issue with the kk kernel when using them.

PlayfulGod said:
Let me say this again since no one seems to f**king read. Recovery works fine with all models. The issue is on 4.4 and getting the kk kernel to stay booted with the stock kernel and maybe possibly on cm when device has service.
Click to expand...
Click to collapse
Just so u know i have held off building anything kernel related because of this i am willing to help anyway i can.
ive dug around in the kernel and talked with some other devs .
I would really like to get our heads together PG and get a custom recovery going for 4.4.2 without reboot issues

And yes i understood that its the kernel causing issues

To be honest i think the issue is with the aboot being jb and not being kk if the aboot were to be switched to kk i think it would solve the issue of reboots and not being able to reboot to kk

The reason i say that the aboot needs to be switched to kk is because the phone is reading it as jb phone and not kk when using jb aboot

allenjthomsen said:
Just so u know i have held off building anything kernel related because of this i am willing to help anyway i can.
ive dug around in the kernel and talked with some other devs .
I would really like to get our heads together PG and get a custom recovery going for 4.4.2 without reboot issues
Click to expand...
Click to collapse
allenjthomsen said:
And yes i understood that its the kernel causing issues
Click to expand...
Click to collapse
you arent alone lol.
I get msg's daily asking when FreedomFlex will support kitkat.
savoca seemed to think something was missing from the kernel src back when he first did the edits need to get the 4.4 kernel to boot with our aboot. And since he doesnt have a Flex, its up to us to find out what is causing the reboot isssus. I will try to work on it this week some time.

[FIX] Restoring G900A after attempting to flash modified recovery [10 Dec 2014]

I know --- the bootloader is locked. But I still had to prove it to myself. And the info provided here may be useful to developers as well as to end-users.
Here is my story:
Running stock KK 4.4.2 (NCE) on my G900A, I successfully rooted using GeoHot’s towelroot https://towelroot.com/.
Then I froze the AT&T software updater app via Titanium Backup Pro --- since there is presently no way to re-root after updating.
Then I modified the stock recovery image to enable “adbd” (Android Debug Bridge daemon). Here’s a brief description of the process:
Running ADB with root and busybox installed, I created directory: /sdcard/Boot and did this:
Code:
dd if=/dev/block/mmcblk0p16 of=/sdcard/Boot/recovery.img
Then on Windows, I unpacked recovery.img to kernel and /ramdisk and modified the /ramdisk/init.rc script as follows:
Code:
service recovery /sbin/recovery
service adbd /sbin/adbd recovery
[COLOR="Blue"]
# se[email protected] (09 Dec 2014)
# disabled
# [email protected] (09 Dec 2014)
[/COLOR]
socket adbd stream 660 system system
##++ Security R&D Group
service qrngd /system/bin/qrngd -f
class load_ode_env
user root
group root
oneshot
Then I repacked kernel and modified /ramdisk to recovery-repack.img, dropped it into /sdcard/Boot and flashed it to the recovery partition from 4.4.2 via ADB:
Code:
dd if=/sdcard/Boot/recovery-repack.img of=/dev/block/mmcblk0p16
When I rebooted, my phone returned an error message and rebooted again, this time to download mode. Oh well, I was really hoping to sneak this one past AT&T.
Somewhat nervous, I scoured the web for two days in search of a decent stock NCE build to recover my G900A. But all of the links were slow, flaky, costly and/or plagued with ads --- except for this one…
NCE Stock TAR with md5: http://www.rwilco12.com/forum/showthread.php?tid=883
Odin versions (esp. v1.85 --- considered the most stable):
http://www.rwilco12.com/forum/showthread.php?tid=101
So I downloaded the 1.5GB zip, decompressed to: “G900AUCU1ANCE_G900AATT1ANCE_G900AUCU1ANCE_HOME.tar.md5”
and ran Odin v1.85 with:
“\{Path-to}\G900AUCU1ANCE_G900AATT1ANCE_G900AUCU1ANCE_HOME.tar.md5”
in the PDA slot with Auto Reboot and F. Reset Time checked and no others checked except for PDA. Execution was flawless (ref. image below) and my G900A gracefully rebooted to stock KK 4.4.2--- with all of my installed apps, data and settings intact. And I quickly recovered root by re-launching the towelroot APK.
Of course I did lose busybox since it installs under /system/xbin. No problem, I just went to the BB app I had installed earlier and reinstalled BB from there.
Note: When I stripped off the .md5 suffix and opened the resulting .tar file with 7zip, an error message was returned but the file listing was still shown:
Note the absence of a data image --- a good thing if you have installed apps etc.
Something else I found helpful is the G900A partition map. Navigating to /dev/block/platform/msm_sdcc.1/by-name …
Code:
cd /dev/block/platform/msm_sdcc.1/by-name
[email protected]:/dev/block/platform/msm_sdcc.1/by-name # ls -ld *
ls -ld *
lrwxrwxrwx root root 2014-01-02 11:49 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-01-02 11:49 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-01-02 11:49 backup -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2014-01-02 11:49 boot -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-01-02 11:49 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2014-01-02 11:49 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-01-02 11:49 ddr -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-01-02 11:49 efs -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-01-02 11:49 fota -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2014-01-02 11:49 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2014-01-02 11:49 fsg -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-01-02 11:49 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-01-02 11:49 modemst1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-01-02 11:49 modemst2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-01-02 11:49 pad -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-01-02 11:49 param -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-01-02 11:49 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2014-01-02 11:49 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2014-01-02 11:49 recovery -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-01-02 11:49 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-01-02 11:49 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-01-02 11:49 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2014-01-02 11:49 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2014-01-02 11:49 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-01-02 11:49 userdata -> /dev/block/mmcblk0p25
[email protected]:/dev/block/platform/msm_sdcc.1/by-name #
Note especially the boot, recovery, system, data and cache partitions…
Code:
lrwxrwxrwx root root 2014-01-02 11:49 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-01-02 11:49 boot -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-01-02 11:49 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2014-01-02 11:49 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2014-01-02 11:49 recovery -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-01-02 11:49 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2014-01-02 11:49 userdata -> /dev/block/mmcblk0p25
Many thanks to Rwilco12 for SGS5 support: http://www.rwilco12.com/
Also thanks to Krang for consolidating Rwilco12’s SGS5 links: http://www.rwilco12.com/forum/member.php?action=profile&uid=450

sendust7 said:
I know --- the bootloader is locked. But I still had to prove it to myself. And the info provided here may be useful to developers as well as to end-users.
Here is my story:
Running stock KK 4.4.2 (NCE) on my G900A, I successfully rooted using GeoHot’s towelroot https://towelroot.com/.
Then I froze the AT&T software updater app via Titanium Backup Pro --- since there is presently no way to re-root after updating.
Then I modified the stock recovery image to enable “adbd” (Android Debug Bridge daemon). Here’s a brief description of the process:
Running ADB with root and busybox installed, I created directory: /sdcard/Boot and did this:
Code:
dd if=/dev/block/mmcblk0p16 of=/sdcard/Boot/recovery.img
Then on Windows, I unpacked recovery.img to kernel and /ramdisk and modified the /ramdisk/init.rc script as follows:
Code:
service recovery /sbin/recovery
service adbd /sbin/adbd recovery
[COLOR="Blue"]
# [email protected] (09 Dec 2014)
# disabled
# [email protected] (09 Dec 2014)
[/COLOR]
socket adbd stream 660 system system
##++ Security R&D Group
service qrngd /system/bin/qrngd -f
class load_ode_env
user root
group root
oneshot
Then I repacked kernel and modified /ramdisk to recovery-repack.img, dropped it into /sdcard/Boot and flashed it to the recovery partition from 4.4.2 via ADB:
Code:
dd if=/sdcard/Boot/recovery-repack.img of=/dev/block/mmcblk0p16
When I rebooted, my phone returned an error message and rebooted again, this time to download mode. Oh well, I was really hoping to sneak this one past AT&T.
Somewhat nervous, I scoured the web for two days in search of a decent stock NCE build to recover my G900A. But all of the links were slow, flaky, costly and/or plagued with ads --- except for this one…
NCE Stock TAR with md5: http://www.rwilco12.com/forum/showthread.php?tid=883
Odin versions (esp. v1.85 --- considered the most stable):
http://www.rwilco12.com/forum/showthread.php?tid=101
So I downloaded the 1.5GB zip, decompressed to: “G900AUCU1ANCE_G900AATT1ANCE_G900AUCU1ANCE_HOME.tar.md5”
and ran Odin v1.85 with:
“\{Path-to}\G900AUCU1ANCE_G900AATT1ANCE_G900AUCU1ANCE_HOME.tar.md5”
in the PDA slot with Auto Reboot and F. Reset Time checked and no others checked except for PDA. Execution was flawless (ref. image below) and my G900A gracefully rebooted to stock KK 4.4.2--- with all of my installed apps, data and settings intact. And I quickly recovered root by re-launching the towelroot APK.
Of course I did lose busybox since it installs under /system/xbin. No problem, I just went to the BB app I had installed earlier and reinstalled BB from there.
Note: When I stripped off the .md5 suffix and opened the resulting .tar file with 7zip, an error message was returned but the file listing was still shown:
Note the absence of a data image --- a good thing if you have installed apps etc.
Something else I found helpful is the G900A partition map. Navigating to /dev/block/platform/msm_sdcc.1/by-name …
Code:
cd /dev/block/platform/msm_sdcc.1/by-name
[email protected]:/dev/block/platform/msm_sdcc.1/by-name # ls -ld *
ls -ld *
lrwxrwxrwx root root 2014-01-02 11:49 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-01-02 11:49 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-01-02 11:49 backup -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2014-01-02 11:49 boot -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-01-02 11:49 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2014-01-02 11:49 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-01-02 11:49 ddr -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-01-02 11:49 efs -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-01-02 11:49 fota -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2014-01-02 11:49 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2014-01-02 11:49 fsg -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-01-02 11:49 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-01-02 11:49 modemst1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-01-02 11:49 modemst2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-01-02 11:49 pad -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-01-02 11:49 param -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-01-02 11:49 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2014-01-02 11:49 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2014-01-02 11:49 recovery -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-01-02 11:49 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-01-02 11:49 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-01-02 11:49 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2014-01-02 11:49 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2014-01-02 11:49 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-01-02 11:49 userdata -> /dev/block/mmcblk0p25
[email protected]:/dev/block/platform/msm_sdcc.1/by-name #
Note especially the boot, recovery, system, data and cache partitions…
Code:
lrwxrwxrwx root root 2014-01-02 11:49 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-01-02 11:49 boot -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-01-02 11:49 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2014-01-02 11:49 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2014-01-02 11:49 recovery -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-01-02 11:49 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2014-01-02 11:49 userdata -> /dev/block/mmcblk0p25
Many thanks to Rwilco12 for SGS5 support: http://www.rwilco12.com/
Also thanks to Krang for consolidating Rwilco12’s SGS5 links: http://www.rwilco12.com/forum/member.php?action=profile&uid=450
Click to expand...
Click to collapse
Actually a little searching on the forums and you'll find a very simple painless way to reroot after the update, also odin 3.09 or 3.10 is the current version. And if you also search for safestrap in the forums you'll find recovery. You have provided a lot of info here thanks for that but could have saved yourself a lot of grief and time by searching first
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app

Question, did this return the phone to stock completely? Removing root and safestrap?

can not locate
cstayton said:
Actually a little searching on the forums and you'll find a very simple painless way to reroot after the update, also odin 3.09 or 3.10 is the current version. And if you also search for safestrap in the forums you'll find recovery. You have provided a lot of info here thanks for that but could have saved yourself a lot of grief and time by searching first
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
Safestrap is not available for the SM-G900A? i can not find any.

ZD551KL/ZE550KL/ZE551KL/ZE600KL/ZE601KL official bootloader unlock

Released on asus website 14/12/2015:
Marshmallow:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551KL/UnlockTool_ASUS_AndroidM20160928_Singed.zip
Lollipop:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE600KL/ZE600KL_UnlockApp.zip
The APKs for each are binary identical, so it is not really important which unlock utility you download.
Frequently asked questions:
Q: will this work on ZE500KG / ZE500KL / ASUS_Z00RD / ASUS_Z00RD_5 / ASUS_Z00RD_7 / ASUS_Z00ED / ASUS_Z00EDB / ASUS_Z00E_1 / ASUS_Z00E_2 / ASUS_Z00E_3
A: we do not think so, but we do not know if anyone has tried it.
Q: can I relock bootloader?
A: we do not have a way of re-locking bootloader right now. Hopefully it will be possible using a backup of some partition to restore original bootloader, but we have not found it yet.
Q: can I restore my warranty by re-locking the bootloader?
A: we believe that ASUS records the serial number of the device through the unlock utility, so it will not be possible to make a warranty claim even if you do manage to re-lock the bootloader.
Q: can I still receive OTA updates?
A: we do not know, because no updates have been released since the unlock utility was released.
Q: can I still update firmware manually?
A: yes, definitely. fetch the new firmware zip from ASUS website and flash in stock recovery or transfer to root of sd-card and boot the phone normally (it will find the update zip file and prompt you).
Download notes from the site:
Unlock Device App: Unlock boot loader
Notice:
1. Update your software image to V1.15.40.771 or latest version
2. Before you download, install, and use the Unlock Device App you acknowledge and assume complete risk to the quality and performance of this App, including but not limited to the following: once you activate the App you will not be able to recover your ASUS product (“Original Product”) back to original locked conditions; the Original Product with the activated App will not be deemed the Original Product; the Revised Product will no longer be covered under the warranty of the Original Product; the software of Revised Product will no longer be deemed the software of the Original Product and can no longer receive ASUS software updates; your purchased digital content may also be affected.
You also acknowledge ASUS does not guarantee service satisfaction to any Revised Product, including events involving paid service requested by you to be performed to the Revised Product.
Furthermore, such repaired Revised Product will not be covered under the warranty of the Original Product; the software of the repaired Revised Product will not be deemed the software of the Original Product and will not receive ASUS software updates.
It is strongly advised that you avoid activating this App unless you fully understand and accept the risks that may arise.
Click to expand...
Click to collapse

Do you think this would work on the US 551KL? If so thatd be great

* edit *
firmware v1.15.40.771 now released for ZE600KL, so I will try to flash now on ZE550KL and then unlock
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE600KL/UL-Z00L-WW-1.15.40.771-user.zip

Please note, I have ZE550KL-1A025TW version, Snapdragon 615, 2GB RAM (ASUS_Z00LD / ASUS_Z00L_93)
I updated my ZE550KL to firmware v1.15.40.771:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE600KL/UL-Z00L-WW-1.15.40.771-user.zip
then ran the ZE600KL unlock utility.
Unlock utility runs without errors, phone reboots, no errors, everything still working fine.
Confirmed unlock successful
Code:
C:\adb>fastboot oem device-info
...
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.010s]
finished. total time: 0.010s

Let me get this straight, you flashed ZE600KL firmware on your ZE550KL and it worked? Not something I would recommend.

Yeh i did, in the source code they seem to be built with identical makefiles so i just figured i would experiment
Sent from my GT-I9195 using Tapatalk

You can test your bootloader status, if you type in fastboot mode "fastboot oem device-info"

Can someone please paste the output on a rooted ZE550KL in adb shell:
Code:
ls -al /dev/block/platform/dw_mmc/by-name
I already compiled a cm recovery, but i am not sure about the block names...

destilant said:
Can someone please paste the output on a rooted ZE550KL in adb shell:
I already compiled a cm recovery, but i am not sure about the block names...
Click to expand...
Click to collapse
Would the recovery also work for a 551KL? I can get you that, if i can help. And also test the recovery

wickedpygmy said:
Yeh i did, in the source code they seem to be built with identical makefiles so i just figured i would experiment
Sent from my GT-I9195 using Tapatalk
Click to expand...
Click to collapse
fair enough. How do it look? The 600KL is a 6" phone and the 5500KL a 5.5". Does it appear to overlap or anything?

capeorigins said:
Would the recovery also work for a 551KL? I can get you that, if i can help. And also test the recovery
Click to expand...
Click to collapse
Nope, the ZE551KL is shipped with a Snapdragon 615 MSM8939, the ZE550KL with a 610 MSM8916, so it wont work...

destilant said:
You can test your bootloader status, if you type in fastboot mode "fastboot oem device-info"
Click to expand...
Click to collapse
Code:
C:\adb>adb devices
List of devices attached
F8AZCY01P722 device
C:\adb>adb reboot bootloader
C:\adb>fastboot oem device-info
...
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.010s]
finished. total time: 0.010s
C:\adb>

destilant said:
Can someone please paste the output on a rooted ZE550KL in adb shell:
Code:
ls -al /dev/block/platform/dw_mmc/by-name
I already compiled a cm recovery, but i am not sure about the block names...
Click to expand...
Click to collapse
Moreover, can somebody please upload raw backups of the 'aboot' (& 'abootbak' if present) partition before & after unlocking the bootloader? You need root access & can use something like this one.

destilant said:
You can test your bootloader status, if you type in fastboot mode "fastboot oem device-info"
Click to expand...
Click to collapse
heywheelie said:
fair enough. How do it look? The 600KL is a 6" phone and the 5500KL a 5.5". Does it appear to overlap or anything?
Click to expand...
Click to collapse
looks normal, both have same resolution. I think both phones use the same firmware since the kernel is identical and Asus don't release Z00m firmware but use Z00L for both models.

Titokhan said:
Moreover, can somebody please upload raw backups of the 'aboot' (& 'abootbak' if present) partition before & after unlocking the bootloader? You need root access & can use something like this one.
Click to expand...
Click to collapse
@Titokhan must be too late for me to do this, since I already unlocked and have no way to get back?
attached is aboot and abootbak after unlocking, maybe @heywheelie can upload the before?

destilant said:
Nope, the ZE551KL is shipped with a Snapdragon 615 MSM8939, the ZE550KL with a 610 MSM8916, so it wont work...
Click to expand...
Click to collapse
the ZE550KL has a snapdragon 615 not 610

destilant said:
Can someone please paste the output on a rooted ZE550KL in adb shell:
Code:
ls -al /dev/block/platform/dw_mmc/by-name
I already compiled a cm recovery, but i am not sure about the block names...
Click to expand...
Click to collapse
doesnt look like folder exists.
Code:
[email protected]_Z00L_93:/ # ls -al /dev/block/platform/
drwxr-xr-x root root 1970-05-15 01:49 7824900.sdhci
[email protected]_Z00L_93:/ #

heywheelie said:
the ZE550KL has a snapdragon 615 not 610
Click to expand...
Click to collapse
init! i wish people would stop polluting the version/hardware topic, especially since its so confusing already

wickedpygmy said:
looks normal, both have same resolution. I think both phones use the same firmware since the kernel is identical and Asus don't release Z00m firmware but use Z00L for both models.
Click to expand...
Click to collapse
might be same firmware but specs do differ slightly
https://www.asus.com/Phone/ZenFone-2-Laser-ZE550KL/specifications/
https://www.asus.com/Phone/ZenFone-2-Laser-ZE600KL/specifications/
WLAN bands differ, bluetooth is 4.0 on 550 and 4.1 on 6.0. Nothing dramatic but different

destilant said:
Can someone please paste the output on a rooted ZE550KL in adb shell:
Code:
ls -al /dev/block/platform/dw_mmc/by-name
I already compiled a cm recovery, but i am not sure about the block names...
Click to expand...
Click to collapse
This any use?
Code:
[email protected]_Z00L_93:/ # ls -al /dev/block/platform/7824900.sdhci/by-name
lrwxrwxrwx root root 1970-05-15 01:49 ADF -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-05-15 01:49 APD -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 1970-05-15 01:49 DDR -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-05-15 01:49 aboot -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-05-15 01:49 abootbak -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-05-15 01:49 abootdebug -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-05-15 01:49 asdf -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-05-15 01:49 asusfw -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-05-15 01:49 asusgpt -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-05-15 01:49 asusgpt1 -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-05-15 01:49 asusgpt2 -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-05-15 01:49 asuskey -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-05-15 01:49 asuskey2 -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-05-15 01:49 asuskey3 -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-05-15 01:49 asuskey4 -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-05-15 01:49 asuskey5 -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-05-15 01:49 boot -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-05-15 01:49 cache -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 1970-05-15 01:49 config -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-05-15 01:49 devinfo -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-05-15 01:49 factory -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-05-15 01:49 factorybak -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-05-15 01:49 fsc -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-05-15 01:49 fsg -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-05-15 01:49 hyp -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-05-15 01:49 hypbak -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-05-15 01:49 keystore -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-05-15 01:49 misc -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-05-15 01:49 modem -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-05-15 01:49 modemst1 -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-05-15 01:49 modemst2 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-05-15 01:49 oem -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-05-15 01:49 persist -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-05-15 01:49 persistent -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-05-15 01:49 recovery -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-05-15 01:49 rpm -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-05-15 01:49 rpmbak -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-05-15 01:49 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-05-15 01:49 sbl1bak -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-05-15 01:49 sec -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-05-15 01:49 splash -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-05-15 01:49 ssd -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-05-15 01:49 system -> /dev/block/mmcblk0p45
lrwxrwxrwx root root 1970-05-15 01:49 tz -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-05-15 01:49 tzbak -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-05-15 01:49 userdata -> /dev/block/mmcblk0p46
[email protected]_Z00L_93:/ #